Modular house · Explainer, Private AI · ~4 min read

Private AI is your models and your agents running on infrastructure you control, with your data staying inside boundaries you set. The name is about who holds the keys. It says nothing about how capable the tools are. Your data, your rules, from dirt to desktop, one partner from the hardware to the interface. Here is what that looks like in practice, and what it does not require you to give up.

The common misconception

Say “private AI” in a planning meeting and watch what people picture. Usually something small. A stripped-down model wheezing away on a spare laptop, good for a demo and not much else, the discount version of the tools everyone already uses at work. That picture is years out of date. A private workspace runs current open-weight models, several of them, on real hardware in a real facility, and you pick the one that fits the job. Privacy and capability are two separate questions. Answering one does not cost you the other.

The confusion is easy to forgive, because the line got blurry on purpose. The public tools sell a business tier with a setting that promises your data will not be used for training, and that promise is worth something. Read where it lives, though. It lives in a contract, and a contract is a thing both parties can revisit. Meanwhile your prompts still leave your building, cross the open internet, and land on servers you have never seen, in a jurisdiction you did not pick. The setting governs what the vendor says it will do with your data. Where your data goes stays the same.

Private AI closes that gap by removing the trust exercise entirely. Data cannot leak out of a boundary when the computing happens inside the boundary. There is nothing to opt out of. A setting is a promise. A boundary is a fact.

The three things that make AI private

Start with where the model runs, because everything else follows from it. When you ask a public tool a question, the question travels. It leaves your network, crosses the internet, and gets processed in a data center you cannot name, alongside everyone else’s traffic. Private AI turns that around: instead of sending your data to the model, you bring the model to your data. For our clients that means an isolated environment in a US-based, FedRAMP-certified data center, and for organizations that want it, dedicated hardware on their own premises. The question gets answered a few racks away from the data it draws on. Sometimes a few feet.

Then the data itself, which covers a lot more than chat history. The real value of a workspace shows up when you connect it to your documents. Contracts, research, case files, the institutional memory of the whole company. That happens through retrieval: the model reads the relevant pieces of your knowledge base at query time and grounds its answer in them. In a private environment, the documents, the index built from them, and the retrieval itself all stay inside the same boundary. Nothing is used to train anyone’s model. Nothing is retained by a third party, because there is no third party in the room.

And the part that gets discussed least while mattering most: who draws the boundary. Who can see which documents. Whether the system can reach the internet at all. What gets encrypted, what gets backed up, and what happens to all of it if you decide to leave. On public platforms those rules are set by the vendor and adjusted at the vendor’s discretion. In a private environment they are yours to set: access controls that separate the legal team’s vault from marketing’s, an air gap where the work demands one, and an exit that is just your data, in usable formats, walking out the door with you. That last one tells you who really owned the environment. If leaving is easy, you did.

What you keep

Everything your team actually liked about the public tools. The chat interface, the drafting and summarizing, the document questions, the code help. Those run just as well on infrastructure you control, through a clean web interface with access to multiple models, so people pick the model that fits the task instead of the one a vendor is promoting this quarter. Good UX is a software problem, and the software exists. Nobody has to learn to love a command line.

You also keep room to grow, because private is a spectrum, and you do not have to buy the far end of it on day one. Our Wildcat tier is the entry point: an isolated environment on shared infrastructure, in the same FedRAMP facility, under the same US jurisdiction as everything above it. Panther steps up to dedicated infrastructure, with file vaults, role-based access controls, and enhanced encryption for teams handling sensitive documents. Grizzly is the top: fully dedicated hardware, zero-trust architecture, an optional air gap, and the option to run it on your own premises instead of ours. The boundary tightens as you climb. What never changes is the jurisdiction. Your data stays in the United States whether it sits in our facility or in your building.

And you keep one accountable partner across the whole stack. The facility, with its redundant power and its guarded doors. The hardware in the racks. The models, kept patched and current, swapped for better ones as better ones ship. The interface your people log into every morning. When something needs attention, there is no seam between a cloud vendor, a hosting vendor, and an AI vendor for the problem to fall through. You hold the deed, and there is one number to call.

Your data, your rules.

The post What ‘private AI’ actually means appeared first on Modular Technology Group.

From the Desk of Cale · Cost, Fixed-cost AI · ~5 min read

