Digital Sovereignty
The ability of a state or organization to control its digital infrastructure, data and dependencies, free from extraterritorial coercion. US hyperscalers hold ~70% of Europe's cloud.

Digital sovereignty is the ability of a state, an organization or a territory to control its digital infrastructure, its data and its technological dependencies — free from extraterritorial coercion (Cloud Act, sanctions, a provider strategically pulling the plug). It isn't a binary status but a multi-axis vector: data, operational, technological, capital, political. In 2025, US hyperscalers hold about 70% of the European cloud market, and most generative AI is concentrated in a handful of US players (OpenAI, Anthropic, Google). Europe's response is taking shape around SecNumCloud (ANSSI, 13 qualified providers in November 2026), GAIA-X, the EU AI Act and the €180M sovereign cloud tender awarded by the European Commission in April 2026.
The 5 axes of digital sovereignty
Sovereignty isn't an attribute; it's a risk exposure you measure axis by axis.
| Axis | Operational question |
|---|---|
| Data | Can my data be read or seized by a foreign jurisdiction through a legal request? |
| Operational | If my provider cuts me off tomorrow (sanctions, bankruptcy, strategic decision), do I grind to a halt? |
| Technological | Who controls the chain — chips, model weights, frameworks? If it closes, do I have a credible local alternative? |
| Capital / IP | Who holds strategic control of the company (capital, patents, governance)? Which jurisdictions apply to those shareholders? |
| Political / values | Does the system carry the values or biases of another frame of reference (censorship, alignment, narrative)? |
The useful question isn't "is it sovereign?" but "on which axis can I not afford a dependency, and which option protects me on that axis?". The five axes can never all be maximized at once — there's always a trade-off to make, and it varies by sector (healthcare, defense, finance, retail, media) and risk profile.
Regulatory framework
The US Cloud Act (2018) requires any provider under US jurisdiction (AWS, Microsoft, Google, but also Cloudflare, Datadog, GitHub, etc.) to hand over the data it hosts to US authorities, even when that data is physically located in Europe. It overrides local laws and requires neither notifying the person concerned nor a court procedure in the hosting country.
On the European side, the GDPR (2018) governs the collection, processing and transfer of personal data, but doesn't address infrastructure sovereignty. The CJEU's Schrems II ruling (2020) invalidated the Privacy Shield, recognizing that data transfers to the United States could not be presumed compliant because of the Cloud Act and FISA 702. The EU AI Act (2024) adds a layer for general-purpose AI (GPAI) systems, with stricter obligations for models that pose a systemic risk.
At the national level, the SecNumCloud framework from ANSSI (France's national cybersecurity agency) requires the cloud provider to be immune to non-European laws: EU hosting, EU staff, majority European ownership, legal isolation from the group's non-European entities. As of November 19, 2026, according to ANSSI's catalog, 13 providers hold at least one qualified offering (Cegedim, Cloud Solutions (Wimi), Cloud Temple, Ecritel, Index Education (Pronote, Hyperplanning, EDT), NumSpot, OVHcloud, Oodrive, Orange Business, Outscale, Thales (S3NS), Whaller, Worldline). Others, such as Bleu and Scaleway, are still going through qualification.
Turning sovereignty into a decision tool
Whatever the type of organization — private company, mid-size firm, scale-up, public administration, nonprofit — the useful approach is the same: turn a slogan into an operational decision grid.
1. Classify data and workloads by sensitivity. Not everything needs to be sovereign. A marketing video library can live on a US hyperscaler without risk; customer, HR, intellectual property or financial data call for closer scrutiny. Three or four sensitivity levels (public / internal / confidential / regulated) are enough to frame decisions.
2. Map each workload onto the 5 axes. For each workload, identify the axis that dominates the risk. An R&D database = technological and IP axes are critical. A CRM = data axis is critical. An internal support SaaS = less critical axes. This grid avoids both over-compliance (moving everything to SecNumCloud on principle, at high cost with no benefit) and under-compliance (everything on AWS without a second thought).
3. Demand reversibility and transparency. The capital and operational axes are managed through contracts: data-location commitments, tested reversibility clauses, access to sovereign access logs (who read my data?), documented exit plans. A provider that refuses these clauses signals its own lack of sovereignty.
4. Diversify without adding complexity. Multi-cloud on principle is expensive. Multi-cloud for critical workloads (a primary plus a secondary under a different jurisdiction) is a relevant sovereignty lever — lock-in with a single vendor remains the most common mistake.
For a public body, the additional lever is public procurement: more than €230 billion in public contracts recorded in France in 2024, according to France's public procurement observatory (OECP), can pull demand toward sovereign solutions. For a private company, it's operational risk (Cloud Act, sanctions) that justifies the investment, not a flag-waving argument.
Limits and open debates
The pursuit of absolute sovereignty is impossible: NVIDIA keeps a near-monopoly on high-end GPUs, ASML holds the monopoly on EUV lithography, and no European player can compete with OpenAI or Anthropic on foundation models at scale. The debate pits two schools against each other: advocates of open strategic autonomy (working with trusted partners while building alternatives in critical segments) and those of strong sovereignty (absolute priority to local players, even at the cost of a technology gap). In practice, most European public strategies take the first approach, concentrating strict requirements on the most sensitive segments (sovereign cloud, digital identity, health data).
Standards and Specifications
GDPR (General Data Protection Regulation)
EU Regulation 2016/679, in force since 2018. Governs the collection, processing and transfer of personal data from the EU — including transfers to third countries (Schrems II, 2020)
Cloud Act (US)
2018 US federal law requiring US cloud providers to hand over data to US authorities, even when it's hosted outside the United States. Creates a direct conflict with the GDPR
EU AI Act
EU Regulation 2024/1689 on AI, in force since August 2024. Classifies AI systems by risk level and imposes specific obligations on general-purpose AI (GPAI) models
SecNumCloud (ANSSI)
French qualification framework for sensitive cloud services, issued by ANSSI (the national cybersecurity agency). Requires EU hosting, EU staff, majority European ownership and legal isolation from non-European laws
NIS2
EU Directive 2022/2555 on cybersecurity, being transposed into French law through the Resilience Act (loi Résilience, passed on first reading by the National Assembly on November 17, 2026). Extends obligations to 18 critical and essential sectors
Frequently Asked Questions
Is a foreign open-source LLM hosted locally sovereign?
It depends on the axis. A model such as Qwen, DeepSeek or GLM hosted on on-premise infrastructure in Europe offers strong data sovereignty (no Cloud Act exposure, no phone-home if the deployment is under control) and strong operational sovereignty (you have the weights, you serve them independently of the country of origin).
On the other hand, technological sovereignty is weak: if the publisher stops releasing open versions, or if its home jurisdiction blocks exports, you're stuck on the version you have. Capital sovereignty is zero (no value captured locally, no jobs, no ecosystem). Political/values sovereignty is risky: alignment biases reflect the training context (censorship, narratives, cultural norms), often invisible on business prompts but detectable on geopolitical or ethical ones.
Acceptable for short-term tactical use, problematic as an organization's multi-year foundation.
Is a European LLM with majority US shareholders sovereign?
Take Mistral: highly international capital, with a Series C led by ASML in 2025 followed by a €3 billion Series D led by Samsung in September 2026 (valuation of more than €21 billion), and a strategic compute partnership with Microsoft Azure since February 2024, along with a €15M investment from Microsoft. Partly open models (Mistral 7B, Mixtral), with the team and training based in France.
Technological and political/values sovereignty is strong (open models, French team, an explicitly European alignment). Data sovereignty depends on the deployment: Azure EU or self-hosted = good, Azure US = exposed to the Cloud Act. Capital sovereignty is medium-to-low: significant US capital, hybrid governance, a real OFAC risk if the US decides to sanction a customer. Operational sovereignty is medium: Microsoft is a critical compute partner.
Better than GPT-4 on most axes, but not equivalent to a 100% European player on capital and operations.
Does the GDPR guarantee digital sovereignty?
No. The GDPR is a framework for personal data protection, not sovereignty. A European company hosted on AWS Frankfurt can be GDPR-compliant while still being exposed to the Cloud Act: US authorities can request the data from AWS, which must comply even if the servers are physically in Germany. This duality was recognized by the CJEU in its Schrems II ruling (2020), which invalidated the Privacy Shield. Digital sovereignty requires combining the GDPR + an operational framework (SecNumCloud, EUCS) + control over the provider's ownership.
What's the difference between SecNumCloud and a standard public cloud?
SecNumCloud is an ANSSI framework requiring the provider to be immune to non-European laws. It mandates: (1) physical hosting in the EU, (2) staff and operations in the EU, (3) majority European ownership with a transparent shareholder structure, (4) encryption and operations isolated from the group's non-European entities.
AWS Frankfurt isn't SecNumCloud (US ownership). S3NS (Thales, running Google Cloud technology) obtained qualification in December 2025 with a legally isolated entity; Bleu (Capgemini and Orange, running Microsoft technology) is now targeting qualification by the end of 2026. As of November 19, 2026, 13 providers hold at least one qualified offering. French government doctrine recommends a SecNumCloud-qualified cloud for the most sensitive data.