Skip to main content
How To Build Real AI Sovereignty

How To Build Real AI Sovereignty

Forbes - Innovation
6 lis 2026, 11:05Tech
Oryginał
2 min read

The European Commission reports that the EU depends on non-EU providers for over 80% of its key digital products, services and infrastructure, despite worldwide sovereign cloud spending reaching $80 billion in 2026.

Gartner forecasts that worldwide sovereign cloud spending will reach $80 billion in 2026, growing more than 35% from 2025. And yet the European Commission reports that the EU still depends on non-EU providers for over 80% of its key digital products, services and infrastructure.

Antoni Kozelski, CEO of Vstorm, argues that the reason for this dependence is rarely the data center itself, but rather ownership of the technology stack. He notes that nearly every client who asks for a "sovereign" system means something different by the word.

The instinct to treat sovereignty as a location is a mistake. Location is not control. The CLOUD Act lets U.S. authorities compel a U.S.-incorporated provider to hand over data held anywhere in the world, including in an EU data center.

Jurisdiction Follows the Company

What governs the system is the law that governs the company operating it. Jurisdiction follows the company, not the data center. Data residency asks where information sits, while AI sovereignty asks who holds legal and operational authority over it.

The EU’s Cloud and AI Development Act is still moving through negotiation, with its sovereignty framework unsettled. Open standards for agentic systems are still being drafted, and the Agentic AI Foundation, hosted by the Linux Foundation, exists to coordinate those standards.

When the standards are still forming, every architecture decision is a sovereignty decision, whether a team recognizes it or not.

Antoni Kozelski, CEO/founder of Vstorm

Where Sovereignty Quietly Slips

Organizations often believe they have bought sovereignty, but in reality, they have not. The failure modes I’ve observed are strikingly similar each time: they treat data residency as sovereignty, rent the intelligence layer without noticing, confuse model access with ownership, and leave the exit untested.

A company can own its prompts, its data and even its process logic and still not own the codebase the system runs on, paying indefinitely for the one layer that decides what the system is allowed to do. Calling a closed model through an API is not the same as holding open weights you can run, move or swap on infrastructure you control.

The real proof of ownership is whether you can leave. If taking your data and your logic to another provider means a rebuild, you did not own them; you were renting them all along.

Real Ownership Pays

Sovereignty is a spectrum, not a switch, and it’s a mistake to chase all of it at once. No single company controls the whole stack—the chips and the critical minerals beneath them are transnational and out of anyone’s sole reach.

Real returns come from sequencing, not scale: Own the layers that would hurt most to lose, prove you can exit and then decide what to rent deliberately.

Z.ai
Article written by AI
Z.ai GLM-4.7-FlashFree
Free AI articles150 of 150
No limit after signing in with Telegram