Per-token pricing is a great way to start and a hard way to budget. The variable cost of someone else’s AI infrastructure isn’t actually variable to you. You just absorb the outputs: pricing changes, capacity limits, decisions made at a scale you’ll never see. Fixed, right-sized private infrastructure flips that. You know what you’re paying, and you know why.

The day-one price is not the real price

I’ve been thinking about taxi meters. A taxi is the right call for a trip to the airport, and nobody argues with the meter for one ride. But if you found yourself taking that same taxi to work every morning, you’d start doing math on a car payment before the end of the month. Per-token AI is a taxi meter, and a lot of companies are now commuting in it. Nobody chose the commute, either. The meter was already running when the habit formed.

The day-one price looks great because day-one usage is tiny. A handful of questions, a summarized document or two. Fractions of a cent each. Then the tool turns out to be useful, which is the whole point, and useful tools get used. People stop asking one question and start pasting in whole contracts. Someone wires it into a workflow that runs on every support ticket. Then come the agents, and an agent doesn’t make one call per task. It reads the document, checks its own work, calls a tool, reads the result, tries again. Every one of those steps is a metered ride. The per-token price never moved. Your consumption did, while everyone was busy being productive.

I sat with a client this spring and put a year of their AI invoices side by side on one screen. That was the entire exercise. No spreadsheet wizardry, no consultants. The line went one direction, and nobody in the room could name a month where anyone decided to spend more. That’s the tell. Metered costs don’t get decided. They accumulate.

Variable to them, fixed to you (and vice versa)

Here’s the part that took me embarrassingly long to see clearly. The provider’s costs are mostly fixed. The data centers are already built and the payroll is already set. What’s variable, to them, is you. Metered pricing is how they convert their fixed cost into your variable one. That’s a rational move on their side of the table. It’s just worth noticing which side of the table you’re on. When a business absorbs volatility, it charges for the service. When it passes volatility through, you’re the one providing that service, and nobody’s paying you for it.

So when their world shifts, the shift gets passed through. A new model generation lands and the price per token changes. Demand spikes and rate limits show up at exactly your busy hour. An older model gets retired, and the workflow your team spent a quarter tuning now runs on something that behaves differently. There’s no villain in any of that. A business planning for millions of customers makes ordinary capacity decisions, and you’re one line in the plan. You don’t get a vote. You get an email.

Now put yourself in the budget meeting. Finance asks what AI will cost next year. The honest answer under metered pricing is “it depends on how much people use it,” which is another way of saying the better it works, the less we can predict. That’s a strange incentive to hand a mid-sized team. Success becomes a cost overrun. I’ve watched a manager quietly discourage adoption of a tool his own company was paying for, because every new enthusiastic user made his forecast worse. Every budget is a guess, but this one is a guess about other people’s guesses.

What predictable looks like

Predictable starts with a boring question: what do you actually run? Not someday, today. Count the real workloads. The document review, the drafting, the internal search, the two or three automations that matter. Most teams find the list is shorter than they feared and steadier than the invoices implied. That steadiness is the asset. You size for your own team and the work it actually does. The whole internet is somebody else’s capacity problem. Once you know the workload, you can size the hardware to it, and once the hardware is sized, the cost is flat. You know the number in January and it’s still the number in October.

That’s the shape of what we build at Modular Technology Group. Our Private AI Workspaces start with Wildcat on shared infrastructure, step up to Panther on dedicated infrastructure, and top out at Grizzly on fully dedicated hardware, which you can host with us or stand up in your own building. The hosted tiers all live in a US-based, FedRAMP-certified data center. Every one of them bills as a flat monthly number. No per-token billing anywhere. We run our own work on the same stack, so when the meter argument comes up, we’re not speculating. We live on the fixed side of it. Right-sizing is a conversation. Some teams land on shared infrastructure and stay there happily. Some need the hardware where they can see it. Either way the number gets chosen, and you’re in the room when it happens.

The total-cost math is worth saying plainly. Owning can look more expensive on day one, the way a car payment looks worse than one cab fare. But a fixed cost changes the direction of every incentive after that. Under a meter, each new user is a liability. On infrastructure you own, each new user makes every task cheaper, because the same monthly number is now doing more work. You quit rationing the tool and start pushing it. Adoption stops being a cost problem and turns back into what it should have been, which is a productivity story. And because the models sit behind an interface you control, no single provider’s pricing decision can reach into your budget. When a better open model ships, it slots in. The bill doesn’t notice.

