Cloud regions
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();.
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.
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.5.
| Tier | AWS Region | Minimum client version | Maximum client version |
|---|---|---|---|
| Tier 1 | US East (N. Virginia) us-east-1 | 1.4.0 | 1.5.5 |
| Tier 1 | US West (Oregon) us-west-2 | 1.4.1 | 1.5.5 |
| Tier 2 | Europe (Frankfurt) eu-central-1 | 1.4.1 | 1.5.5 |
| Tier 2 | Europe (Dublin) eu-west-1 | 1.4.1 | 1.5.5 |
| Tier 3 | Asia Pacific (Tokyo) ap-northeast-1 | 1.4.1 | 1.5.5 |
| Tier 3 | Asia Pacific (Sydney) ap-southeast-2 | 1.4.1 | 1.5.5 |
For the full lifecycle and end-of-life policy, see MotherDuck version lifecycle schedules.
AI functions
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 for data residency 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.
- Data locality. For the best performance, keep source data (for example, in Amazon S3) in the same region as your Organization.
- Postgres endpoint. The Postgres endpoint hostname is regional, in the form
pg.<region>-aws.motherduck.com.