What capability do you give up with sovereign AI?

Primarily access to the largest frontier models, which are generally available only as hosted services. Locally served open-weight models handle extraction, classification and retrieval-grounded generation well; the gap is wider on open-ended reasoning. Air-gapped deployment additionally forgoes automatic updates and external data sources.

Why does model independence matter for sovereignty?

Because data sovereignty without model independence leaves the institution dependent on a foreign commercial entity for continuity. If a provider changes terms, exits a market or becomes politically unavailable, workflows built on that provider's models stop. Independence means substituting models without rewriting the workflows.

Sovereign AI: A Guide for Regulated Enterprises

Q: Is sovereign AI the same as data residency?

No. Data residency concerns where data is stored. Sovereign AI additionally concerns where processing happens, who can access the running system, who holds encryption keys, and whether the deployment depends on a single external model provider. Residency is the weakest of these guarantees and the easiest to advertise.

Q: How do you verify a vendor's sovereignty claim?

Ask specifically where inference runs, whether content leaves for logging, monitoring or abuse detection, who holds encryption keys and admin credentials, under which jurisdiction those people can be compelled, and what the model substitution path is. Ask for the answers in writing. Precision in the answers is the signal.

This guide sets out what sovereignty actually requires at each layer of the stack, the four deployment topologies and what each genuinely costs, and the questions that separate a real sovereignty claim from a hosting arrangement with a national flag on it.

What sovereignty actually requires

A vendor can truthfully say "your data stays in-country" while several other things about the deployment remain entirely outside your control. Sovereignty is a property of the whole stack, and each layer can be sovereign or not independently.

Data residency: where the data sits at rest

The layer everyone means when they say sovereignty, and the easiest to satisfy. Necessary and nowhere near sufficient — data at rest in Singapore that is processed by a model serving from another region has not stayed in Singapore in any sense that matters.

Processing locality: where inference happens

Where the model actually runs when your data is in context. The question that resolves it: when a document is processed, does its content leave this facility for any purpose, including inference, logging, monitoring or abuse detection? Abuse-detection pipelines are the common exception clause — content is transmitted for safety scanning even where the primary inference is local.

Operational control: who can access the running system

Who holds administrative credentials, who can read logs, and under which country's legal process those people can be compelled. Data physically stored in one jurisdiction may still be reachable through legal process directed at a provider incorporated elsewhere — for government health agencies this frequently turns out to be the decisive consideration.

Key custody

Who holds the encryption keys, and can the provider decrypt without you. Provider-managed keys mean provider-accessible data regardless of where it sits. Customer-managed keys in customer-controlled hardware is a materially different position.

Model supply and independence

The layer most often ignored, and the one with the longest tail. The scenario worth planning for is not a technical failure — it is commercial or political: a provider changes terms, is acquired, exits a market, or falls out with your government. Model independence means the orchestration layer can route to different models, including locally served open-weight models, without the workflows being rewritten.

The four topologies

Deployment options, from least to most constrained. The right choice is per workflow, not per organisation.

Hosted with regional residency — the vendor's cloud, with data stored in a chosen region. Sovereign in the residency layer only.

Sovereign cloud with in-country tenancy — dedicated tenancy in national infrastructure with in-country processing and defined operational control. The common landing point for government health agencies and large pharma.

On-premise — inside your own data centre, on your hardware, behind your firewall. Strong across every layer; costs are real hardware, operational burden and an update path you own.

Air-gapped — no outbound connectivity at all. The strongest position and the most constrained, eliminating whole categories of risk rather than mitigating them, at the cost of frontier model access and automatic updates.

Where Eclypse sits: the platform supports all four topologies on the same orchestration layer, so a workflow's constraint decides its posture rather than the whole estate inheriting the strictest one. See AI for government health agencies for how this plays out in a sovereign deployment.

Verifying a sovereignty claim

Six questions, asked in writing. The precision of the answers is itself the signal: where does inference physically run; does content leave the boundary for any purpose; who holds the keys and the credentials; what happens if your model provider withdraws; can you substitute models without rewriting workflows; and what is the update path. Vendors who have genuinely built for this answer specifically; vendors who have not answer in adjectives.

Common questions about sovereign AI.

What is sovereign AI?

An AI deployment where processing happens within a defined jurisdiction, under the controlling organisation's authority, with the data not leaving that boundary. It spans data residency, processing locality, operational control, key custody and model supply.

Is sovereign AI the same as data residency?

No. Residency covers only where data is stored. Sovereign AI additionally covers where processing happens, who can access the system, who holds keys, and model-provider dependency.

Does sovereign AI mean air-gapped?

No. Air-gapped is the most constrained of four topologies — hosted with regional residency, sovereign cloud, on-premise, and air-gapped. Most institutions should run different workflows in different topologies.

How do you verify a vendor's sovereignty claim?

Ask where inference runs, whether content leaves for logging or abuse detection, who holds keys and admin credentials, and what the model substitution path is — in writing.

Sovereign AI