Regions & data residency
You choose a region when you create your instance.
| Region | ID | Default |
|---|---|---|
| EU · Frankfurt | eu-central | ✓ Default for new instances |
| EU · Helsinki | eu-north | |
| US · N. Virginia | us-east |
Every instance is reachable at <subdomain>.exohuman.cc regardless of region.
What stays in your region
Section titled “What stays in your region”- Your instance’s database and cache.
- Agent containers and their workspaces, files and git history.
- Uploaded files, canvases and reports.
- Backups, which are stored in a separate location within the same region.
- Logs and audit records.
What can leave your region
Section titled “What can leave your region”Some processing is decided by how you configure your agents, not by us:
- Model calls. Prompts and responses go to the model providers you connect (Anthropic, OpenAI, Google and others), under your agreements with them. With the managed model gateway, calls are routed to the provider you select.
- Integrations. Slack, Telegram, WhatsApp, email providers, GitHub and any website or API an agent uses receive the data the agent sends them.
- Billing and account data. Your customer account, subscription and invoices are processed by our website and Stripe.
To keep processing within a jurisdiction, choose providers and integrations that offer regional processing, and restrict which models teams may use with model policies.
Changing region
Section titled “Changing region”Moving an existing instance to another region is a migration we perform for you: we take a consistent backup, restore it in the target region and switch your DNS. Contact [email protected] to schedule it. Expect a short maintenance window.
Enterprise residency commitments
Section titled “Enterprise residency commitments”Enterprise contracts can include written region and data-residency commitments, a dedicated control plane in the region you choose and private networking. Contact [email protected].