Let’s talk about why the AI model running on your own machine might still belong to someone else.
There is a moment every builder hits now. You watch the cloud assistant get a little too good at predicting you, and something in your chest tightens. So you go looking for the alternative. A local model. Open weights. Runs on your hardware, your data stays in the building, no telemetry, no subscription, no middleman.
It feels like buying the farm instead of renting the plot. And it is a real thing — local inference is genuinely private in ways the cloud is not. But here is the pattern nobody is naming: sovereignty is being sold as a location. Move the model onto your desk and you are told you own it.
You don’t. You’re a tenant.
Let me walk the lease.
First, the hardware. That “private” model runs on a chip whose firmware, drivers, and update channel belong to someone else. The NPU in your laptop has its own little operating system you never see. The vendor can patch it, profile it, and in some documented cases, phone home through the very feature that was supposed to make you local. You didn’t escape the cloud. You moved into its guest house.
Second, the weights. Open weights does not mean open mind. The model arrived fully formed, trained by a lab on a data set you will never fully see, aligned to values you did not vote on. Fine-tuning it on your documents makes it your color of paint on someone else’s house. You control the runtime. You do not control what it knows or why it answers the way it does.
Third, the license. This is the one that gets builders. “Open” licenses still come with clauses: no commercial use, attribution requirements, restrictions on what you can fine-tune and resell, and occasionally a quiet line that lets the lab harvest your usage or your fine-tunes. A license is a contract. Most people who download a model never read the one they just signed.
Fourth, the update. Local does not mean permanent. The model you love today needs the next version for security, for new benchmarks, for the bug that makes it say the wrong thing to a customer. Every update is a new consent moment. The vendor can change the terms, change the behavior, or simply stop shipping — and your “owned” intelligence starts rotting on the shelf.
So here is the test that matters. Sovereignty is not where the weights live. It is who holds the keys.
Can you verify what the model actually does, or are you trusting a benchmark from the people who built it? Can you audit its outputs against your own standard, or are you taking its word? Can you leave — take your data, your fine-tunes, your workflows — and get the same behavior somewhere else? Can you prove your data never left the device, or are you taking the vendor’s word for that too?
Most “sovereign AI” fails at least one of those. Usually more.
And that is the operator lesson hiding in the pattern. When a vendor sells you privacy, ask what they mean by it. When they sell you control, ask who holds the root account. The companies that made the cloud sticky are now very happy to sell you a local box — because the box still runs their silicon, their weights, their license, their update feed. They moved the storefront. They kept the inventory.
I am not saying local is a scam. I am saying local is a spectrum, and most people are buying the first rung and being told they bought the ladder.
The real question to ask any AI vendor, cloud or local, is not “where does this run?” It is: if you disappeared tomorrow, does this still work? Do I still know what it knows? Can I prove what it did with my data?
If the answer to any of those is “trust us” — you are renting.
Renting is not a sin. Renting is a legitimate choice, as long as you know you are renting. The sin is paying the ownership price and getting the rental agreement.
The machine is going to get more personal either way. Go into it with your eyes open, or find out on the day you try to leave.
Ask the vendor the disappear question. If it makes them uncomfortable, that is your answer.