Here’s something you can do this week, and it costs nothing. Pull your last twelve months of AI invoices and put them in one place. Ask two questions. What happens to this line if usage doubles, and who decided the current number? If the answers are “it doubles” and “nobody,” you’re renting, and now you know what the rent really is. Then you get to decide what the number should be instead. Your data, your rules, from dirt to desktop.

If your AI line item has quit behaving, or you just want a second set of eyes on the own-versus-meter math, I’m always glad to compare notes. No pitch. Bring the invoices.

Own it, don’t rent it. Your data, your rules.

The post The hidden cost of renting your AI appeared first on Modular Technology Group.

Episode 8 · 4:40 · Download MP3 · RSS · Transcript

An AI agent is not a feature you switch on. It is an actor with authority. This week: a single link that could build a working agent inside somebody’s workspace with every connector attached and approvals switched off, an attacker who ran an agent unattended inside a national finance ministry, and a government that stopped a billion-euro cloud procurement to ask where its data lives. Three sizes of the same question.

In this episode

• A link that built an agent. Researchers showed one crafted URL could create a working agent inside a logged-in account, attach every connected mailbox and file store, set approvals to never ask, and put it on an hourly schedule. Patched on June 8, with no reported exploitation in the wild. The open question is not the bug. It is how casually agent authority gets handed out.
• An agent nobody was supervising. A security firm reports an attacker running an off-the-shelf agent with its approval mode disabled for post-exploitation work inside a national finance ministry. One firm is the only public source and the ministry has not confirmed it. The transferable lesson is that the useful setting was the one that removed the human.
• A government asking where its data lives. Ireland’s Office of Government Procurement cancelled a cloud framework competition over digital sovereignty. Jurisdiction moved from a slide in a security review to a reason to stop a contract.

Sources

• The Hacker News, July 24, 2026 — agent-builder flaw
• The Hacker News, July 24, 2026 — unattended agent at a national finance ministry
• The Register, July 22, 2026 — Ireland stalls cloud tender over digital sovereignty

AI voice disclosure

Laura and Arthur are AI-generated voices, produced locally on Modular’s own hardware. Story selection, reporting, and fact-checking are done by the Modular Technology Group team. Your data, your rules applies to our own production too.

If your team is pointing AI agents at real systems and nobody can say who owns them or what they may touch, book a conversation.

Your data, your rules.

The post The Modular Briefing, Episode 8: Who Gave It the Keys? appeared first on Modular Technology Group.

On July 13, 2026, the Department of War announced the immediate suspension of CMMC Phase II, the third-party certification requirement that had been scheduled to start appearing in defense contracts on November 10, 2026, roughly four months out (DefenseScoop). Read the announcement closely: the suspension covers only the certification gate. DFARS 7012 still applies. The NIST 800-171 self-assessment still applies. For anyone bringing AI into the defense supply chain, that means less paperwork sitting on top of the same responsibility. Piping that data into someone else’s cloud model is still a risk you own.

What the suspension actually covers

Phase II is the part of CMMC where an outside assessor certifies you, meaning Level 2 assessments conducted by a C3PAO and the Level 3 assessments above them. That requirement is now suspended while a new CMMC Reform Task Force runs a 60-day review, and Phases 3 and 4 are frozen along with the program’s future implementation milestones. The stated reason is cost. The department wants to cut compliance expense and bureaucratic burden as part of a wider effort to streamline defense acquisition, and for a small contractor that is genuinely good news.

The review leaves the standing rules in place. DFARS clause 252.204-7012, which requires you to safeguard covered defense information and report cyber incidents, remains in force. So does the CMMC Phase I self-assessment: you still complete a NIST SP 800-171 self-assessment and upload your score to the DoD’s SPRS system. An inaccurate score can still create liability under the False Claims Act. The only thing removed from the calendar is the assessor’s visit. Every rule that assessor would have checked remains on the books.

What the pause means for how you handle CUI

The obligation follows the data, and it always has. Controlled unclassified information, CUI, carried the same obligations on July 14 that it carried on July 12, whether or not anyone is scheduled to check your work. Now consider where CUI actually goes when someone on your team pastes a spec or a contract excerpt into a public AI chat tool. It leaves your network and lands on infrastructure you cannot inspect, under retention terms you never negotiated. DFARS 7012 still expects you to report incidents involving that information, and you cannot report what you cannot see.

