Inference that stays in the country
Our roadmap for region-locked deployments. Each jurisdiction lists the intended operator model and controls, but no sovereign guarantee is generally available today.
European Union — Frankfurt
Coming soon- 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
Coming soon- Dual-region active/active with US-only failover
- Planned contractual data-handling controls
- Planned retention configuration
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 dedicated inference to one region today?+
Regional and sovereign guarantees remain on the roadmap. We confirm the available deployment boundary during enterprise scoping and do not imply a jurisdictional guarantee before it is contracted.
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 security page?+
No. The security page is the current source for what is available, contract-specific, or still on the roadmap.