What is sovereign AI? A plain answer for UK businesses.
Sovereign means holding supreme or final power. Sovereign AI is AI where the final say over the model, the data and the computing power rests with the people it serves: the country whose law applies, the company that owns the work, and the individual the information is about. For a business, that means your client files, and the work done on them, stay where you decided, under your control, and you can prove it.
What sovereign AI means.
There is no single agreed definition of sovereign AI yet. Governments tend to mean national capability: in the UK, the Sovereign AI Unit is a £500m government-backed fund that invests in British AI companies, and the UK Compute Roadmap describes sovereignty as the ability to act independently and effectively where it matters most. Suppliers often mean where a server sits. We start from the word itself. A sovereign holds supreme or final power, so the question for any AI is who has the final say over three things: the model (the weights that do the reading and writing), the data (what goes in and what comes out) and the compute (the machines that run it).
Our answer is that the final say belongs to three parties, each over its own part: the country whose law applies, the company that owns the work, and the person the information is about. Each has a degree of control, a degree of residency and a degree of ownership.
Why UK professional services businesses are asking now.
Law, accounting and consulting run on information clients trust them with. Three duties already in force now reach the AI tools that information passes through.
Where your model can run: two options.
Both can be sovereign when they are set up properly. They differ in who carries the work, how fast you start and how the cost behaves. Neither is right for everyone.
| What to compare | Your environmentYour own servers or private cloud | Hosted by MindLynxIn the UK and EU by default |
|---|---|---|
| Who owns the hardware | You do, or your cloud provider under your own account. | We do, through named data-centre operators. The security pack lists each one. |
| Who patches it | Your team: operating systems, drivers and model servers. We supply updates to our software. | We do. |
| Who holds the keys | You do, in your own key store. | We manage them for the service. The security pack sets out how they are held and who can use them. |
| Time to first use | Longer. Capacity has to be in place, then installation and testing with your security team, with our engineers alongside yours. | Shorter. Our activation team connects your systems, and every connection starts read-only. |
| Cost shape | Hardware or reserved capacity paid for up front, plus your people to run it. The cost stays the same when usage falls. | A subscription. Every step has a budget and a price, agreed before it runs and shown after. |
| Upgrade path | You decide when to move to a new model or version, and you test it first. | We move to newer models. Every receipt names the model that ran, so a change is never hidden. |
| Audit evidence | Receipts are written inside your environment, into your own logs, where your auditors can read them. | A receipt for every step, which your auditors can read and you can export as plain files. |
| When a model is retired | Nothing is retired on you. Open-weight models you run stay on your servers until you replace them. | The work moves to another model your rules allow. What your business has learnt stays in Cortex, which is not tied to any one model. |
- You already run GPUs or a private cloud with spare capacity.
- The work is air-gapped or classified and cannot touch a network you do not control.
- A regulator, a client contract or your insurer requires it.
- Your security team must hold every key and patch every machine.
- You want to start on one problem without buying hardware.
- You have no team to run model servers.
- Your usage rises and falls through the year.
- Processing in the UK and EU, with named operators and a receipt for every step, meets your obligations.
You can start hosted and move into your own environment later. Your knowledge, playbooks and records export as plain files.
Sovereign AI in practice: we set it up with you.
Sovereignty is not only a policy question. It is also a choice about where your AI runs, and who controls it. MindLynx can host Albion for you in the UK and EU, or set it up inside your own environment and train it there on how your firm works. What it learns there belongs to you. Albion is in development, and we are building it with design partners now.
Control first. Then build.
Sovereignty is control, with a British lens. Part of being sovereign is being shaped by national experience, culture and beliefs, so that is how Albion is built: in this order, and in the open.
- 01 Control first Complete data residency and complete transparency, with data privacy law applied from day one. It will not be perfect, but nothing is lost by starting here, and everything after it inherits it.
- 02 Start from the models that exist The best open models available today give near-frontier capability from the start. We teach them through our own method: lawful data, models whose licences allow it, and people who teach with consent and fair pay. How people teach Albion →
- 03 Teach the British lens where it moves the needle Law, finance, health, public services and the institutions behind them: the places where British data, British practice and British culture make the biggest difference to the answer.
- 04 Train our own, scientifically In parallel, we are training our own model from scratch. We say what we will test before we test it, publish every result, including the ones we lose, and every model card names its base, its teachers and its scores.
- 05 A receipt for every step Every step records who asked, which rules applied, which model ran, where it ran and what it cost. We build in the open, so you can check the record rather than take our word.
What people ask about sovereign AI.
Need more for your due diligence? Our security pack covers our controls, the places we process data, our subprocessors and how we handle incidents.
Request our security packKnow where your AI runs.
Bring us the tools you use and the rules you answer to. We will show you where the work would run, in your environment or ours, and what the record looks like.
- GOV.UK: first backing through the UK's Sovereign AI Unit, 16 April 2026
- GOV.UK: UK Compute Roadmap, section 5.1
- SRA: Code of Conduct for Solicitors, paragraph 6.3
- SRA: warning notice on the misuse of AI, August 2026
- ICO: are we making a restricted transfer?
- Data (Use and Access) Act 2025 transfer provisions in force, SI 2026/82
- NCSC: Cloud Security Principle 2, asset protection and resilience
- GOV.UK: PPN 017, improving transparency of AI use in procurement
