Sovereign AI Europe: checklist for companies 2026

TL;DR

Sovereign AI in Europe is a control stack, not a brand. Check location, operators, legal entity, keys and weights. Claude stays behind eu.anthropic.claude-sonnet-5-5 or Google aiplatform.eu.rep.googleapis.com. The Anthropic API has no eu value. Foundry documents no EU data zone. The AWS sovereign partition in Brandenburg is not commercial Bedrock EU geo.

What counts as sovereign AI in Europe?

Sovereign AI in Europe is five controls, not a product name. Residency says where inference runs. Sovereignty also asks who operates the site, which law binds the operator, who holds the keys, and who owns the weights. GDPR does not require an EU location. The AI Act does not require EU weights.

This is not legal advice. The provider matrix is in Claude GDPR compliance in Europe. How to pin Claude itself is in Claude data residency in the EU. The hosting tree (your GPUs, import, Claude EU) stays in private LLM in the EU.

Five checks separate a brochure from a specification:

Location. Does inference stay in a member state, in documented EU geography, or anywhere?
Operations. Who may enter the data centre and the support queue? EU residents, EU citizens, or a global roster?
Legal entity. Which law binds the operator? A German GmbH is not a US parent with EU Regions.
Keys. Who decrypts? Customer KMS, an external HSM, or the platform default?
Weights. Closed US weights behind an EU endpoint, or Apache 2.0 weights on your node?

Check	Often enough	Rarely enough
Location	Bedrock EU geo, Google `locations/eu`	Anthropic API, Foundry Claude
Operations	Assured Workloads Premium, ESC staff rules	Worldwide standard support
Legal entity	AWS European Sovereign Cloud GmbH, Azure Local	A commercial EU Region alone
Keys	CMEK, Cloud EKM, customer HSM	Cloud default keys
Weights	Mistral Large 3 on your node	Claude weights, which stay closed

A private LLM answers check 1 and often check 5. Sovereign AI Europe asks for the other three once procurement or a public contract writes the word. The AI Act does not change that. Regulation (EU) 2026/1744 of 8 July 2026 keeps the general application date of 2 August 2026 and moves high-risk duties for Annex III to 2 December 2027 and for Annex I to 2 August 2028. That is role law, not a sovereignty statute.

What do AWS, Google and Microsoft actually sell?

The three US clouds sell sovereignty as a product line. AWS splits commercial EU Regions from a separate partition in Brandenburg. Google sells Assured Workloads packages, Free and Premium. Microsoft splits Sovereign Public Cloud, Sovereign Private Cloud and National Partner Clouds. None of those lines turns Claude into a European model.

AWS documents eight European Regions: Ireland, Frankfurt, London, Paris, Stockholm, Milan, Zurich and Spain. Six sit in EU member states. London and Zurich do not. The European Sovereign Cloud is a separate partition, first Region Brandenburg, with its own billing, identity and accounts. Global AWS accounts do not open it. German-law entities operate it, including AWS European Sovereign Cloud GmbH. The advisory board has four members, all EU citizens and EU residents, one of them independent. Qualified staff sit in the EU. Nitro remains the technical bar against operator access to EC2 content.

Commercial Bedrock EU geo is not that partition. The Sonnet 5.5 card lists eu.anthropic.claude-sonnet-5-5 on the global AWS Cloud. From Frankfurt the profile routes to Frankfurt, Stockholm, Milan, Spain, Ireland and Paris. London is an extra source, not a destination from Frankfurt. The catalogue is in What is Amazon Bedrock.

Google splits residency from personnel. Assured Workloads lists EU Data Boundary as a Free package: EU-only regions. EU Data Boundary and Support and EU Data Boundary with Access Justifications are Premium. Premium support access is limited to personnel based in the EU, whether Google or a subprocessor answers. Access Justifications adds a ticket for each access. Switzerland has its own package. It is not inside the EU boundary.

Microsoft describes Sovereign Cloud as three models. Sovereign Public Cloud runs in Microsoft datacentres inside a geopolitical boundary, for example the EU Data Boundary: EU plus EFTA (Liechtenstein, Iceland, Norway, Switzerland). Sovereign Private Cloud runs on Azure Local, including Foundry Local. National Partner Clouds run with an approved domestic partner. The EU Data Boundary page was last updated on 26 February 2025. Foundry Local does not fix Claude: the Foundry Claude page lists Global Standard and Data Zone Standard (US).