There is also the score you already attested. Your SPRS submission describes an environment where CUI stays inside defined controls. If CUI is quietly flowing into public tools, that submission stops being true, and the False Claims Act does not pause for a task force. The right response is simply to know where your data goes, and that is a thing you get to decide.

The private-AI answer for defense work

The same move that satisfies the standing rules also unlocks the AI you wanted in the first place: run the model inside a boundary you control. That can be your own environment, or a private one a partner builds and operates for you. When the model lives where the data lives, CUI never crosses into a system you cannot account for. This maps directly onto what survived the review. 7012 asks you to safeguard covered defense information; a boundary you control is the safeguard. The 800-171 self-assessment asks you to score your environment honestly; a contained environment is one you can score honestly and keep scoring honestly, review or no review.

You can move before the task force reports, and you can bring in help to do it. Modular Technology Group builds and runs private AI for contractors in exactly this position, and we own the whole stack. Your data, your rules, from dirt to desktop. Use the pause to get your AI inside your boundary, so that whatever comes back from the review, you are already standing where the rules point.

Your data, your rules.

The post The compliance gate paused. Your duty to your data did not. appeared first on Modular Technology Group.

Most companies did not decide to rent their AI. It happened one login at a time. A hotel is fine for a night, but you do not own the room, you cannot change the locks, and the nightly rate is whatever they say it is. Your business AI deserves a home you own, where your data stays yours and the bill does not surprise you.

How renting happens by accident

Nobody signs a lease with the whole company in mind. Someone in marketing starts a free trial to draft campaign copy. An engineer signs up with a work email because the tool saves an hour a day. Neither asks permission, because why would they? It is a free trial. Six months later there are a dozen seats spread across four departments, nobody owns any of them, and nobody can say what has been pasted into which chat window. There is no boundary because nobody ever drew one.

The moment you notice is usually mundane. A renewal notice arrives at a new rate, or a client’s security questionnaire asks where their information lives and the honest answer takes a week to assemble. So you decide to consolidate, and you discover that the prompts, the saved conversations, the custom workflows, the habits your team built are all inside someone else’s building. You can walk out, but you leave the furniture. That is the tell that you have been renting all along: leaving costs more than staying, and the landlord knows it.

What “owning the room” actually buys you

Start with the question your clients are already asking you: where does our data live? When you own the room, the answer is one sentence. It lives here, inside a boundary we control, and it does not feed anyone else’s model. That answer shortens security reviews and calms auditors, and it has the advantage of being simply true. No contract exhibit required.

The economics change too. Renting means metered billing, per seat and per token, at a rate set by someone who knows you cannot easily leave. Owning means the cost is mostly fixed. You know what the hardware costs and what running it costs, and the bill in month eighteen looks like the bill in month three. Budgeting becomes boring, which is exactly what budgeting should be. There is a quieter benefit underneath both of those: because the models sit behind an interface you control, you can change them without changing anything else. When a better open model ships, and they ship constantly now, you swap it in over a weekend. No migration project, no new vendor negotiation. The room stays the same. Only the furniture improves.

What it does not require you to give up

The usual objection is that owning means going without. It does not. The tools your team already likes (the chat interface, the document work, the code assistance, the meeting summaries) run just as well on infrastructure you control. Good UX is a software problem, and the software exists. Your people should not notice a difference, except that the question of where the data goes finally has an answer.

Owning also does not mean building from scratch. You would not pour your own foundation to own a house; you would hire a builder and hold the deed. The same trade exists here. A partner can stand up the hardware, run the models, keep everything patched and current, and hand you the keys. That is the work we do at Modular: your data, your rules, from dirt to desktop. You hold the deed. We keep the lights on.

Your data, your rules.

The post AI needs a home, not a hotel appeared first on Modular Technology Group.

That is not a story about lazy employees. It is a story about missing guardrails.

The real risk is ownership, not the tool

When someone submits work they do not understand, the organization has quietly taken on a liability it cannot see. A wrong figure in a board deck, an unsupported claim in a client memo, a compliance answer that sounds right and is not: each of these is now traveling under your name, and no one in the building can defend it. The tool did not create that exposure. The absence of an owner did.

This is the pattern behind most shadow AI. People adopt AI because it helps, not because they were reckless. They paste a contract into a public chatbot to summarize it. They let a model draft the analysis and move on. Every one of those choices is reasonable in isolation. Added up across a department, with no policy and no review, they become an accountability gap that widens every week.

