Sovereignty isn’t an exit plan. It’s a floor plan.

The Register ran a piece this week that a lot of IT leaders will nod along to: digital sovereignty sounds great until you try ditching your suppliers. The gist: everyone in Europe and beyond is suddenly talking about controlling their own data, their own infrastructure, their own destiny. Then they open the hood, see fifteen years of accumulated dependence on two or three hyperscalers, and quietly close it again. Migration is expensive. The skills aren’t there. The integrations run deep. Sovereignty, the article suggests, is a nice speech and a brutal project plan.

The article is right about almost everything, and it still draws the wrong lesson.

The pessimism is earned, but it’s pessimism about retrofitting

Read the piece carefully and notice what every hard case has in common. The organizations struggling aren’t struggling with sovereignty. They’re struggling with reversal. They built for a decade on someone else’s platform, using someone else’s proprietary services, on someone else’s contract terms, and now they want to walk it back. Of course that’s painful. You’re not adopting an architecture at that point. You’re performing surgery on a live patient who’s been fused to the operating table.

Egress fees are the obvious villain, and yes, they’re real money. But egress is the small problem. The big problem is that most cloud-native systems weren’t designed to run anywhere else. When your app logic is welded to a hyperscaler’s managed queue, its identity service, its serverless functions, its specific flavor of managed database, the data can technically leave. The system can’t. You’d be rewriting, not migrating.

So when a CIO says “sovereignty is too hard,” what they usually mean is “unwinding my last ten years of decisions is too hard.” True. Also not an argument against sovereignty. It’s an argument against how they got here.

Lock-in is a design choice you made, whether you noticed or not

Nobody signs a contract titled “Dependence Agreement.” Lock-in accretes. A team picks the managed service because standing up the open equivalent would take three sprints. A vendor discount ties renewal to consumption commitments. A compliance officer signs off on a region, and suddenly the region is load-bearing. Each decision was locally rational. The sum is a company that can’t leave.

The fix isn’t a heroic exit project scheduled for some future fiscal year when things calm down. Things never calm down. The fix is refusing to accumulate the dependence in the first place, and that has to happen at the architecture stage, on day one, when it’s cheap.

What does that actually look like? Concretely:

Own the physical layer or contract it in a way you can walk away from. Know which building your data sits in and under whose legal jurisdiction. If the answer involves a foreign court’s subpoena power, you don’t have sovereignty, you have a hopeful arrangement.

Pick portable primitives. Containers over proprietary serverless. Open protocols over vendor SDKs. Standard databases over managed ones with quirks you’ll only discover during a migration. Boring choices, deliberately.

Stay model-agnostic on the AI side. This is the newest lock-in vector and the fastest-growing one. Teams are currently wiring their workflows to one frontier model’s API the same way teams in 2012 wired everything to one cloud’s services. Same movie, faster projector. If your prompts, your pipelines, and your evaluations only work against one vendor’s endpoint, you’ve rebuilt the exact trap The Register is describing, except this time the vendor can change the model underneath you without asking.

Fix your costs. Variable consumption pricing is itself a control mechanism. When leaving means eating an unpredictable bill, the pricing model is doing the lock-in work the technology doesn’t have to.

None of this is exotic. It’s just unfashionable, because every step trades a little short-term convenience for long-term freedom of movement, and short-term convenience has been winning that trade for fifteen years. The Register piece is the invoice arriving.

We’re biased, and here’s why

Modular builds private AI infrastructure end to end, from the physical facility up through the interface people actually use. From dirt to desktop, on US soil, at fixed pricing, running whatever models fit the client’s needs rather than whichever vendor bought us lunch. So yes, we have a horse in this race.

But the reason we built it that way is precisely the failure mode in this article. We watched organizations try to bolt sovereignty onto architectures that were never meant to grant it, and we watched the retrofit cost kill the initiative every time. The only version of sovereignty that survives contact with a budget meeting is the version that was there from the start, when portability cost nothing extra because it was simply how the system got built.

Your data, your rules. That’s the whole thesis, and it only holds if “your rules” is enforced by the architecture instead of promised by a contract. A sovereignty clause in an MSA is a rule the vendor agreed to follow. A stack you control is a rule nobody has to follow, because there’s no one else in the room.

The honest takeaway

If you’re deep in a hyperscaler today, the article’s pessimism is fair warning: don’t announce a grand exodus you can’t fund. Rank your workloads by how trapped they are. Move the portable ones. Stop the bleeding on new builds by making them portable by default. Sovereignty regained incrementally beats sovereignty announced and abandoned.

And if you’re starting something new right now, an AI initiative, a new product line, a greenfield system, you have a choice the retrofitters would kill for. You can build on ground you own. The cost of doing it from day one is small. The cost of doing it in year ten is the entire subject of that Register article.

So here’s what I’d genuinely like to know from people running infrastructure right now: if you had to move your most important workload off its current platform in twelve months, what’s the first thing that would break? Not hypothetically. Name it. That answer tells you more about your sovereignty posture than any strategy deck, and I’d like to hear it.