We recommend the commercial EU Region as the default once check 1 wins the specification. The sovereign partition, Assured Workloads Premium or Azure Local come on top once checks 2 to 4 are written down.

Where can Claude stay in the EU?

Claude in the EU is an endpoint problem. The Anthropic API accepts only global and us for inference_geo. Workspace geo is us only. Bedrock pins through eu.anthropic.claude-sonnet-5-5. Google pins through aiplatform.eu.rep.googleapis.com and locations/eu. Foundry does not pin Claude to an EU zone.

The data residency page lists that under Current limitations. The parameter works on Claude 4.6 and later. Older models return 400. US inference is 1.1x on input, output, cache writes and cache reads. Global stays at list price. The same 1.1x applies to Foundry Data Zone Standard (US).

The Sonnet 5.5 card lists launch on 28 September 2026, EOL no sooner than 28 September 2027, 1 million tokens of context, 128,000 output, June 2026 cutoff. Google keeps the same generation in Europe multi-region at 1,250 QPM, 12,500,000 uncached input TPM and 1,250,000 output TPM. The global endpoint doubles that to 2,500 QPM. The EU endpoint excludes the United Kingdom and Switzerland.

import json
import boto3

client = boto3.client("bedrock-runtime", region_name="eu-central-1")
response = client.converse(
    modelId="eu.anthropic.claude-sonnet-5-5",
    messages=[{
        "role": "user",
        "content": [{"text": "Name the five sovereignty checks in one sentence."}],
    }],
)
print(json.dumps(response["output"]))

Deny global.anthropic.* in IAM. Point Google calls at host aiplatform.eu.rep.googleapis.com and location eu. Foundry stays out of a sovereign Claude default. The gaps are in Azure AI Foundry explained.

What does the sovereign path cost?

Sovereignty adds a premium, but not the same premium on every path. Claude on a regional or multi-region endpoint costs ten percent more than global from Sonnet 4.5. Gemma 4 in Frankfurt costs more than in Virginia. Custom Model Import in Frankfurt costs more per minute than in the US Regions. Assured Workloads Premium is its own package. The first-party API has no eu, only a dearer us.

The Anthropic pricing page lists Sonnet 5.5 at 2 / 10 USD per million tokens, Opus 5.5 at 4 / 20, Haiku 5.5 up to 100,000 tokens at 0.10 / 0.50. Sonnet 5.5 cache reads cost 0.10 USD. CCU is 0.01 USD, 100 CCU equals 1 USD. EU Sonnet on Bedrock or Google is therefore 2.20 / 11.

Bedrock pricing lists Gemma 4 31B in Frankfurt at 0.17 / 0.48 USD, in US East, Ohio and West at 0.14 / 0.40. Custom Model Import in Frankfurt is 0.07144 USD per Custom Model Unit per minute, storage 1.95 USD per unit per month. In US East and Oregon the minute rate is 0.05718 USD, storage the same. Llama 3.1 8B 128K needs 2 units, Llama 3.1 70B 128K needs 8. Billing uses 5-minute windows.

Path	List price	Sovereignty lever
Claude Sonnet 5.5 global	2 / 10 USD per 1M tokens	none
Claude Sonnet 5.5 EU geo (10 %)	2.20 / 11 USD	location in the card destinations
Claude API `inference_geo: us`	1.1x list	location in the US, not the EU
Gemma 4 31B Frankfurt	0.17 / 0.48 USD	one EU Region, open weights
Import Frankfurt, 2 units	0.14288 USD per active minute	`eu-central-1`, your weights
Import Frankfurt, 8 units	0.57152 USD per active minute	same, larger model
Mistral Large 3 self-hosted	GPU rent, not read here	weights and operations with you

Two units in Frankfurt cost 0.14288 USD per active minute. Eight units cost 0.57152 USD. Text weights must stay under 200 GB, multimodal under 100 GB, context under 128K. Mistral Large 3 at 675B total parameters sits outside a naive import. The card names vLLM from 1.12.0 on one 8xH200 node. We did not read GPU list prices on an allowed source in this run, so that cell stays empty.