Banning the tool is the wrong instinct

The reflex in regulated and high-stakes work is to lock AI down. Block the sites, forbid the tools, wait for the risk to pass. It never does. The work still needs doing, the tools are still faster, and the usage simply moves somewhere you cannot see. A ban does not remove the risk. It removes your visibility into it.

The better move is to govern the tool the same way you govern any other capability that touches sensitive work. Name an owner. Set the boundaries. Give people sanctioned tools that are good enough that they stop reaching for the unsanctioned ones. Your AI, your rules, the same principle you already apply to your data.

What governance looks like in practice

Governance sounds heavy. In a mid-sized company it is closer to a short list of decisions made once and enforced consistently:

• An accountable owner. Someone whose job is to say what AI is allowed to touch, and to answer for it. This is the core of the fractional Chief AI Officer role: senior judgment on AI risk without a full-time executive hire.
• Sanctioned tools with real boundaries. A private, governed workspace where your data stays inside your walls and never trains someone else’s model. When the approved option is genuinely useful, shadow AI loses its pull.
• Oversight that fits the work. Higher-stakes output gets a human check before it ships. Routine work moves fast. Match the level of review to the level of consequence, not the other way around.
• Training that closes the gap. People should be able to explain what the AI did for them. That is a skill, and it is teachable.

None of this requires banning anything. It requires deciding who is responsible before the work goes out the door, not after it comes back wrong.

The through-line

Every organization is going to run on more AI next year than it does today. The question is not whether your team uses it. They already do. The question is whether the work it produces is something you can stand behind.

That comes down to ownership. Own the tools, own the data, own the decision about who is accountable. A duty of care, not a ban.

If you are not sure who owns AI risk in your organization, that is the first thing worth fixing. It is exactly the problem a fractional Chief AI Officer is built to solve, and it is where we usually start.

Talk to us about AI governance →

Your data, your rules. Modular Technology Group helps regulated and mid-sized teams run private AI on infrastructure they own, from dirt to desktop.

The post When Your Team Ships Work They Can’t Explain appeared first on Modular Technology Group.

If your AI runs on someone else’s meter, that forecast is not a growth story. It’s an invoice you haven’t opened yet.

And the companies you’d expect to absorb that hit better than anyone are the ones flinching first. Uber reportedly burned through its entire 2026 AI budget in a matter of months. Uber’s CTO went public with it, and the operations chief, Andrew Macdonald, told Business Insider something even more damning than the overspend: after talking to his senior engineers, he couldn’t find a clear line between how many tokens the company was burning and how many features customers actually got. More than 80 percent of Uber’s engineers were using agentic tools. Over 60 percent of the code was AI-generated. And it still wasn’t worth what they were paying for it.

Microsoft, meanwhile, started pulling its own developers off a third-party coding assistant and moving them onto an in-house tool, with a deadline that landed conveniently at the close of its fiscal year. The official line was consolidation. The timing told a different story. Microsoft also flipped one of its developer products to token-based billing because the cost of running it had ballooned.

When the two companies that helped write the playbook for aggressive AI adoption are both quietly restructuring how they buy it, that’s not a blip. That’s the meter catching up with the marketing.

The math nobody put on the slide

For two years, the pitch for cloud AI has been simple: usage is cheap, it’ll only get cheaper, and you can scale infinitely. The first part was true for a chatbot answering one question at a time. It stops being true the moment you point an agent at a real workflow.

A single agentic task can consume more than a thousand times the tokens of a one-shot chatbot query. Agents don’t ask once. They plan, call tools, check their own work, retry, and chain steps together, and every one of those steps is metered. Multiply that by a whole department running agents all day, then layer on the Goldman Sachs 24x demand curve, and the “it’ll get cheaper” story collapses under its own arithmetic.

The numbers coming out of the industry have started to sound less like efficiency and more like a dare. Nvidia’s CEO said earlier this year that if one of his $500,000 engineers wasn’t burning at least $250,000 in tokens, he’d be worried. Airbnb’s CEO bragged that 60 percent of the company’s code is now AI-generated. One reported that 84 percent of its code was AI-written. A three-person team running an aggressive stack of agents managed to spend $1.3 million in tokens in a single month.

