“Sovereign AI” has gone from a policy buzzword to a procurement requirement in under two years. The short definition: an organisation has sovereign AI when it controls the three things that matter, the model, the data it processes, and the infrastructure it runs on, without depending on a third party who can change the terms, read the inputs, or switch the service off.

That sounds obvious until you look at how most enterprises consume AI today. A prompt typed into a cloud assistant leaves the building, is processed on infrastructure the customer never sees, under a contract that can be revised, and is often retained for some period for abuse-monitoring or training. For a marketing team that trade-off is fine. For a hospital, a law firm, a bank, or a defence contractor, it is frequently a non-starter.

The three layers of sovereignty

It helps to be precise, because vendors use the word loosely. True sovereignty has three independent layers, and a deployment is only as sovereign as its weakest one:

  • Data sovereignty, your inputs, outputs and documents physically stay on hardware you control and are never transmitted to a third party.
  • Model sovereignty, you can inspect, pin, and keep running the exact model you deployed, regardless of a vendor deprecating or altering it.
  • Operational sovereignty, the system keeps working without phoning home, even fully air-gapped, and you decide when and whether to update it.

A “private” cloud endpoint typically gives you the first layer on paper and none of the others. A downloaded open-weights model gives you model sovereignty but leaves you to solve operations, governance and security yourself. Sovereign AI as a product category is the attempt to deliver all three at once.

Why now

Three forces are converging. First, regulation: the EU AI Act, GDPR enforcement, sector rules like DORA and NIS2, and national data-residency expectations have made “where does the data go?” a board-level question. Second, capability: open-weights models are now good enough that a self-hosted assistant is genuinely useful for drafting, summarising and document Q&A, the gap to frontier cloud models has narrowed for everyday enterprise tasks. Third, economics: per-seat cloud AI pricing scales linearly with headcount, while owned hardware is a fixed cost that the organisation keeps.

“The question has quietly flipped. It used to be “why would we run AI ourselves?” Now, for regulated buyers, it is “why are we still sending this data to someone else?””

What sovereignty is not

Sovereignty is not isolationism, and it does not mean giving up a modern experience. A well-built sovereign platform still offers streaming chat, retrieval over your own documents, image understanding, an admin console and an API, it simply runs them on metal you control. Nor does sovereignty mean “air-gapped or nothing”: most organisations run connected for convenience and reserve full network isolation for their most sensitive workloads. The point is that the choice is yours to make and to change.

A useful test: if your AI vendor went out of business tomorrow, or doubled their price, or was compelled to hand over logs, would your AI capability survive intact? If the answer is no, you do not yet have sovereign AI.

Who needs it first

Adoption is led by the organisations with the least room to be wrong about data handling:

  • Healthcare, patient data under GDPR Article 9, MDR/IVDR and the emerging European Health Data Space.
  • Legal, privilege and client confidentiality that cannot survive a third-party processor.
  • Finance, DORA, supervisory expectations and the sensitivity of transaction and client data.
  • Defence and public sector, classification, national sovereignty and air-gapped environments by default.

What these sectors share is that the cost of a data-handling mistake is measured in licences, lawsuits and lives, not churn. For them sovereignty is the baseline, and a capable assistant on top of it is the prize.

Getting there

The practical path is less daunting than it sounds. Sovereign AI runs on commodity GPU servers or even capable CPU nodes for smaller models; it installs in minutes rather than requiring a Kubernetes platform team; and the governance, isolation and compliance tooling that regulated buyers need can ship in the box rather than being assembled from a dozen projects. That is the bet Kaldryn is built on, and the rest of this research hub goes deeper on each layer, from reference architectures to EU AI Act compliance.