The three-cloud API table is in Claude API pricing EU.

How do you pick the stack?

You pick sovereign AI in Europe in six steps, not in one RFP sentence. Write the five checks into the specification. Choose location first. Choose operations and legal entity only if a supervisor or a contract asks. Lock Claude or open weights. Block global endpoints. Record the AI Act role and the EOL date.

Specification. Location, operations, legal entity, keys, weights. If it is not written, do not buy it.
Pick location. Member state, EU geography, or global. Claude only through Bedrock EU geo or Google locations/eu.
Operations and entity. Commercial EU Region, Assured Workloads Premium, the AWS sovereign partition, or Azure Local. Do not mix them unless you need the extra.
Model. Claude Sonnet 5.5 for agents and a million tokens. Gemma 4 31B in Frankfurt when the dollar rate and in-region are enough. Mistral Large 3 on your node when the weights must sit in house.
Block. IAM against global.. Organisation policy against the Google global host. Foundry Claude out of the default.
Evidence. Profile ID, location, package name, licence, AI Act role, EOL date in the runbook.

We recommend Claude on Bedrock EU as the default for European teams that need agents and residency but not their own partition. Assured Workloads Premium or the sovereign partition come on top when personnel and legal entity are written down. Open weights come in addition, not instead, once check 5 wins. Roles are in EU AI Act for LLM deployers.

FAQ

What is sovereign AI in Europe in one sentence?

Sovereign AI in Europe is a control stack of location, operating staff, legal entity, key custody and weight licence. It is not a model name and not a cloud logo.

Is an EU Region enough for sovereign AI?

An EU Region meets the location check. It does not automatically meet operations, legal entity or keys. AWS splits the six commercial EU Regions from the sovereign partition in Brandenburg. Google splits Free EU Data Boundary from Premium support packages.

What does sovereign AI cost against global Claude list?

Regional and multi-region endpoints from Sonnet 4.5 add 10 percent, so EU Sonnet 5.5 is 2.20 / 11 USD per million tokens instead of 2 / 10. Gemma 4 31B in Frankfurt is 0.17 / 0.48 instead of 0.14 / 0.40. Import in Frankfurt is 0.07144 USD per unit per minute instead of 0.05718 in the US Regions.

Sovereign AI vs a private LLM: which one?

A private LLM answers hosting and often the weights. Sovereign AI also asks for personnel, legal entity and keys. Use the private-LLM tree when location is enough. Use this checklist when procurement writes sovereignty.

Does Microsoft Foundry pin Claude to the EU?

No. The Foundry Claude page lists Global Standard and Data Zone Standard (US). No EU data zone is documented there. Foundry Local on Azure Local covers other models, not this Claude default.

Does the AI Act replace a sovereignty review?

No. The AI Act applies generally from 2 August 2026 and governs roles, bans and high-risk duties. It does not require EU weights or an EU GmbH. Residency and sovereignty stay procurement choices beside the regulation.

Sources

Anthropic: Pricing (20 October 2026)
Anthropic: Data residency (20 October 2026)
AWS: Overview of the AWS European Sovereign Cloud (20 October 2026)
AWS: ESC design approach (20 October 2026)
AWS: Claude Sonnet 5.5 Model Card (20 October 2026)
AWS: Custom Model Import (20 October 2026)
Amazon Bedrock Pricing (20 October 2026)
Google Cloud: Assured Workloads control packages (20 October 2026)
Google Cloud: Data residency (20 October 2026)
Google Cloud: Claude Sonnet 5.5 (20 October 2026)
Google Cloud: Use partner models (20 October 2026)
Microsoft Learn: Microsoft Sovereign Cloud (20 October 2026)
Microsoft Learn: EU Data Boundary (20 October 2026)
Microsoft Learn: Claude models in Foundry (20 October 2026)
Hugging Face: Mistral-Large-3-675B-Instruct-2512 (20 October 2026)
EUR-Lex: Regulation (EU) 2026/1744 (20 October 2026)