Somewhere in there, the conversation quietly stopped being about results and started being about consumption for its own sake. Token usage became the brag, as if the size of the bill proved the value of the work. Uber just demonstrated, in public, that it doesn’t.

Consumption is not a strategy

Here’s the part that should land for any business owner watching this from the outside: the meter punishes exactly the usage you’re being told to chase.

You are encouraged to put AI into everything, hand the agents more autonomy, let them run longer and reason harder. Every one of those instructions increases token consumption. So the more seriously you take the advice, the faster your costs compound, and they compound on a curve you don’t control and can’t predict. You find out what you owe after the work is done. That’s a brutal way to run a budget, and it’s an impossible way to run a small or mid-sized organization that needs to know its number before the quarter starts, not after.

This is the question we ask clients to sit with before they sign anything: what happens to our costs if our usage succeeds? If the honest answer is “they go up in a way we can’t forecast,” then the platform isn’t priced for you to win. It’s priced for you to ration.

And rationing is precisely what’s happening. The biggest names in tech are now teaching their people to use less of the very tools they spent a year telling everyone to use more of. If Microsoft and Uber can’t make consumption-based AI pencil out at their scale, the odds that a 40-person law firm or a boutique advisory shop will are not good.

The hardware cavalry isn’t coming in time

The usual reassurance is that better chips will rescue the economics. Next-generation inference hardware is genuinely more efficient, and the Goldman Sachs report leans on exactly that hope: cheaper tokens, usage keeps climbing, profits eventually follow.

The timing doesn’t cooperate. The newest platforms are still rolling out, and the efficiency gains, real as they are, are years from deploying at the scale this demand curve requires. In the meantime, more than half of the data center projects planned around the current generation of hardware have reportedly been delayed or cancelled, choked by shortages of power and parts. The hyperscalers themselves have started stretching their hardware to run for six years instead of replacing it on the old cadence, which is hard to square with the promise of a dramatic efficiency leap every single year.

So the demand is exploding now. The relief is theoretical and late. And the gap between the two gets paid for in your monthly bill.

There is another way to buy this

None of this is an argument against AI. We build our business on AI. It’s an argument against renting your intelligence by the drink from infrastructure you don’t control, priced on a model designed to climb.

At Modular Technology Group, we made a different bet, and the news this month is the reason we made it. Modular runs private AI on infrastructure we own, in a US-based FedRAMP data center, at a fixed monthly price. No per-token billing. No per-query billing. No consumption meter quietly compounding in the background while your agents do exactly what you asked them to do.

When the AI runs on hardware you control, the equation flips. Heavier usage doesn’t mean a heavier invoice. Once the box is yours, running more agents, longer reasoning, bigger context, all of it lives inside a cost you already know. The incentive inverts: instead of being penalized for using AI more, you’re free to. That’s the difference between intelligence as a metered utility and intelligence as owned capability.

A few things follow from owning the stack instead of renting it:

Your costs are knowable before the work starts. A flat monthly fee means the budget conversation happens once, up front, not in a panicked review when the usage report comes in. No surprises, no variable cloud bill, no quarter blown in a month.

Your usage can succeed without punishing you. The whole point of AI is to do more with it over time. On a metered model, success is the thing that breaks your budget. On owned infrastructure, success is just success.

You’re not locked to one vendor’s pricing whims. Microsoft just moved a product to token billing because its own costs ran away. When you don’t own the layer your business depends on, someone else’s cost problem becomes your pricing problem overnight. We run the model that fits the job, on hardware that’s ours, so a vendor’s repricing isn’t your emergency.

Your data stays yours. This was always the foundation. Models run locally, on our infrastructure, in our facility. Your data never routes through someone else’s cloud to get answered. Your data, your rules. The cost predictability is a benefit that rides on top of the same architecture that keeps your information private in the first place.

The meter was always the business model

The token-billing crisis isn’t a bug in cloud AI. It’s the business model working as designed. Usage was always going to climb, agents were always going to multiply the consumption, and the bill was always going to follow the curve. May just happened to be the month some very large companies looked up and noticed.

The organizations that come out of this ahead won’t be the ones who used AI the least to survive the bill. They’ll be the ones who stopped renting intelligence by the token and started owning it, so that using more was never the thing that hurt them.

If you’re staring at an AI bill that grows every time the tools actually work, that’s worth a conversation. We’re always happy to compare notes on what fixed-cost, private AI looks like for an organization your size. You can reach us at modtechgroup.com/consultation.

