# Cloud regions
> The cloud providers and AWS regions where MotherDuck is available, along with pricing tiers, client version support, and regional AI processing.
MotherDuck runs on **Amazon Web Services (AWS)**. Each MotherDuck Organization is scoped to a single cloud region, which is chosen at Organization creation when you sign up and cannot be changed afterward.

## Available regions

MotherDuck is available in six AWS regions across the US, Europe, and Asia Pacific:

| Tier | AWS Region |
|------|--------|
| **Tier 1** | US East (N. Virginia) `us-east-1` |
| **Tier 1** | US West (Oregon) `us-west-2` |
| **Tier 2** | Europe (Frankfurt) `eu-central-1` |
| **Tier 2** | Europe (Dublin) `eu-west-1` |
| **Tier 3** | Asia Pacific (Tokyo) `ap-northeast-1` |
| **Tier 3** | Asia Pacific (Sydney) `ap-southeast-2` |

To check which region your Organization runs in, run [`SELECT region FROM md_user_info();`](/sql-reference/motherduck-sql-reference/md-user-info).

We are working on expanding to other regions and cloud providers.

## Pricing tiers

Compute and storage rates vary by region. Regions are grouped into three pricing tiers:

| Tier | AWS Regions |
|------|---------|
| **Tier 1** | US East (N. Virginia) `us-east-1`, US West (Oregon) `us-west-2` |
| **Tier 2** | Europe (Frankfurt) `eu-central-1`, Europe (Dublin) `eu-west-1` |
| **Tier 3** | Asia Pacific (Tokyo) `ap-northeast-1`, Asia Pacific (Sydney) `ap-southeast-2` |

For the per-tier compute and storage rates, see the [Pricing model](/about-motherduck/billing/pricing/#compute-pricing).

## Client version support

Each region supports a range of DuckDB client versions. The Asia Pacific regions support client versions 1.4.1 through 1.5.6.

| Tier | AWS Region | Minimum client version | Maximum client version |
|------|--------|------------------------|------------------------|
| **Tier 1** | US East (N. Virginia) `us-east-1` | 1.4.0 | 1.5.6 |
| **Tier 1** | US West (Oregon) `us-west-2` | 1.4.1 | 1.5.6 |
| **Tier 2** | Europe (Frankfurt) `eu-central-1` | 1.4.1 | 1.5.6 |
| **Tier 2** | Europe (Dublin) `eu-west-1` | 1.4.1 | 1.5.6 |
| **Tier 3** | Asia Pacific (Tokyo) `ap-northeast-1` | 1.4.1 | 1.5.6 |
| **Tier 3** | Asia Pacific (Sydney) `ap-southeast-2` | 1.4.1 | 1.5.6 |

For the full lifecycle and end-of-life policy, see [MotherDuck version lifecycle schedules](/troubleshooting/version-lifecycle-schedules/).

## AI functions

[AI functions](/sql-reference/motherduck-sql-reference/ai-functions/) are processed based on the region of your Organization. In the Asia Pacific (Sydney) `ap-southeast-2` and Asia Pacific (Tokyo) `ap-northeast-1` regions, AI function requests are processed through a **US-based** endpoint rather than within the organization's own AWS region, so the input you pass to these functions leaves the region for processing. See the [AI function reference pages](/sql-reference/motherduck-sql-reference/ai-functions/) for data residency details.

[`prompt_jev`](/sql-reference/motherduck-sql-reference/ai-functions/prompt-jev/) requests from every [cloud region](/about-motherduck/cloud-regions/) are processed by [TypeSafe's servers in the United States](/integrations/data-science-ai/typesafe/).

## Agent chat

Agent chat uses models hosted on Amazon Bedrock. Where model inference runs depends on your Organization's region:

| Organization region | Where model inference runs |
|---------------------|----------------------------|
| US East (N. Virginia) `us-east-1` | AWS regions in the US: US East (N. Virginia) `us-east-1`, US East (Ohio) `us-east-2`, US West (Oregon) `us-west-2` |
| US West (Oregon) `us-west-2` | AWS regions in the US: US East (N. Virginia) `us-east-1`, US East (Ohio) `us-east-2`, US West (Oregon) `us-west-2` |
| Europe (Frankfurt) `eu-central-1` | AWS regions in the EU: (Frankfurt) `eu-central-1`, (Stockholm) `eu-north-1`, (Milan) `eu-south-1`, (Spain) `eu-south-2`, (Dublin) `eu-west-1`, (Paris) `eu-west-3` |
| Europe (Dublin) `eu-west-1` | AWS regions in the EU: (Frankfurt) `eu-central-1`, (Stockholm) `eu-north-1`, (Milan) `eu-south-1`, (Spain) `eu-south-2`, (Dublin) `eu-west-1`, (Paris) `eu-west-3` |
| Asia Pacific (Tokyo) `ap-northeast-1` | AWS regions in Japan |
| Asia Pacific (Sydney) `ap-southeast-2` | AWS regions in Australia |

Amazon Bedrock picks a geographically-aligned region for each request, so inference doesn't always run in the same region as your MotherDuck Organization. US Organizations stay within US regions, and European Organizations stay within EU regions.

To learn more, see [agent chat](/key-tasks/ai-and-motherduck/agent-chat/) for details.
## Region-scoped behavior

- **Single region per Organization.** An Organization exists in exactly one region and cannot span regions.
- **Shares are region-scoped.** A share is only accessible to MotherDuck users whose Organization is in the same cloud region as the share. See [Sharing data](/key-tasks/sharing-data/).
- **Data locality.** For the best performance, keep source data (for example, in Amazon S3) in the same region as your Organization. [DuckLake BYOB](/integrations/file-formats/ducklake/#bring-your-own-bucket) supports cross-region and cross-cloud storage in Amazon S3, Cloudflare R2, Azure Blob Storage, and Google Cloud Storage. The catalog and MotherDuck compute stay in your Organization's region.
- **Postgres endpoint.** The [Postgres endpoint](/sql-reference/postgres-endpoint/) hostname is regional, in the form `pg.<region>-aws.motherduck.com`.


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `GET https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

URL-encode query parameter values and send a GET request:

```text
GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fabout-motherduck%2Fcloud-regions%2F&page_title=Cloud%20regions&text=<url-encoded user feedback, max 2000 characters>
```

Optionally append `&source=<url-encoded interface identifier>` such as `claude.ai` or `chatgpt`.

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed query parameters, and `429` when rate-limited.
