# Data residency

Data residency pins an environment's personal data to one home region. It is included in Enterprise and is a +$99 a month add-on (excl. taxes) on Business; see [plans and limits](/get-started/plans-and-limits/#data-residency-add-on) for buying it and moving an existing environment.

| Region | Code | AWS region   |
| ------ | ---- | ------------ |
| EU     | `eu` | eu-central-1 |
| India  | `in` | ap-south-1   |
| US     | `us` | us-east-1    |

## How it works

- Choose the region when you create the environment (`residency_region`). Directories inherit their environment's region. `GET /v1/environment` reports it in `residency`.
- API requests are routed to the home region after authentication. SCIM requests go to the directory's home region.
- Sign-ins are redirected to the home region, never proxied. If the home region is down, the sign-in fails rather than being served elsewhere ([`home_region_unavailable`](/errors/home_region_unavailable/)).
- Moving an environment to another region is a staff-run, audited job that copies the data, checks the counts, switches the home region and deletes the old copy. Ask support.

## Availability

OhAuthCat runs in India (ap-south-1) today. The EU and US regions open as their infrastructure goes live; until then only `in` can be chosen. IdP-initiated SAML sign-ins and legacy SCIM paths are still served locally rather than routed by region.
