---
title: "Choosing a data region"
description: "See where each store keeps a team's data, indexes, logs and backups. The global placement is the one offered; asking for the European Union or the United States is refused with the list of supported regions."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.overlane.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Choosing a data region

Overlane offers the `global` placement. `eu` and `us` are refused, with the list of supported regions, because not every store can hold a team's data in them. A team that has a pinned region keeps its data, indexes, logs and backups there, and moving to another region is an explicit, audited migration.

## Regions

| Region | What it means |
| --- | --- |
| `global` | No pin. The platform places data where it runs best. |
| `eu` | Stored and processed in the European Union. Refused: not every store can hold data there. |
| `us` | Stored and processed in the United States. Refused: not every store can hold data there. |

A region is offered only when every store the team uses can hold data in it. `fedramp` is a Cloudflare jurisdiction too, but it needs an account that is FedRAMP-capable, so it is not offered. Asking for a region that is not supported is refused with the list of supported ones, and nothing is created.

The regions rest on Cloudflare jurisdictions, checked on 2026-10-10: D1, R2, KV and Durable Objects all support `eu`, `us` and `fedramp` jurisdictions. Vectorize and the platform's own logs have no jurisdiction, so a pinned team keeps its vectors in jurisdiction Durable Object storage and its tenant logs in the jurisdiction R2 bucket; platform logs carry identifiers only.

## Pin a region

```sh
overlane enterprise region set --region eu
overlane enterprise region show
```

`region show` prints the pinned region and the store-location check: D1, R2, KV, Durable Objects, vectors, logs and backups, each with the region it holds. The check fails, and says which store, if any of them holds the team's data anywhere else or has no recorded placement.

## Move regions

```sh
overlane enterprise region set --region us --reason "customer request"
```

Once a team is pinned, a change needs a reason and is recorded in the [audit log](/enterprise/audit-and-siem/) as a migration request, with who asked. If the stores cannot all move, the old placement stays and the migration is marked failed.

## Backups

The database's own point-in-time recovery (D1 Time Travel) is the first backup. R2 has no object versioning, so Overlane writes dated, write-once snapshots to the jurisdiction bucket as well; they expire after 30 days. A restore drill ([retention, export and deletion](/enterprise/retention-and-deletion/)) proves the snapshots restore.

## Plans

Data residency is included from the Business plan up.

Source: https://docs.overlane.app/enterprise/data-region/index.mdx