Field Note
Sovereignty means more than data residency
Residency is one property of a system. Custody, operational control, technological dependence, and the ability to leave determine whether an organisation can keep operating on its own terms.
“Stored in region” answers one useful question: where the provider says the data rests. It does not answer who can access the system, which jurisdiction applies to the operator, whether a workload can be moved, or what happens when the provider changes a service.
Four tests make the distinction clearer.
1. Residency
Where are data, backups, logs, model inputs, and derived artifacts stored and processed? The answer needs to include failover and support paths, not only the primary database region.
2. Custody
Who holds encryption keys and privileged access? Which employees, sub-processors, or government authorities can compel or perform access? A local region operated through a foreign control plane can satisfy residency while leaving custody elsewhere.
3. Control
Who can change the model, runtime, identity system, policy, or update schedule? Can the organisation inspect the relevant components, defer an update, run offline, and apply its own safety or retention rules? For AI, control reaches weights, prompts, tools, evaluation data, and the orchestration layer.
4. Continuity
Can the system keep doing essential work through a network outage, commercial dispute, provider exit, or change in law? Is there a tested export in a usable format and a second execution path?
These are not theoretical additions. The European Commission’s Cloud Sovereignty Framework evaluates legal, operational, supply-chain, technological, data, AI, security, and strategic dimensions. The EU Data Act adds switching and interoperability duties for cloud and edge services, including requirements intended to remove obstacles to moving between providers.
Neither instrument settles a universal definition of sovereign AI. They do show why a map pin is insufficient. A credible sovereignty claim should name the dependency, the control the operator actually holds, and the failure or exit test that proves it.