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.

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.

The post AI Isn’t Just for Clients — It’s in Our DNA appeared first on Modular Technology Group.