A cloud that passed the sovereignty test, storage that passed it, a model on top that passed it too. Each piece certified, so the sum must be too. It isn’t necessarily. The sum may have parts no certificate covered – the pieces someone adds, the way they’re joined, the provider’s own dependencies, whoever operates the result. Any one of them can make the whole not sovereign. Sovereignty doesn’t add up from the parts. ...
Sovereignty done right makes you resilient. But sovereignty you don’t operate is the opposite: a risk. You move a workload in-house to be more sovereign. Your jurisdiction, your rules, no outside provider in the loop. More control – which is the whole point. But the provider you left wasn’t only running the service. They were also keeping it up, patching it, and making sure you could still reach it when something broke. You didn’t see that part, because you never had to. ...
A global company decides to become fully sovereign. Every system in its own data centers, in its own jurisdiction. Foreign providers out, cross-border transfers stopped, the estate air-gapped. Customer data untouchable, IP locked down. Then it goes bankrupt. It was in the pizza delivery business, and the ordering platform was inside the air gap with everything else. Of course nobody would do this. But notice what went wrong: not the ambition, not the execution. They applied it uniformly. The recipe and the order line got the same treatment, and only one of them needed it. ...