Workspace data lives in the region you choose at creation, and processing happens there too — residency that only covers storage while inference happens somewhere else is not residency, it is marketing.
Available regions
- ap-south (Mumbai) — default for workspaces created from India.
- eu-central (Frankfurt) — recommended for GDPR-scoped teams.
- us-east (Virginia) — default for everyone else.
What stays in region
Run logs, traces, contexts, artifacts, and backups. Model inference runs on in-region capacity; when a routed model has no in-region deployment, the run log says so before execution and you can pin routing to in-region models only.
y0 workspace show --field residency
# region: eu-central
# inference: in-region only (strict)
# backups: eu-central, encryptedWhat does not
Billing records (processed by our payment provider) and the account email/name needed for global login. That is the complete list, and it is also in the DPA in less friendly language.
Changing region after creation requires an export-and-migrate; we do not move workspaces silently. Enterprise plans can request single-region contractual commitments.