Data residency is one of those topics that doesn't matter until it matters very badly. Compliance teams, public-sector customers, and regulated industries — fintech, healthcare, gov — increasingly require that customer data never leaves a specific jurisdiction. We're announcing residency options for two of the regions where this comes up most for our customers.
What's changed
Business and Enterprise plans can now choose one of:
- EU residency — all conversation data, customer records, and AI processing stays within Frankfurt, Germany. Aligned with GDPR's data-residency expectations for member-state regulated industries.
- GCC residency — same, hosted in Bahrain (our home region). Aligned with the data-protection laws in Bahrain, Saudi Arabia, UAE, Qatar, Oman, and Kuwait, including PDPL requirements.
Same product, same APIs, same Studio interface. The only difference is which region your data physically lives in.
What about the AI?
Captain AI's inference runs in the same region as your data. We use frontier-model providers who offer regional endpoints — your conversations don't leave your chosen region for the AI step either.
What's not changed
- Pricing: Data residency is included in Business and Enterprise plans at no additional cost
- Performance: Both regions are colocated with major peering exchanges; latency is competitive with our default hosting
- Migration: Existing customers can request a residency change — we migrate your workspace within a maintenance window we schedule with you
Requesting a residency setup
If you need EU or GCC residency, contact your account manager or [email protected]. We confirm the move within a business day and schedule the migration with you.