Curated in-region model registry
Every endpoint we route to, with its legal address.
Policy packs never route to a provider in general. They route to a named regional deployment whose region id, facility, parent jurisdiction, retention terms and certifications have been checked and recorded.
Registry / endpoints by zone
- EU19
- UK4
- CH5
- GCC6
- APAC7
- US3
reviewed 2026-11-06
- 44
- in-region endpoints from 19 providers and self-hosted runtimes
- YTT Secunet endpoint registry, reviewed 2026-11-06
- 6
- legal zones with their own endpoint pools: EU, UK, Switzerland, GCC, APAC and US government regions
- YTT Secunet endpoint registry, reviewed 2026-11-06
- 8
- endpoints rated None for CLOUD Act exposure: no US operating group, or customer-operated
- YTT Secunet endpoint registry, reviewed 2026-11-06
- 15
- endpoints with zero data retention available without a separate approval
- YTT Secunet endpoint registry, reviewed 2026-11-06
- No US parent
- Indirect exposure
- Direct (US parent)
- Mixed at one site
- Self-hosted runtime
44 of 44 endpoints match
| Provider / service | Region id | Location | Zone | Parent HQ | CLOUD Act | ZDR | Certifications | Model families |
|---|---|---|---|---|---|---|---|---|
 Microsoft AzureAzure OpenAI Service | swedencentral | Gävle, Sweden | EU | United States | Direct | On request | ISO 27001, SOC 2 Type II | GPT-4o family, GPT-4.1 family, o-series reasoning |
| Microsoft AzureAzure OpenAI Service | francecentral | Paris, France | EU | United States | Direct | On request | ISO 27001, SOC 2 Type II, HDS | GPT-4o family |
| Microsoft AzureAzure OpenAI Service (Data Zone EU deployment) | germanywestcentral | Frankfurt am Main, Germany | EU | United States | Direct | On request | ISO 27001, SOC 2 Type II, BSI C5 | GPT-4o family, GPT-4.1 family |
 Amazon Web ServicesAmazon Bedrock | eu-central-1 | Frankfurt am Main, Germany | EU | United States | Direct | Available | ISO 27001, SOC 2 Type II, BSI C5 | Anthropic Claude, Amazon Nova, Meta Llama 3.x, Mistral |
| Amazon Web ServicesAmazon Bedrock | eu-west-1 | Dublin, Ireland | EU | United States | Direct | Available | ISO 27001, SOC 2 Type II | Anthropic Claude, Amazon Nova, Meta Llama 3.x, Mistral |
| Amazon Web ServicesAmazon Bedrock | eu-west-3 | Paris, France | EU | United States | Direct | Available | ISO 27001, SOC 2 Type II, HDS | Anthropic Claude, Amazon Titan Embeddings |
| AWS European Sovereign CloudAmazon Bedrock (AWS European Sovereign Cloud) | eusc-de-east-1 | Brandenburg, Germany | EU | United States (operated by German subsidiaries) | Indirect | Available | Region-specific Bedrock catalogue | |
 Google CloudVertex AI (Generative AI) | europe-west3 | Frankfurt am Main, Germany | EU | United States | Direct | On request | ISO 27001, SOC 2 Type II, BSI C5 | Gemini family, Gemini embeddings |
