Geopatriation:
move AI workloads under EU jurisdiction.
Geopatriation is Gartner's term for moving cloud workloads back from US-parent hyperscalers to sovereign regional clouds. For AI inference, that means migrating to EU-controlled, hardware-sealed infrastructure with per-session attestation.
Built as a destination for organisations whose DPO, CISO or audit committee is no longer comfortable with US-parent inference for sensitive workloads.
Definition
Geopatriation / ˈdʒiː.oʊ.peɪ.triˈeɪ.ʃən /
noun. The practice of moving cloud workloads back from globally distributed providers, typically US-parent hyperscalers, to sovereign regional clouds whose controlling legal entity is incorporated in the customer's regulatory zone. Driven by geopolitical risk, regulatory pressure (CLOUD Act, FISA 702, EU AI Act, DORA, NIS2) and the maturity of regional alternatives.
Coined by Gartner as part of its emerging-trends taxonomy. Distinct from cloud repatriation (cost-driven, 2018-2022), geopatriation is jurisdictional (2024-2030).
Market context
The destination market is past inflection.
Sovereign cloud is the receiving market for geopatriated workloads. The numbers below are from primary public reports and confirm that buyer behaviour is already shifting.
$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).
Drivers
Why geopatriation is accelerating in 2026.
Four compounding forces. Each on its own would push some workloads off US-parent providers. Together they make the trend structural rather than cyclical.
EU AI Act enforcement (Aug 2026)
General-purpose AI provider obligations apply from August 2026. Buyers prefer an EU controller who can respond directly under EU law, with model cards, transparency notices, copyright posture and post-market monitoring documentation. Hyperscaler EU regions do not change which legal entity is the controller.
DORA mandatory since Jan 2025
The Digital Operational Resilience Act became mandatory for the financial sector in January 2025. It requires controllable processors, EU sub-processor chains and demonstrable resilience. Banks, asset managers and insurers are reviewing US-parent third-party risk and accelerating workload moves to sovereign destinations.
Schrems II unresolved
The CJEU invalidated Privacy Shield in 2020. The 2023 EU-US Data Privacy Framework is under legal challenge. SCC plus a transfer impact assessment is the current default for US transfers, and a growing number of European DPOs decline to sign it for sensitive workloads. The legal uncertainty pushes geopatriation up the priority list.
Infrastructure maturity
Intel TDX, NVIDIA Confidential Computing on H100, H200 and RTX PRO 6000 Blackwell, and OpenAI-compatible inference APIs from EU controllers have reached production maturity. The lock-in argument against moving off a US-parent provider does not hold: SDK swap is a base_url change, and model quality on regulated workloads is within striking distance of GPT-4-class systems.
Compared
Cloud repatriation vs. geopatriation.
The terms sound similar. The drivers, buyers and destinations are different. Confusing the two leads to projects that solve cost when the audit committee was worried about legal exposure.
Project shape
A geopatriation project in four stages.
Typical run is four to twelve weeks per workload. The Inventory stage is the most informative, most organisations discover 30-60% more US-controlled AI usage than the CISO assumed.
Inventory
List AI workloads on US-parent providers, inference endpoints, agent flows, fine-tuned models. Capture traffic volumes, data sensitivity, SLAs and existing DPA terms. Most organisations discover 30-60% more US-controlled AI usage than the CISO assumed.
Mapping
Match each workload to a sovereign destination. Decide which can run on multi-tenant TEE inference (most chat completions, embeddings, image generation) and which need a dedicated regional cluster (high-volume agents, fine-tuned models, custom toolchains).
Parallel run
Mirror a representative slice of production traffic to the sovereign destination and compare outputs over an agreed evaluation window. Document differences, validate they are within tolerance, and capture the evaluation pack for the audit committee.
Cutover
Move traffic with a feature flag or percentage rollout. Keep rollback available until the metrics are stable. Decommission the US-parent endpoint, archive the DPA, and update the processor register with the new EU controller. Most workloads cut over in four to twelve weeks.
Destination
What VoltageGPU offers as a destination.
The destination side of geopatriation matters as much as the source. A sovereign destination has to clear procurement, satisfy the audit committee and not break the engineers' existing integration.
EU controller
VOLTAGE EI, France, SIREN 943 808 824. The contracting and processing entity is registered in France. No US parent. GDPR Article 28 DPA by default. EU AI Act applies directly.
Intel TDX enclaves
Inference runs inside hardware-sealed Trust Domains. Memory is encrypted with per-tenant keys, hypervisor and host operator are excluded. Per-session attestation produces cryptographic evidence.
OpenAI-compatible API
Migrating off OpenAI, Azure OpenAI, AWS Bedrock or Vertex AI is a base_url and API key swap in the existing SDK code. Chat completions, embeddings and images use the same payloads. Most teams complete a functional migration in an afternoon.
Framework coverage
GDPR Art. 28 by default, EU AI Act-aligned, DORA-mapped, NIS2-ready, SecNumCloud-aligned, HDS-aligned and Gaia-X compatible. Documentation pack provided on Enterprise plans.
FAQ
Frequently asked questions.
What is geopatriation, exactly?
Geopatriation is the practice of moving cloud workloads back from globally distributed providers (typically US-parent hyperscalers) to sovereign regional clouds. Gartner added it to its emerging-trends list to describe a structural shift driven by geopolitical risk, regulatory pressure (CLOUD Act, FISA 702, EU AI Act, DORA, NIS2) and the maturity of regional alternatives. For AI workloads specifically, geopatriation means moving prompts, training data and model deployments out of US-controlled inference into EU-controlled, attested infrastructure.
Is geopatriation just cloud repatriation rebranded?
No. Cloud repatriation in the 2018-2022 sense was a cost discussion, workloads moved on-premises to optimise TCO against hyperscaler list prices. Geopatriation is a jurisdictional discussion, workloads move to a sovereign regional cloud whose controlling legal entity is incorporated in the customer's regulatory zone. The buyer is the DPO, General Counsel and Audit Committee, not the FinOps team.
How big is the geopatriation market?
The sovereign cloud market, which is the destination for geopatriated workloads, is sized at $9.31 billion in 2024 by Mordor Intelligence and projected to reach $15.15 billion by 2030. Forrester estimates European sovereign AI cumulative spend through 2030 at €1.5 trillion. The confidential AI sub-segment is growing at a CAGR of 62.74%. Hyperscalers themselves are responding with sovereign cloud propositions, which confirms the trend.
Why is geopatriation accelerating in 2026?
Four compounding drivers. The EU AI Act phases general-purpose AI provider obligations in August 2026. DORA became mandatory for the financial sector in January 2025. Schrems II remains structurally unresolved with the 2023 EU-US Data Privacy Framework under legal challenge. And the maturity of EU sovereign infrastructure has reached production-grade, making the migration a configuration change rather than a rewrite.
What does a geopatriation project actually look like?
Four stages: (1) Inventory, list AI workloads on US-parent providers with traffic, sensitivity and SLAs. (2) Mapping, match each workload to a sovereign destination, deciding which can run on multi-tenant TEE inference and which need a dedicated regional cluster. (3) Parallel run, mirror traffic to the sovereign destination and compare outputs. (4) Cutover, move traffic with a feature flag, keep rollback available, decommission the US-parent endpoint once stable. Four to twelve weeks per workload.
Does geopatriation break model quality?
Not for most workloads. VoltageGPU runs Qwen3.5-397B-TEE and DeepSeek-V3.2-TEE inside the TDX enclave. On open benchmarks (MMLU, GSM8K, HumanEval, LegalBench, MedQA) these models score within striking distance of GPT-4-class systems. The trade-off is a small amount of marginal capability on the most exotic tasks against hardware confidentiality, EU jurisdiction and direct EU AI Act applicability. For regulated workloads, the trade is the right one.
Are hyperscalers responding to geopatriation?
Yes. Microsoft Cloud for Sovereignty, AWS European Sovereign Cloud and Google Cloud Sovereign Solutions are all responses to the same buyer signal. None of them, however, solves the US-parent problem: the controlling legal entity remains a US corporation, and the CLOUD Act applies to the parent regardless of which region holds the data. Geopatriation as a strict definition (EU controller, not just EU region) requires moving off the US-parent provider.
How does VoltageGPU fit a geopatriation strategy?
VoltageGPU is built as a destination for geopatriated AI inference. EU controller (VOLTAGE EI, France, SIREN 943 808 824), Intel TDX enclaves with per-session attestation, OpenAI-compatible API for drop-in SDK swap, a sub-processor chain documented in the DPA rather than claimed to be EU-only, and a documentation pack covering GDPR Art. 28, EU AI Act, DORA, NIS2, SecNumCloud and HDS. Plans run from $20/month to $5,000+/month with dedicated regional clusters and BYOA on the higher tiers.
Start with one workload. Geopatriate the rest after the evaluation.
A geopatriation pilot is a base_url swap and a parallel evaluation. No rewrite. Keep the existing OpenAI SDK code, point it at VoltageGPU, run a representative slice in parallel.