Regions + data residency
Wholisphere runs region-scoped deployments so customers with data-residency requirements (EU GDPR, APAC localization, US-only contracts) keep their captures, audit events, and embeddings inside the right border.
Hosts
| Region | Host |
|---|---|
| US (default) | api.wholisphere.ai |
| EU | eu.api.wholisphere.ai |
| APAC | apac.api.wholisphere.ai |
The dashboard hosts mirror the same prefixes (e.g. eu.app.wholisphere.ai).
Pinning an org
Org owners can change region in Settings → Organization → Region. The
default is us. Once changed, all of the org’s data lives in that region.
Migration between regions is a support-assisted operation today.
Misdirected requests
If a request authenticated as an org pinned to region X reaches a deployment in region Y, the API returns HTTP 421 Misdirected Request with two extra headers:
x-wholisphere-correct-region: eux-wholisphere-correct-host: eu.api.wholisphere.aiThe official SDK + dashboard auto-retry against the correct host when they see a 421 from us. Custom integrations should do the same: pin your base URL to the host that matches your org’s region.
What stays vs what moves
- Stays in-region: D1 (org metadata, audit), KV (cache, secrets, sessions), R2 (captures, exports), Durable Objects (rate-limit counters), webhook outbox + delivery attempts.
- Calls out-of-region: third-party LLM endpoints (Gemini, Claude) hit the providers’ regional endpoints when available. Stripe + Resend are global; we send only billing identifiers + email metadata.