| Google CloudVertex AI (Generative AI) | europe-west4 | Eemshaven, Netherlands | EU | United States | Direct | On request | ISO 27001, SOC 2 Type II | Gemini family, Gemini embeddings |
 Mistral AILa Plateforme API (EU endpoint) | eu | EU data centres, European Union | EU | France | None | On request | ISO 27001, SOC 2 Type II | Mistral Large, Mistral Medium, Mistral Small, Codestral |
 ScalewayGenerative APIs | fr-par | Paris, France | EU | France (Iliad Group) | None | Available | ISO 27001, HDS | Llama 3.x, Mistral family, Qwen family |
 OVHcloudAI Endpoints | gra | Gravelines, France | EU | France | Indirect | On request | ISO 27001 | Llama 3.3 70B, Mistral Nemo, Mixtral 8x7B, Qwen 2.5 Coder |
 STACKITAI Model Serving | eu01 | Germany (eu01) | EU | Germany (Schwarz Group) | None | Available | ISO 27001, BSI C5 | Llama 3.3, Gemma 3, gpt-oss, Qwen3 |
 IONOSAI Model Hub | de-txl | Berlin, Germany | EU | Germany | Indirect | On request | ISO 27001 | Llama 3.3 70B, Mistral Small 24B, gpt-oss-120b |
 T-SystemsAI Foundation Services (LLM Serving, open-weight tier) | otc-eu-de | Germany | EU | Germany (Deutsche Telekom) | Indirect | On request | ISO 27001, BSI C5 | Llama 3.3 70B, gpt-oss-120b, Mistral Small, Qwen family |
 NebiusToken Factory (dedicated endpoint) | eu-north1 | Mäntsälä, Finland | EU | Netherlands | Indirect | Available | ISO 27001 | Llama 3.x, Qwen family, DeepSeek family |
 Oracle Cloud InfrastructureOCI Generative AI | eu-frankfurt-1 | Frankfurt am Main, Germany | EU | United States | Direct | On request | ISO 27001, SOC 2 Type II, BSI C5 | Cohere Command, Meta Llama 3.x |
| Oracle EU Sovereign CloudOCI Generative AI (EU Sovereign Central) | eu-frankfurt-2 | Frankfurt am Main, Germany | EU | United States (operated by EU subsidiaries) | Indirect | On request | Cohere Command, Meta Llama 3.x | |
 vLLM (self-hosted)Customer-operated vLLM runtime | customer-vpc-eu | Customer data centre (EU), European Union | EU | Customer entity | None | Self-managed | Customer controls | Llama 3.x, Mistral open-weight, Qwen family, gpt-oss |
| Microsoft AzureAzure OpenAI Service | uksouth | London, United Kingdom | UK | United States | Direct | On request | ISO 27001, SOC 2 Type II, Cyber Essentials Plus | GPT-4o family |
| Amazon Web ServicesAmazon Bedrock | eu-west-2 | London, United Kingdom | UK | United States | Direct | Available | ISO 27001, SOC 2 Type II | Anthropic Claude, Amazon Titan Embeddings |
| Google CloudVertex AI (Generative AI) | europe-west2 | London, United Kingdom | UK | United States | Direct | On request | ISO 27001, SOC 2 Type II | Gemini family |
| Oracle Cloud InfrastructureOCI Generative AI | uk-london-1 | London, United Kingdom | UK | United States | Direct | On request | ISO 27001, SOC 2 Type II | Cohere Command, Meta Llama 3.x |
| Amazon Web ServicesAmazon Bedrock | eu-central-2 | Zurich, Switzerland | CH | United States | Direct | Available | ISO 27001, SOC 2 Type II | Anthropic Claude Sonnet, Amazon Titan Embeddings V2 |
| Google CloudVertex AI (Generative AI) | europe-west6 | Zurich, Switzerland | CH | United States | Direct | On request | ISO 27001, SOC 2 Type II | Gemini family |
 SwisscomSwiss AI Platform (managed inference) | ch | Switzerland | CH | Switzerland | None | On request | ISO 27001 | Apertus, Open-weight LLMs |
 InfomaniakAI Tools LLM API | ch-gva | Geneva, Switzerland | CH | Switzerland | None | Available | ISO 27001, ISO 9001 | Llama 3.3, Mixtral, IBM Granite |