Because when the token bill finally comes due across the industry, you want to be the company that already knows its number.

Modular Technology Group builds and operates private AI infrastructure on owned, US-based hardware: fixed pricing, local inference, your data and your AI under your rules, from dirt to desktop. modtechgroup.com

The post When the Token Bill Comes Due: What Uber and Microsoft Just Taught the Rest of Us About Renting Intelligence appeared first on Modular Technology Group.

At Google Cloud Next 2026 in Las Vegas this week, Google made a quiet but significant announcement: Gemini can now run on a single air-gapped server, fully disconnected from the internet — and from Google itself.

The product is a Dell-certified, Google-approved hardware appliance delivered through a neocloud partner called Cirrascale Cloud Services. Eight Nvidia GPUs. Confidential computing protections. The marketing hook: “pull the plug and the model vanishes.”

We’ve been watching the coverage with genuine interest. And a fair bit of déjà vu.

The Market Just Caught Up

For years, enterprise organizations in financial services, healthcare, defense, and government faced what analysts called an impossible tradeoff: access the most powerful AI models through public cloud APIs — and surrender control of your data — or settle for less capable open-source models you could host yourself.

Google’s announcement is a formal acknowledgment that this framing was always wrong. The demand for fully private AI wasn’t a niche concern. It was the only architecturally honest answer for any organization that takes data governance seriously.

Modular Technology Group has been building on that premise since before it was a keynote slide.

What Google Is Actually Selling

Let’s be precise about the offering, because the details matter.

The Cirrascale deployment requires a Google-certified hardware platform. It requires a partnership with a specific neocloud provider. It requires Google’s approval of the appliance configuration. General availability is projected for June or July 2026 — it’s in preview now.

And the selling point — that the model “vanishes when you pull the plug” — is a confidential computing feature that ties the model weights to the specific hardware. Impressive engineering. But consider what it implies: you are still dependent on Google’s certification ecosystem to acquire and maintain access to the model. The sovereignty is physical, not architectural.

The right question for any enterprise evaluating this: What is your exit strategy?

• What happens if Cirrascale changes its pricing or partnership terms?
• What happens if Google deprecates the on-premises licensing tier?
• What happens when the certified hardware goes end-of-life?

Vendor lock-in doesn’t disappear because the server is in your rack. It moves from the network layer to the hardware and licensing layer.

A Different Architectural Bet

Modular Technology Group made a different set of choices when we designed our private AI infrastructure.

Model-agnostic. We are not tied to any single model provider. Our clients run the models that fit their use case — whether that’s an open-weight model, a fine-tuned variant, or a frontier model accessed under controlled conditions. When a better model ships, you switch. No re-certification. No new appliance.

Hardware-agnostic. We operate in a FedRAMP-authorized data center on infrastructure you control. You are not locked to a specific GPU configuration or a vendor-approved hardware stack. The architecture scales with your needs, not with a product roadmap you don’t control.

Fixed, transparent pricing. No usage-based API billing. No surprise invoices at the end of the month. You know what you’re paying. That predictability is a feature, not an accident.

Available now. Not in preview. Not GA in Q3. Running, deployed, with clients in production today.

Data Sovereignty Is Architecture, Not Proximity

The broader lesson from Google’s announcement isn’t about Google. It’s about how the enterprise AI market is maturing in its understanding of what “private” actually means.

Physical proximity — a server in your building, or in a data center you can point to — is necessary but not sufficient. True data sovereignty requires architectural ownership: control over the model, the infrastructure, the data pipeline, and the exit path.

When your AI model “vanishes when you pull the plug,” ask yourself: whose plug is it, really?

At Modular Technology Group, “Your Data, Your Rules” isn’t a product announcement. It’s been the design constraint from the beginning.

If you’re evaluating private AI infrastructure — whether in response to this week’s news or because you’ve been thinking about it longer than Google has been announcing it — we’re happy to compare architectures.

Schedule a conversation →

---

Source inspiration: LinkedIn

The post When Google Validates Your Architecture: Private AI Was Never the Alternative appeared first on Modular Technology Group.

The post The Model That Barely Slows Down: Gemma 4 26B vs Qwen 3.6 35B at Long Context appeared first on Modular Technology Group.

The post Same AI Model, Two Hardware Tiers — And Why Context Length Is the Hidden Variable appeared first on Modular Technology Group.