Vendors know “sovereign” wins deals. So the word gets attached to offerings that are, on inspection, an in-country datacenter wrapped around a foreign-controlled platform. That is sovereignty washing — and in defense and public-sector procurement it is a disqualifying risk, not a marketing quibble.
The five questions
Ask these of any “sovereign” offering. Each one a vendor cannot answer cleanly is a dependency you are inheriting.
1. Who operates the control plane?
Not where the data sits — who runs the system. If the vendor’s staff operate the control plane, the vendor’s jurisdiction reaches your workloads.
2. Can it run fully disconnected?
A genuinely self-hosted platform can run air-gapped, with no call-home, no licence server check-in, no remote management path. If disconnection breaks it, it was never yours.
3. Who holds the encryption keys?
“Encrypted at rest” is meaningless if the provider holds or escrows the keys. Sovereign key management means the keys never leave your control.
4. What jurisdiction is the vendor subject to?
A US-headquartered vendor is subject to the US CLOUD Act regardless of where the datacenter is. A vendor’s home law travels with the vendor. Ask explicitly.
5. Can you read and rebuild the source?
Closed source means you are trusting, not verifying. Open source means you — or an auditor, or a national security agency — can inspect exactly what runs.
The residency-vs-sovereignty table
| Claim | What it actually guarantees |
|---|---|
| “Data stays in Germany” | Location at rest. Not access, not control. |
| “EU region” | A datacenter location on a foreign control plane. |
| “Encrypted at rest” | Nothing, if the provider holds the keys. |
| “ISO 27001 certified” | A security-management process — not sovereignty. |
| “Sovereign, self-hosted, open source, no foreign root” | Sovereignty. |
Why this matters more in defense
In a commercial context, sovereignty washing is a procurement disappointment. In defense and critical public infrastructure, a foreign dependency that surfaces during a crisis — a jurisdiction dispute, a sanctions regime, a vendor withdrawal — is an operational failure at the worst possible moment. The Anthropic-shutdown episode was a small, civilian preview of a general risk: capability you don’t control can be withdrawn.
Our own rule: we hold ourselves to the same test. We do not publish a certification, clearance, or reference we cannot substantiate — because a sovereignty brand that overclaims becomes the thing it critiques.
Once you can name the dependencies, you can decide which are acceptable. The point of the test is not that every foreign component is disqualifying — it is that a sovereign posture should be chosen with eyes open, not sold under a label.