A question the Sovereignty Test answers ยท from Own Your AI, chapter 2
Is sovereign hosting the same as sovereign AI?
No. Sovereign hosting answers the location question: where the data and the compute sit, and under whose law. Sovereign AI answers the control question: who can access, modify or terminate the system.
A region can be sovereign while the AI inside it is not. Data in a sovereign region, run by contractors who can be compelled elsewhere, on a model you cannot swap, is sovereign hosting. It is not sovereign AI. The difference is the whole of the Sovereignty Test, which ignores the place and asks who controls the system.
01What hosting gives you
Location solves one half of one control.
Sovereign hosting, a sovereign region, a sovereign cloud: the offers differ in detail and agree on one promise, that the data and the compute stay inside a border and under its law. That is worth having. It answers the half of legal control a regulator can make you solve, which is why regulators ask for it and why vendors sell it.
It says nothing about the other three controls. Who operates the system day to day, and whom they answer to. Who holds the encryption keys, the credentials and the update mechanism, and whether the system keeps working when its foreign dependencies are cut. Who decides what the model can do, what it becomes next, and whether it keeps running at all. Hosting is silent on all three, and a vendor's sovereignty page usually is too.
02The Frankfurt example
Every box ticked. Control not started.
In March 2024 a European bank's chief information security officer asked us, "We store all our data in Frankfurt. We're sovereign, right?" Every box was ticked. Foreign contractors ran daily operations, the orchestration layer depended on a cloud service, and there was no path to model updates. On the Sovereignty Maturity Index the bank scored 14 out of 30: compliance-driven. Location had been solved. Control had not been started.
Read the other way, the test is not an argument against the cloud. A tenancy you control, with your keys, your choice of model, your update schedule and a tested path to leave, can pass inside a hyperscaler. A subscription you cannot leave fails in your own data centre. The test never asks where the software runs. It asks who can switch it off.
03Three questions
Put these to the vendor, and time the answer.
- Access
Who can read the system and the data without our consent? Name them: the operator, the subcontractor, the court that can compel them.
- Modify
Who can change the model, the weights or the update schedule without us? If the answer is "the provider, on their release cadence", the model is theirs.
- Terminate
Who can end the service, and what runs the morning after? A tested answer is a system that was switched to another model or another host and worked.
If any answer is the vendor's own name, the offer is hosting, not sovereign AI. Score it on the six statements and the band will say the same thing in a number.
04Cite
Naraindas, P. and Bijlani, V. (2026). Own Your AI: The Sovereign Stack Playbook for Nations and Enterprises. Chapter 2, "The Sovereignty Test". Canonical page: premnaraindas.com/sovereignty-test.
This page answers one question from the test. The definition, the four dimensions and the scorer are on the Sovereignty Test page.