# Regions (/docs/regions)
Every Daytona sandbox runs in a **region**: a geographic or logical grouping of compute infrastructure. When creating a sandbox, you can target a specific region, and Daytona schedules the workload on available capacity within that region. A create request that names no region uses the project's default region, then the organization's, then Earth.
Regions form one flat list, and each region names the broader regions it is inside, from Earth down to its direct parent. Earth covers every other region and means anywhere: a sandbox created in Earth can land in any geography.
A broader region lets Daytona place the sandbox anywhere inside it; a narrower region keeps the sandbox closer to you. Each region has its own price multiplier, applied to the base price of the sandbox's resources, and a region without one is billed at Earth's. The hierarchy does not set the price: a narrower region can cost less than its parent, so check the multiplier of the region you name. A listed region describes topology, not capacity: a create request can still fail for lack of capacity or matching hardware.
## Shared regions [#shared-regions]
Regions managed by Daytona and available to all organizations:
```python
from daytona import Daytona
daytona = Daytona()
# Create a sandbox anywhere in Earth
sandbox = daytona.v2.create(region="earth")
```
```typescript
import { Daytona } from '@daytona/sdk'
const daytona = new Daytona()
// Create a sandbox anywhere in Earth
const sandbox = await daytona.v2.create({ region: 'earth' })
```
```bash
# Create a sandbox anywhere in Earth
daytona sandbox create --region earth
```
```bash
# Create a sandbox anywhere in Earth
curl 'https://api.daytona.com/sandboxes' \
--request POST \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
"region_id": "earth"
}'
```
## Operations [#operations]
### List regions [#list-regions]
List regions. The list contains every region you can name in a create request, as one flat list in tree order: Earth first, then each region followed by the regions inside it. Each region names its parent regions, so a client can rebuild the hierarchy from the list. Regions that cannot be used are left out. A region that covers others stays listed when none of them accepts automatic placement, marked as unavailable, and cannot be named in a create request.
```bash
# Regions available to the current project, as NAME, ID, PRICE MULTIPLIER, and AVAILABLE columns
daytona region list
# Include parent regions
daytona region list --output json
```
```bash
# Regions available to the current project
curl 'https://api.daytona.com/regions' \
--header 'Authorization: Bearer YOUR_API_KEY'
```
The response contains one entry per region and the ID of your default region, with the following fields:
| **Field** | **Description** |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id` | Region ID, the value a create request names in `region_id`. |
| `name` | Display name. |
| `parent_region_ids` | IDs of the broader regions this region is inside, outermost first, so the last one is its direct parent. Empty for `earth`. Every ID is listed in the same response. |
| `available` | Whether a create request can name this region. For a region that covers others, whether at least one of them accepts automatic placement. Not a health or capacity signal. |
| `api_base_url` | The API base URL of the region, when it publishes its own. |
| `default_region_id` | ID of your default region: the project's default region, else the organization's, else the platform's. `null` when that region is not listed. |
### List region price multipliers [#list-region-price-multipliers]
List region price multipliers. The list contains the price multiplier of every region a create request can name, Earth first, then every other region ordered by ID. A sandbox's CPU, memory, GPU, and storage are billed at the base price times the multiplier of the region its create request named. A create request that names no region is billed at its default region's multiplier, or at Earth's when no default is set. For the other pricing dimensions, see [billing](/docs/billing#pricing-dimensions).
```bash
# The PRICE MULTIPLIER column of the region list
daytona region list
```
```bash
curl 'https://api.daytona.com/orgs/ORGANIZATION_ID/billing/region-multipliers' \
--header 'Authorization: Bearer YOUR_OIDC_TOKEN'
```
The response contains one entry per region, Earth first and the rest ordered by ID, with the following fields:
| **Field** | **Description** |
| ------------ | --------------------------------------------------------------------- |
| `region_id` | The region ID accepted by create requests. |
| `multiplier` | The multiplier applied to base CPU, memory, GPU, and storage prices. |