# Regions

> Where your machines, databases and files run. One EU region at launch; a machine never leaves the region it was created in.

A region is the unit everything runs in: its own hosts, its own API, its own address space. Your workloads and data stay in the region of your workspace. Account and billing data stay in the EU whatever the region.

## At launch: EU

Rytiv launches with one region in the EU. Every app, computer, sandbox, database and bucket of a workspace runs there, under `https://<app>.rytiv.app`, and the API is `https://api.rytiv.app`. The region's code in the API is `ams`; the API field `region` on a machine carries it.

A US region follows. When it is offered, a workspace is created in one region and stays there; one login reaches every workspace, and each region has its own API address.

## A machine never moves between regions

A machine is placed in its region when it is created and stays there for its lifetime: a move to another host (`POST /v1/machines/:id/migrate`), a host failure, a deploy that replaces machines, all of it stays inside the region. Capacity is found in the region or not at all (`503` with `no-capacity`), never somewhere else. That is what makes the residency promise a property of the platform rather than a setting.

## What this means for you

- Choose the region with the workspace; nothing after that asks again.
- Internal addresses (`<database>.internal`, app links) resolve inside the region only.
- Static sites are served from the region's edge. It is one region, not a content delivery network.
- Mail is sent from the region's own delivery hosts; the sending domain is yours.

See [Security and data](https://docs.rytiv.com/concepts/security.md) for what stays encrypted and who can read what.