Executive Summary
Running a workload in an EU data center is not the same as operating independently of non-EU jurisdictions. For sovereignty, the important questions are not only where the infrastructure is physically located, but also who owns, controls and operates it, which legal regimes apply to the provider, and whether a third-country government could materially affect continued access.
If AI becomes critical enterprise infrastructure, jurisdictional resilience should be treated as a business-continuity concern rather than merely as a data-residency or procurement issue.
Hosting Location and Jurisdiction Are Different Things
Cloud providers increasingly offer products described as EU sovereign, European sovereign or sovereign cloud. These offerings can provide real controls, including EU data residency, locally operated infrastructure, restricted administrative access, EU-based personnel, encryption and key-management controls, and contractual commitments around support and operations.
Those controls matter, but they do not by themselves establish jurisdictional independence. A service can be physically hosted and operationally isolated in Europe while the ultimate provider, parent company, software supply chain or control structure remains subject to another jurisdiction.
The practical sovereignty test is therefore whether geopolitical, legal or trade changes in a third country could materially affect access to the service.
Europe Is Beginning to Distinguish Levels of Sovereignty
The European Commission’s current Cloud and AI Development Act framing is useful because it separates physical location from deeper forms of sovereignty. The proposed framework describes four levels:
-
Level 1 — data is processed and stored in infrastructure located in the EU.
-
Level 2 — providers must demonstrate independence from third countries and transparency over their software supply chain.
-
Level 3 — providers must be owned and controlled from the EU, with additional requirements.
-
Level 4 — providers provide full transparency and control over the software supply chain and no interference from a third country.
Source: European Commission — Cloud and AI Development Act
The important point is that physical location is only one dimension. Independence, ownership, operational control and freedom from third-country interference are separate considerations.
Data Residency Is Not Sovereignty
Data residency answers where data is stored and processed. Sovereignty is broader: who can access and operate the service, which legal regimes can compel the provider, who controls the software and infrastructure, and whether the service can continue if geopolitical relationships deteriorate.
European data-protection guidance following the Schrems II judgment already reflects this distinction by requiring organizations to consider whether laws and practices in a third country could prevent a provider from complying with European safeguards.
Source: European Commission — Standard Contractual Clauses and Schrems II
The same reasoning is relevant to strategic technology dependency even when the immediate issue is not personal-data transfer.
Sovereignty Is Also About Continuity
For organizations, the more important issue may be continuity of strategic capability rather than compliance alone. If AI becomes embedded in research, supply chain, commercial operations, software engineering and knowledge work, dependence on a single geopolitical technology ecosystem becomes a business risk.
The relevant scenario is not necessarily that a provider voluntarily chooses to stop serving us. Regulation, sanctions, export controls, national-security measures or broader geopolitical events can constrain what a provider is legally permitted to deliver. In that situation, contractual assurances about an EU-hosted region are only as durable as the legal and operational independence behind them.
This should therefore be framed as resilience rather than vendor distrust. The issue is whether strategically important AI capabilities should depend entirely on continued permission from one jurisdiction.
Architectural Implication
The answer is not to abandon US hyperscalers or frontier-model providers. We should use the best services available where they create value, while ensuring that strategically important AI capabilities have a credible path to alternative jurisdictions and providers if needed.
That implies designing for:
-
portable workloads
-
model independence where practical
-
open or replaceable interfaces
-
data portability
-
infrastructure portability
-
open models as a credible fallback
-
access to EU-controlled compute and inference
-
avoidance of dependencies that cannot be reproduced outside a single provider ecosystem
This is consistent with the EU Data Act, which pushes cloud providers toward interoperability, switching and open interfaces so customers can move between providers without losing data or functionality.
Sources:
Sovereign AI Should Be an Option, Not Necessarily the Default
This is not an argument that every workload should immediately run on European-owned infrastructure. It is an argument for maintaining a viable option.
If strong open models continue to close the capability gap with proprietary frontier models for many enterprise workloads, then a sovereign execution path becomes increasingly practical. That path could involve European-owned GPU infrastructure, European inference providers, open-weight models, managed or self-hosted open-model inference, European model providers, and workloads capable of moving between US, EU and other regional ecosystems.
The strategic value is that organizations would not need to create that capability from scratch after a crisis has already begun.
A Useful Test
For any service described as sovereign, ask what legal and operational mechanisms would prevent a government outside the EU from suspending, restricting or otherwise affecting the service through the ultimate provider. If the answer is only that the servers are located in Europe, then the service provides data residency; that alone does not establish jurisdictional independence.
Conclusion
Sovereignty is a spectrum, not a hosting-region label. Physical location, operational separation, personnel and key control all matter, but so do ownership, jurisdiction, software supply-chain control and the ability to operate independently of third-country intervention.
For strategic AI infrastructure, the objective should be to avoid single-jurisdiction dependency and preserve a credible path to continue operating critical AI capabilities under European legal and operational control if circumstances require it.
Hosting location ≠ jurisdictional independence.
