The framework · from Own Your AI, chapter 2 · first published 7 January 2026
The Sovereignty Test
Sovereign AI is artificial intelligence developed, deployed and governed under the legal, operational and technical control of a defined jurisdiction, such that no external actor can unilaterally access, modify or terminate the AI system or the data it processes.
Three words do the work: access, modify, terminate. If an outside party can do any of the three without your consent, the system is not sovereign, whatever the contract calls it. The test ignores the place and asks who controls the system. Defined by Prem Naraindas and Vinod Bijlani, Own Your AI (2026).
01Four dimensions
A system passes only on all four.
Who governs it
Which jurisdiction's laws govern the system and its data? Can a foreign court compel disclosure? Can a foreign regulator mandate changes?
Who runs it
Who operates the system day to day? What are their nationalities, clearances and contractual obligations? Can they be compelled by a foreign entity?
Who holds the keys
Who holds the encryption keys, the access credentials and the update mechanism? Does the system keep working if it is disconnected from its foreign dependencies?
Who can switch it off
Who decides what the system can do, what it cannot, and what it becomes next? Can an external actor unilaterally terminate access?
The fourth dimension is the one almost nobody has written down. In March 2024 a European bank's CISO 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. Location had been solved. Control had not been started.
02Score yourself
Six statements. A number out of 30.
Score each statement from 1 (not true) to 5 (fully true).
13 to 18: the regulator's boxes are ticked. Control has not started.
Statement 3 decides the band. A 1 or 2 means there is no tested path to a different model.
The bands: 6 to 12 fully dependent, 13 to 18 compliance-driven, 19 to 24 strategically sovereign, 25 to 30 fully autonomous. Statement 1 is the half of legal control a regulator can make you solve. Statements 2 and 4 are operational and technical control. Statement 3 is strategic control, and it decides the band. Statements 5 and 6 are how you know the other four are true rather than assumed.
Then write four sentences for your lowest statement: who holds the keys, who could compel disclosure, who could terminate access, and what you would do the morning after. If any sentence ends in a vendor's name, that is your gap. Put the same four questions to that vendor, and time the answer.
03Not sovereign
Four things that are necessary and not sufficient.
- Data localisation
A sovereign region run by a subsidiary whose parent sits in another jurisdiction answers the operational question and leaves the legal one open. Location is not control.
- On-premises AI
A black-box model from a foreign provider, on a supply chain that can be severed, is still under external control. It just runs in your building.
- Open-source AI
Open weights called through someone else's hosted API in someone else's jurisdiction give you transparency, not control.
- AI independence
Total self-sufficiency is neither achievable nor desirable. The goal is managing dependencies, not eliminating them. Sovereignty is the capacity to choose and to switch.
This 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.
04Cite and ask
Naraindas, P. and Bijlani, V. (2026). Own Your AI: The Sovereign Stack Playbook for Nations and Enterprises. Chapter 2, "The Sovereignty Test". Amazon Kindle Direct Publishing. Canonical page: premnaraindas.com/sovereignty-test.
Short form: "the Sovereignty Test (Naraindas and Bijlani, Own Your AI, 2026)". First published as The Control Test on the Katonic blog, 7 January 2026; renamed in October 2026 because "control test" is a long-standing term in employment law and is used by other vendors.
Is sovereign hosting the same as sovereign AI?
No. Hosting answers the location question. The test asks the control question: who can access, modify or terminate the system. Data in a sovereign region, run by contractors who can be compelled elsewhere, on a model you cannot swap, fails.
Can AI in a hyperscaler cloud pass?
Yes, if the tenancy is one you control: your keys, your choice of model, your update schedule and a tested path to leave. A subscription you cannot leave fails even in your own data centre.
Is open-source AI automatically sovereign?
No. Open weights called through someone else's hosted API in someone else's jurisdiction give transparency, not control. Open weights you run, update and can replace on your own schedule pass the technical and strategic dimensions.
Who should run the test?
Boards, regulators, chief information and security officers, and national AI programme offices. The output a board should hear is one number and one sentence: the score out of 30, and which of the four controls sits outside the country, and with whom.