Inference that stays in the country
Where a jurisdiction demands local control, we run the models ourselves rather than routing to someone else's cloud. Each region names its operator-of-record, its residency guarantees and its status.
European Union — Frankfurt
Live- Inference, cache and logs never leave EU soil
- EU-resident staff only for production access
- No US parent access path for customer content
United States — Ashburn & Hillsboro
Live- Dual-region active/active with US-only failover
- BAA available on hosted endpoints
- Zero prompt retention by default
United Kingdom — London
Coming soon- UK-only residency
- UK IDTA in place of SCCs
India — Mumbai
Coming soon- In-country storage and inference
- Local grievance officer
United Arab Emirates — Abu Dhabi
Coming soon- In-country residency
- Arabic-first model line-up
Japan — Tokyo
Coming soon- Domestic residency
- JP-language support tier
US Public Sector — GovCloud
Coming soon- US persons only
- Isolated control plane
- Air-gap option
What does sovereign mean here?+
Inference, cache and logs are processed and stored inside the jurisdiction, by an entity subject to that jurisdiction, with staff access limited to residents of it. Anything short of that we label as residency, not sovereignty.
Can I pin routing to one region?+
Yes. Set provider.region on the request, or lock it at the API-key level. Requests that cannot be served in-region fail rather than silently leaving it.
Do coming-soon regions have dates?+
We publish a region only once the operator entity and the hardware are contracted. Waitlist members get the target date and early access before general availability.
Does this replace the trust pages?+
No — the trust section still covers frameworks, subprocessors and agreements for the whole platform. This page is only about where our own hardware runs.