For enterprise tenants - especially those in regulated industries or with GDPR / data-residency obligations - knowing exactly where your data lives is the first compliance question. This guide covers what's available today and what's on the multi-region roadmap.
Regions available
- Asia-Pacific (Chennai, India) - the platform's home region; default for tenants based in APAC
- Europe (Frankfurt, Germany) - GDPR-resident; default for tenants based in EU
- North America (Virginia, US) - in beta; default for tenants based in NAM
- GCC (Dubai, UAE) - planned for Q4 2026; current GCC-region tenants pin to APAC with explicit data-handling acknowledgement
Region pinning at tenant creation
Region is set once at tenant creation and cannot be changed without a full data migration. Pick the right region upfront. Org Admins choose during the post-signup setup; default suggestion is based on the SaaS Admin's signup IP, but you can override.
What lives in your tenant's region
- Primary database (Postgres) - your tenant's records, configuration, RBAC, audit logs
- Object storage (files, attachments, generated documents) - same region
- Backups - replicated to a paired region in the same compliance zone (APAC pairs to APAC-2; EU pairs to EU-2; never crosses compliance boundaries)
- Vector store (RAG embeddings) - same region as primary
What may cross regions
- LLM inference - by default routes to the closest API endpoint of the model provider. Anthropic Claude is served from US-East; OpenAI GPT-4 likewise. For inference-residency-sensitive tenants, the platform supports a configurable LLM_REGION env that pins inference to a specific provider region
- Email delivery (via the SMTP layer) - sent through SendGrid US-East regardless of tenant region
- Telemetry (anonymous platform metrics, not customer data) - aggregated to the platform's home region
Multi-region deployment (Q4 2026)
On the Q4 2026 roadmap: a single tenant can have data pinned across multiple regions with the platform routing queries to the right region transparently. Useful for global enterprises with country-level residency rules (e.g., Germany data stays in Frankfurt; India data stays in Chennai). Until then, tenants serve one primary region with backup pairing.