Six weeks ago, at the World Governments Summit in Dubai, Nvidia's chief executive told an audience of ministers that every country needs to own the production of its own intelligence. The phrase he used was "sovereign AI", and it has moved through policy circles since at a speed that has very little to do with the underlying engineering.
Where the phrase came from matters, because the provenance is the argument.
The phrase has a vendor's fingerprints on it¶
"Digital sovereignty" is an older idea with a real constituency. European data protection authorities have been making it for a decade, and it is mostly about jurisdiction: whose courts can compel disclosure, whose law governs a transfer, which regulator you can actually call. That argument is about legal exposure and it is usually made by lawyers.
"Sovereign AI" is a newer construction, and it was not introduced by a regulator. It entered general circulation on an Nvidia earnings call in November 2023 and reached ministers in February. The content of the phrase, as it is being used, is that a nation must build domestic capacity to train and run models on hardware it controls.
Notice what that does. The older sovereignty argument was about who can compel you. The new one is about what you have bought. The first has an answer that might be "change the contract" or "move the data" or "accept the risk and write it down". The second has an answer that is a purchase order.
We have no quarrel with a country wanting domestic compute. The objection is narrower: the definition currently in circulation makes a vendor's product the measure of a national capability, and that definition was supplied by the vendor.
What the pitch leaves out¶
Four dependencies sit between a sovereign AI programme and anything a minister could call sovereign. None of them is addressed by buying accelerators.
The accelerators themselves. A datacentre full of hardware from one company in one jurisdiction remains a dependency. If the chips, the firmware, the interconnect and the driver stack come from a single foreign supplier, the question "what is our position if this is withdrawn" has the same answer it had before the money was spent. It may well be a better answer than renting the same hardware from a hyperscaler, since the asset is on your soil and nobody can switch it off remotely. Owning a dependency still leaves you dependent.
The software that makes them useful. CUDA is the dependency that the hardware conversation keeps eliding. A national programme that trains on this hardware produces artefacts, skills and tooling bound to one company's proprietary software environment. There are portable alternatives, and they are behind. That gap is the lock-in, and it does not appear on the invoice.
Export control. An accelerator's availability is set by the exporting government, in units of processing power, revised when it chooses. A capability whose supply can be restricted by another state's licensing decision is a capability held at that state's discretion. This has already happened, and not only to adversaries: allied purchasers have found their orders reclassified. A sovereignty programme that depends on an export licence is a sovereignty programme with a foreign veto.
The weights. Most of what is being called sovereign AI is a national deployment of a model trained elsewhere, on data assembled elsewhere, with alignment decisions made elsewhere. The compute is domestic; the artefact is not. A country that can run a model it cannot inspect, retrain or reproduce has bought a hosting arrangement.
The test we would apply¶
Our usual question works here with no modification. Which of these capabilities could be withdrawn or compelled by a party outside our control, and what is our position if that happens?
Run it over a sovereign AI proposal and the answers are uncomfortable but useful:
- If the export licence lapses, can we still expand? Usually no.
- If the proprietary software stack changes its terms, what is the migration cost? Usually unmeasured.
- If the model's originator stops publishing weights, do we have a reproducible path to the current one? Usually no.
- If the vendor's roadmap moves, is our programme stranded? Ask the people who standardised on a single storage vendor.
A programme that can answer those has done the work. A programme that has bought a lot of hardware has bought a lot of hardware.
What would actually move the needle¶
Three things, none of them as photogenic as a ribbon-cutting at a datacentre.
Reproducible training. Published data provenance, published recipe and enough detail that an independent party can produce an equivalent model. That is what turns a delivered artefact into a capability you hold. It is also the part no vendor has an incentive to fund.
Portable software. Work that runs on more than one supplier's silicon. The alternatives being behind is a reason to invest in them, not a reason to deepen the dependency. A national programme is one of the few buyers large enough to change that calculus.
Dependency accounting, written down. Every sovereignty claim should be accompanied by the list of things that could be withdrawn and by whom. That list belongs in the programme's published specification rather than in a risk register nobody reads, because a dependency you have named is one you can plan around.
Why this matters beyond AI¶
The pattern has a history, which is why we are writing this down now rather than waiting to see how the programmes work out.
A technology arrives. It has a real sovereignty dimension. A supplier supplies the vocabulary for discussing it, and the vocabulary is shaped so that the supplier's product is the solution. The cloud argument went this way. "Sovereign cloud" came to mean a local region operated by the same company under the same parent jurisdiction, which addressed the data-residency question and left the control question exactly where it was.
The accelerator version of this will be harder to unwind, because the capital commitment is larger and the alternatives are further behind. The useful move, for anyone specifying one of these programmes, is to insist on a definition that was not written by a party with something to sell.
Sovereignty describes your position when a supplier changes its mind. An inventory of hardware says nothing about that position on its own.