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

# Multi-Region Deployment

> Deploy your apps globally across multiple regions for improved latency and data residency compliance

Deploy apps globally across multiple continents to reduce latency through co-location and meet data residency requirements.

<Warning>
  Multi-region deployment is currently in **beta**. Rapid updates and
  improvements will be made over the next few months to bring full functionality
  to life. Please reach out on our [Discord](https://discord.gg/ATj6USmeE2)
  about features/functionality you would like to see
</Warning>

## Why Use Multi-Region Deployment

* **Reduced Latency**: Deploy closer to users for faster response times and better experience with real-time applications like voice agents and LLMs
* **Data Residency**: Meet data protection requirements by keeping sensitive data within specific geographic regions to comply with regulations like GDPR and CCPA
* **High Availability**: Ensure fault tolerance and continuous service through geographic redundancy, disaster recovery, and load balancing across multiple regions

## Available Regions

Cerebrium supports deployment across three major continents with the following regions:

### United States

* **us-east-1** (N. Virginia) - Default region

### Europe

* **eu-west-2** (United Kingdom)
* **eu-north-1** (Stockholm)

### Asia Pacific

* **ap-south-1** (Mumbai)

<Info>
  Additional regions are being evaluated and will be added based on user demand
  and infrastructure availability. Contact
  [support](mailto:support@cerebrium.ai) if you need deployment in a specific
  region not currently listed.
</Info>

## CLI Configuration

Configure the CLI to work with different regions in two ways:

Set a default region for all CLI commands:

```bash theme={null}
cerebrium region set us-east-1
```

This sets the default region for commands like listing storage volumes, running applications, and other operations.

Alternatively, specify the region for individual commands using `--region` (or its short form `-r`). This works for all file commands — `cp`, `ls`, `rm`, and `download`:

```bash theme={null}
cerebrium ls --region eu-north-1
cerebrium cp model.bin -r eu-north-1
cerebrium rm old_file.txt --region eu-north-1
cerebrium download results.json -r eu-north-1
```

<Info>
  `--region` applies only to the command it's attached to. The default set by
  `cerebrium region set` is not modified.
</Info>

## App Deployment

Set the deployment region using the `region` parameter in the `[cerebrium.hardware]` section of `cerebrium.toml`:

```toml theme={null}
[cerebrium.hardware]
region = "us-east-1"
provider = "aws"
compute = "AMPERE_A10"
cpu = 2
memory = 8.0
```

## Pricing

Pricing varies by region based on local infrastructure costs and availability:

## GPU Availability by Region

GPU availability and pricing vary across regions due to infrastructure constraints and local demand:

| GPU Model          | US East | US Central | EU West | EU North | AP South |
| ------------------ | ------- | ---------- | ------- | -------- | -------- |
| BLACKWELL\_B300    | ✅       | ❌          | ❌       | ❌        | ❌        |
| BLACKWELL\_B200    | ✅       | ✅          | ❌       | ❌        | ❌        |
| HOPPER\_H200       | ✅       | ✅          | ✅       | ✅        | ✅        |
| HOPPER\_H100       | ✅       | ❌          | ✅       | ✅        | ✅        |
| BLACKWELL\_RTX6000 | ❌       | ✅          | ❌       | ❌        | ❌        |
| AMPERE\_A100\_80GB | ✅       | ❌          | ✅       | ✅        | ✅        |
| AMPERE\_A100\_40GB | ✅       | ❌          | ✅       | ✅        | ✅        |
| ADA\_L40S          | ✅       | ❌          | ❌       | ✅        | ❌        |
| ADA\_L4            | ✅       | ❌          | ✅       | ✅        | ✅        |
| AMPERE\_A10        | ✅       | ❌          | ✅       | ✅        | ✅        |
| TURING\_T4         | ✅       | ❌          | ✅       | ✅        | ✅        |

### Limitations

* Each region requires a separate deployment. Apps deployed in one region do not automatically replicate to other regions.
* Each region has its own isolated persistent storage volume. Data stored in `/persistent-storage` in one region is not accessible
  from other regions.