Trust · Residency
Prompts, completions and logs — pinned to a region.
Choose from 12 regions. The router refuses to send eligible traffic outside the pinned set. Log stores are co-located in the same region.
MVP · join waitlist
| Region | Jurisdiction & law | Eligible providers | Log store | Status |
|---|---|---|---|---|
US · N. Virginia us-east-1 | US federal + state (CCPA/CPRA) | OpenAI, Anthropic, Google Vertex US, xAI, Groq, Fireworks, Together, Cerebras | us-east-1 | GA |
US · Oregon us-west-2 | US federal + state (CCPA/CPRA) | OpenAI, Anthropic, Google Vertex US, Fireworks, Together | us-west-2 | GA |
EU · Frankfurt eu-central-1 | GDPR, EU-US DPF, German BDSG | OpenAI EU, Anthropic EU, Google Vertex EU, Mistral, Azure OpenAI EU | eu-central-1 | GA |
EU · Ireland eu-west-1 | GDPR, EU-US DPF, Irish DPC | OpenAI EU, Anthropic EU, Google Vertex EU, Mistral | eu-west-1 | GA |
UK · London uk-south-1 | UK GDPR, DPA 2018, ICO | Azure OpenAI UK, Google Vertex UK, Anthropic EU (fallback) | uk-south-1 | MVP |
Canada · Montréal ca-central-1 | PIPEDA, Quebec Law 25 | Azure OpenAI Canada, Google Vertex Canada, Cohere Canada | ca-central-1 | MVP |
India · Mumbai ap-south-1 | DPDP Act 2023, MeitY | Azure OpenAI India, Sarvam, Krutrim, Google Vertex India | ap-south-1 | MVP |
Singapore ap-southeast-1 | PDPA, MAS TRM (finance) | Azure OpenAI SG, Google Vertex SG, AWS Bedrock SG | ap-southeast-1 | MVP |
Australia · Sydney ap-southeast-2 | Privacy Act 1988, IRAP | Azure OpenAI AU, Google Vertex AU, AWS Bedrock AU | ap-southeast-2 | Roadmap |
Japan · Tokyo ap-northeast-1 | APPI, PPC | Azure OpenAI Japan, Google Vertex Japan, AWS Bedrock Japan | ap-northeast-1 | Roadmap |
UAE · Dubai me-central-1 | UAE PDPL, DIFC DPL | Azure OpenAI UAE, G42/Falcon, AWS Bedrock ME | me-central-1 | Roadmap |
Brazil · São Paulo sa-east-1 | LGPD, ANPD | Azure OpenAI Brazil, Google Vertex Brazil, AWS Bedrock BR | sa-east-1 | Roadmap |
What happens if no eligible provider is available in a region?+
The request hard-fails with a typed 503 error and a policy_violation code. We never silently degrade to an ineligible region — that would defeat the purpose of pinning residency.
Are prompts and completions ever stored outside the pinned region?+
No. Under a pinned policy, request bodies, completions and derived embeddings stay in the region's log store for the configured retention window.
Can I pin routing to a region without pinning the log store?+
Yes — the two are independent. Common pattern: EU-only routing with a US log store for teams already running observability there, provided your DPA permits it.