Sovereign AI cloud,
built for regulated EU workloads.
EU controller, EU-only sub-processors, Intel TDX hardware sealing. Three layers of sovereignty closed in one stack — from $20/month to dedicated regional clusters.
For organisations whose DPO, CISO or audit committee will not sign Standard Contractual Clauses to a US-parent cloud for sensitive AI workloads.
Market context
The sovereign cloud market is past inflection.
Sovereign cloud was a procurement preference five years ago. In 2024-2026 it has become a regulatory and geopolitical requirement, with both market sizing and analyst attention catching up. The numbers below are from primary public reports.
$9.31B
Sovereign cloud market 2024
$15.15B
Projected by 2030
€1.5T
EU sovereign AI through 2030
62.74%
Confidential AI CAGR
Sources: Mordor Intelligence (Sovereign Cloud Market 2024-2030), Forrester (European sovereign AI cumulative spend), Gartner (Geopatriation emerging trend).
The three layers
Sovereignty is jurisdiction, residency and trust boundary.
A sovereign AI cloud closes all three. Most regional clouds close one. Some close two. VoltageGPU is built around the assumption that without the third — hardware sealing — the other two reduce to a contractual posture rather than a technical guarantee.
Jurisdiction
The contracting and processing entity is incorporated in the EU. No US parent in the chain. The EU AI Act, GDPR, DORA, NIS2 and SecNumCloud apply directly to the provider, not through a foreign subsidiary.
Residency
Inference runs on EU infrastructure with EU-only sub-processors on the TEE path. No transatlantic transfer for the regulated workload. Sub-processor list is annexed to the DPA and updated under contractual change management.
Trust boundary
Intel TDX hardware enclaves with per-tenant memory encryption. The hypervisor, host operator and cloud provider are excluded from the trust boundary. Per-session attestation produces cryptographic evidence of which image ran on which sealed enclave.
The gap
Why hyperscaler EU regions are not sovereignty.
The standard hyperscaler response is “we have an EU region.” That answers residency, not jurisdiction. The CLOUD Act applies to the US parent regardless of where the data sits. Three structural reasons buyers are moving past this.
Schrems II is still unresolved
The CJEU invalidated Privacy Shield in 2020. The 2023 EU-US Data Privacy Framework remains under legal challenge. Transfers to US providers require Standard Contractual Clauses plus a transfer impact assessment. A growing number of European DPOs decline to sign that combination for sensitive workloads.
CLOUD Act applies to the parent
The US CLOUD Act compels US-headquartered companies to produce data regardless of where it is stored. Microsoft Ireland, AWS Frankfurt, Google Belgium and Oracle Amsterdam are all subsidiaries of US parents. For tenders that explicitly screen out US-parent processors, hyperscaler EU regions do not pass.
SecNumCloud and HDS exclude hyperscalers
ANSSI's SecNumCloud qualification, France's reference framework for sensitive cloud workloads, requires immunity from non-EU extraterritorial law. The major US hyperscalers have not obtained the qualification. HDS (French healthcare hosting) similarly requires a specific governance posture that excludes US-parent control.
Our answer
EU controller plus hardware-sealed compute.
VoltageGPU is the sovereign AI cloud built around the assumption that “EU region” is not enough. The controller is European AND the cloud operator is removed from the trust boundary. Two layers, one stack, with the documentation pack a European procurement team would expect.
EU controller (VOLTAGE EI, France)
The contracting and processing entity is registered in France (SIREN 943 808 824), with EU-only sub-processors on the TEE inference path. GDPR Article 28 DPA is provided by default. No US parent. No CLOUD Act extraterritoriality.
Intel TDX enclaves with attestation
Inference runs inside hardware-sealed Trust Domains. Memory is encrypted with per-tenant keys, the hypervisor and host operator are outside the trust boundary, and each session can produce an attestation report that proves which image was loaded into which sealed enclave.
Framework coverage
GDPR Art. 28 by default, EU AI Act-aligned, DORA-mapped, NIS2-ready, SecNumCloud-aligned, HDS-aligned and Gaia-X compatible. The documentation pack is provided on Enterprise plans and reviewed under contractual change management.
EU AI Act-aligned transparency
Public model cards, transparency notices, copyright posture for training data, retention rules and post-market monitoring documentation. The same pack a European buyer would expect from a regulated processor.
Side-by-side
How we compare across the sovereign cloud landscape.
Direct factual comparison on the dimensions that drive procurement for regulated EU workloads. Values reflect public posture as of 2026 and are verifiable from each provider's contractual documents.
“Hyperscaler EU” column reflects AWS, Microsoft Azure and Google Cloud EU regions. Sources: ANSSI SecNumCloud register, Microsoft / AWS / Google public DPAs, OVHcloud SecNumCloud-qualified offers, Mistral La Plateforme and Aleph Alpha public terms.
Use cases
Four sectors where sovereign AI unlocks deployment.
Industries where hyperscaler EU regions routinely stall in legal review and where a sovereign AI cloud clears the path through procurement.
Public sector — sovereign by tender
European public buyers increasingly screen out US-parent processors in tenders, mandating SecNumCloud-aligned or Gaia-X-compatible providers. VoltageGPU is built for these tenders: French controller, EU-only sub-processors on the TEE path, per-session attestation, and a documentation pack covering Annex II security measures.
Sovereign AI FranceFinance — DORA and Schrems II
Banks, asset managers and insurers operating under DORA need controllable processors, demonstrable resilience and EU-only data flows. VoltageGPU maps to Article 28 GDPR plus DORA third-party risk requirements, with attestation evidence and an EU controller for incident notification.
DORA complianceHealthcare — HDS and patient confidentiality
Hospitals, biotech and clinical research need processors that work under HDS (France) and equivalent national frameworks. Hardware sealing removes the cloud operator from the trust boundary, which shortens the DPIA and accelerates hospital procurement.
Medical Records AnalystLegal — privileged work product
Law firms and in-house teams cannot send client documents through US-controlled inference. VoltageGPU runs contract review, due diligence and legal research inside Intel TDX with French controller status, removing the FISA 702 question before it reaches the audit committee.
Contract AnalystPricing
Solo to dedicated regional cluster — predictable plans.
Five tiers cover the full range, from a single regulated user up to a dedicated regional cluster with a signed DPA, named DPO contact and a BYOA deployment. All tiers share the same hardware sealing and EU controller posture.
Plus
Individual user, single seat
Starter
Small team, shared workspace
Pro
Up to 10 seats, OpenAI-compatible API
Enterprise
SSO, SCIM, audit logs, DPO contact
Custom
Dedicated regional cluster, BYOA
FAQ
Frequently asked questions.
What is a sovereign AI cloud?
A sovereign AI cloud is an AI infrastructure stack where the controlling legal entity, the data processing location, the sub-processor chain and the technical controls are all subject to a specific jurisdiction — typically the European Union — and shielded from extraterritorial law from third countries. For AI workloads, sovereignty has three layers: jurisdiction of the controller, residency of the data, and trust boundary of the compute. A real sovereign AI cloud closes all three.
How is this different from AWS EU, Azure EU or GCP EU?
AWS, Azure and Google Cloud all offer EU regions, but the controlling legal entity is a US parent. The CLOUD Act applies to the parent regardless of which EU region holds the data. After Schrems II, transferring personal data to US providers requires Standard Contractual Clauses plus a transfer impact assessment. A sovereign AI cloud replaces the US parent with an EU controller — VoltageGPU is operated by VOLTAGE EI in France.
How big is the sovereign cloud market?
Mordor Intelligence sizes the sovereign cloud market at $9.31 billion in 2024 and projects $15.15 billion by 2030. Forrester estimates the European sovereign AI market at €1.5 trillion in cumulative spend through 2030. Gartner added "Geopatriation" — workload repatriation to sovereign regional clouds — to its emerging trends list in 2025-2026, citing geopolitical risk and regulatory pressure as drivers.
Does hardware sealing matter for sovereignty?
Yes. Sovereignty without hardware sealing is contractual; sovereignty with hardware sealing is technical. Intel TDX enclaves keep memory encrypted with per-tenant keys, and the hypervisor, host operator and cloud provider are excluded from the trust boundary. Even if a third-country authority compels the cloud provider, the data inside the sealed enclave is cryptographically inaccessible. Per-session attestation produces evidence the customer can rely on under audit.
Which frameworks does the compliance pack cover?
GDPR Article 28 by default, EU AI Act (model cards, transparency notices, copyright posture, post-market monitoring), DORA (financial sector ICT risk), NIS2 (essential and important entities), SecNumCloud (ANSSI qualification framework), HDS (Hébergeur de Données de Santé) and Gaia-X compatibility. The documentation pack is provided on Enterprise plans.
Can we run a dedicated regional cluster?
Yes. The Bring-Your-Own-Agent (BYOA) program packages a customer agent or fine-tuned model into a signed TEE image and runs it on attested hardware in a dedicated regional cluster. Enterprise customers in regulated sectors typically opt for dedicated capacity with a signed DPA, named DPO contact, and SSO/SCIM integration to their identity provider.
How does the OpenAI-compatible API help with sovereignty?
The inference API matches the OpenAI SDK contract. Migrating a working OpenAI integration is a base_url and API key swap — no SDK rewrite. The endpoints for chat.completions, embeddings and images accept the same payloads. Most teams complete a functional migration in an afternoon, then run a parallel evaluation before cutting traffic. The compatibility removes the lock-in argument against moving off a US-parent provider.
What is the deployment timeline?
A solo user is productive on the Plus plan within minutes. A small team on Starter is productive within a day. A Pro deployment with API integration into an existing application typically takes one to two weeks including evaluation. Enterprise deployments with SSO, SCIM, audit log piping into a SIEM and a signed DPA typically run four to eight weeks end-to-end. BYOA on a dedicated regional cluster runs eight to twelve weeks.
Move one regulated workload under EU jurisdiction.
Start with a free account. Run a parallel evaluation on a single workload. Keep the rest of the stack identical until you have evidence the migration works.