| vLLM (self-hosted)Customer-operated vLLM runtime | customer-onprem-ch | Customer data centre (CH), Switzerland | CH | Customer entity | None | Self-managed | Customer controls | Llama 3.x, Mistral open-weight, Apertus |
| Amazon Web ServicesAmazon Bedrock | me-central-1 | United Arab Emirates | GCC | United States | Direct | Available | ISO 27001, SOC 2 Type II | In-region Bedrock catalogue (model-dependent) |
| Google CloudVertex AI (Generative AI) | me-central2 | Dammam, Saudi Arabia | GCC | United States | Direct | On request | ISO 27001, SOC 2 Type II | Gemini family |
| Oracle Cloud InfrastructureOCI Generative AI | me-dubai-1 | Dubai, United Arab Emirates | GCC | United States | Direct | On request | ISO 27001, SOC 2 Type II | Cohere Command, Meta Llama 3.x |
| Oracle Cloud InfrastructureOCI Generative AI | me-riyadh-1 | Riyadh, Saudi Arabia | GCC | United States | Direct | On request | ISO 27001, SOC 2 Type II | Cohere Command, Meta Llama 3.x |
 Core42 (G42)Compass API | uae | Abu Dhabi, United Arab Emirates | GCC | United Arab Emirates | Indirect | On request | Jais, Llama 3, gpt-oss-120b, gpt-oss-20b | |
| vLLM (self-hosted)Customer-operated vLLM runtime | customer-onprem-sa | Customer data centre (KSA), Saudi Arabia | GCC | Customer entity | None | Self-managed | Customer controls | Llama 3.x, Jais, Qwen family |
| Microsoft AzureAzure OpenAI Service | japaneast | Tokyo, Japan | APAC | United States | Direct | On request | ISO 27001, SOC 2 Type II | GPT-4o family |
| Microsoft AzureAzure OpenAI Service | australiaeast | Sydney, Australia | APAC | United States | Direct | On request | ISO 27001, SOC 2 Type II, IRAP | GPT-4o family |
| Amazon Web ServicesAmazon Bedrock | ap-southeast-1 | Singapore | APAC | United States | Direct | Available | ISO 27001, SOC 2 Type II, MTCS Level 3 | Anthropic Claude, Amazon Titan Embeddings |
| Amazon Web ServicesAmazon Bedrock | ap-southeast-2 | Sydney, Australia | APAC | United States | Direct | Available | ISO 27001, SOC 2 Type II, IRAP | Anthropic Claude, Amazon Titan Embeddings |
| Amazon Web ServicesAmazon Bedrock | ap-northeast-1 | Tokyo, Japan | APAC | United States | Direct | Available | ISO 27001, SOC 2 Type II | Anthropic Claude, Amazon Nova, Amazon Titan Embeddings |
| Google CloudVertex AI (Generative AI) | asia-southeast1 | Singapore | APAC | United States | Direct | On request | ISO 27001, SOC 2 Type II, MTCS Level 3 | Gemini family |
| Google CloudVertex AI (Generative AI) | australia-southeast1 | Sydney, Australia | APAC | United States | Direct | On request | ISO 27001, SOC 2 Type II, IRAP | Gemini family |
| AWS GovCloud (US)Amazon Bedrock | us-gov-west-1 | US Northwest, United States | US | United States | Direct | Available | FedRAMP High, DoD IL4/IL5, ITAR | Claude 3.7 Sonnet, Claude 3.5 Sonnet, Claude 3 Haiku, Llama 3 8B / 70B |
| Azure GovernmentAzure OpenAI Service | usgovarizona | Arizona, United States | US | United States | Direct | On request | FedRAMP High, DoD IL2 | GPT-4o family |
| Azure GovernmentAzure OpenAI Service | usgovvirginia | Virginia, United States | US | United States | Direct | On request | FedRAMP High, DoD IL2 | GPT-4o family |
- 01
Inference, not just storage, in region
Provider documentation must state that inference for the service runs in the region. Storage-at-rest commitments alone do not qualify; those regions are listed separately and no pack treats them as in-region processing.
- 02
Retention terms on record
We record whether zero data retention is available by default, on request or self-managed. Packs that require ZDR only route to an endpoint once the tenant's retention agreement or approval reference is stored against it.
- 03
Parent and operator jurisdiction
The operating entity and its ultimate parent are recorded and rated None, Indirect or Direct for CLOUD Act exposure, using the method published with the Sovereign AI Index.
- 04
Certifications checked at the source
ISO 27001 certificates, SOC 2 reports, BSI C5 attestations and HDS certificates are checked against the issuer or the report itself, with scope and expiry dates, not taken from a marketing page.
- 05
Region id and facility verified
Network and TLS checks confirm the hostname serves from the claimed region before the endpoint goes live. The method is below.
- 06
Continuous re-verification
Probes run daily, documentation is re-reviewed quarterly, and a certificate or IP change outside the provider's published ranges opens a review. A demoted endpoint leaves every pool; routes fail closed rather than fall back.
Region id. Taken from the provider's own region list and the endpoint hostname, then checked against the IP ranges the provider publishes per region: AWS publishes region-tagged ranges, Azure publishes regional service tags and Google Cloud publishes ranges per region scope.
Physical bound. Light in fibre covers roughly 100 km per millisecond of round trip. Probes in several cities measure round-trip time to the endpoint, so a 1.4 ms answer from Frankfurt rules out a host in Virginia, whatever the DNS name says.
Facility code. Country, metro and site. Where a provider discloses only the metro, the code is metro-level and says so; where it discloses sites under NDA, or the endpoint is your own data centre, the code is site-level. The receipt carries this code and the TLS thumbprint for every request.
id: ep_azure_gwc
provider: Microsoft Azure
service: Azure OpenAI Service
region: germanywestcentral
facility: DE-FRA-1 # metro-level code
jurisdiction: EU
cloudActExposure: Direct
zdr: on_request
checks:
ipRanges:
source: provider service tags, region-scoped
result: pass
rtt:
probe-fra: 1.4ms # under 2 ms bounds the host
probe-ams: 7.9ms # to roughly 140 km of Frankfurt
probe-iad: 88.6ms
tls:
spkiSha256: 6d1f...c9a0
lastRotation: 2026-09-14
reviewedAt: 2026-11-06EU, Swiss or other non-US parent with no US operating group, or a runtime you operate yourself. No US entity in the chain that a US warrant could reach.
Non-US parent whose group runs material US cloud, telecom or data centre operations or holds a US listing, or a US-parented sovereign subsidiary operated under EU law.
The operating entity is a US company or a US company's branch or region. Data in an EU region is still held by a provider subject to US compelled disclosure.
The rating describes legal exposure of the operator, not the quality of its security. A Direct-rated EU region with zero data retention can be a reasonable choice under your transfer impact assessment; an Indirect or None rating does not make a deployment lawful on its own. YTT Secunet reduces what any provider can be compelled to disclose (no prompt retention, customer-held keys, in-VPC deployment) but does not make a US-parented provider immune from the CLOUD Act.
Packs use the rating directly. eu-gdpr-strict can be configured to allow only None and Indirect endpoints for a tenant, and the receipt names the endpoint, so the choice is visible per request.
Does YTT Secunet host any of these models?
No. Every row is a provider's regional deployment or a customer-operated runtime. YTT Secunet certifies the endpoint, routes to it and receipts each request; the provider or your own team runs the model.
Why are Azure, AWS and Google regions in Europe rated Direct?
Because the operating entity's ultimate parent is a US company, which can be compelled under the CLOUD Act regardless of where the data sits. That rating is about legal exposure, not about the quality of the provider's EU controls. Your transfer impact assessment decides whether contractual and technical measures, such as zero retention, are sufficient.
Can we add our own endpoint?
Yes. Self-hosted runtimes such as vLLM or Ollama in your VPC or data centre are registered as private endpoints on Enterprise Sovereign and Sovereign Dedicated. They go through the same region and certificate checks, and their facility code is your own site.
What happens when a provider changes a region's terms?
The quarterly review or a probe failure opens a re-verification. If the endpoint no longer meets a pack's requirements it is removed from that pack's pools, receipts start showing the new pool, and affected tenants are notified. Routing never silently falls back to an out-of-zone endpoint.
How does this registry relate to the public Sovereign AI Index?
They are the same dataset. The index publishes the rows, ratings and methodology for anyone to use; this registry is the operational view that policy packs route against, with per-tenant approvals and certificate pins added.
Sovereign route ready
Stop risking 4% global turnover GDPR fines on AI inference.
Deploy sovereign, cryptographically proven AI routing in 15 minutes.