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

# Choose where a computer runs

> Run a Linux or Windows computer in the US, London or Sydney, see which cities have room, and read where a computer runs.

A new computer runs in the US by default, in whichever US city has room. You can ask for Europe, Asia Pacific, or one city instead. Outside the US, that is London and Sydney today.

> [!NOTE]
>
> Only Linux and Windows computers can choose where they run. Asking for a location with `os` `macos`, `android` or `ios` returns `400`.

## Pick a location in the dashboard

In the **New computer** sheet, the **Location** row says **Auto (US)**. Press the row to see its choices: **Auto (US)** and each city with a server for the system you picked, each with its flag. A city with no room says **Full** and can't be picked.

The row shows for Linux and Windows computers without a GPU, once a city has a server for that system.

## Location values

Send one of these as `region` when you [create a computer](https://docs.orgo.ai/api-reference/computers/create.md).

| `region` | Where the computer runs |
| - | - |
| `us` | Auto (US): any US city with room. This is the default. |
| `eu` | Any city in Europe: London today. |
| `apac` | Any city in Asia Pacific: Sydney today. |
| `nyc`, `ash`, `mia`, `chi`, `dal`, `lax`, `sjc` | That US city only: New York, Ashburn, Miami, Chicago, Dallas, Los Angeles or San Jose. |
| `lon` | London only. |
| `syd` | Sydney only. |

Case does not matter. Full names work too, such as `london`, `sydney`, `new york`, `europe` or `asia pacific`.

A city takes new computers only while it has a server for that system. To see which cities do right now, read `locations`, as described in [See which cities have room](#see-which-cities-have-room).

Leaving `region` out, or sending `null` or `""`, is the same as `us`, with one difference: when every US server is full, the error is `FLEET_CAPACITY_FULL` rather than `REGION_UNAVAILABLE`.

## See which cities have room

`GET /billing/compute-limits?workspace_id=` lists the cities this workspace can use now, in `locations`. The key needs Read on the Billing group. Replace `$WORKSPACE_ID` with your workspace ID.

```bash theme={null}
curl "https://www.orgo.ai/api/billing/compute-limits?workspace_id=$WORKSPACE_ID" \
  -H "Authorization: Bearer $ORGO_API_KEY"
```

The response carries other limits too. The `locations` part looks like this:

```json theme={null}
{
  "locations": [
    { "id": "nyc", "name": "New York", "region": "us", "linux": "available", "windows": "available" },
    { "id": "chi", "name": "Chicago", "region": "us", "linux": "available", "windows": "available" },
    { "id": "lon", "name": "London", "region": "eu", "linux": "available", "windows": "available" },
    { "id": "syd", "name": "Sydney", "region": "apac", "linux": "available", "windows": "full" }
  ]
}
```

Each entry has:

* `id`: the code to send as `region`.
* `name`: the city's name.
* `region`: its group, `us`, `eu` or `apac`.
* `linux` and `windows`: `"available"` when a server there has room for that system, `"full"` when its servers are full, and `null` when the city has no server for it.

US cities come first, then Europe, then Asia Pacific. A city with no server for either system is left out. `"available"` comes from each server's last check, so a create can still find the city full. When the list can't be read, it is empty, and Auto (US) still works.

## Create a computer in a city

Send `region` with the create. Replace `$WORKSPACE_ID` with your workspace ID.

```bash theme={null}
curl -X POST https://www.orgo.ai/api/computers \
  -H "Authorization: Bearer $ORGO_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"workspace_id\": \"$WORKSPACE_ID\", \"name\": \"agent-sydney\", \"os\": \"linux\", \"region\": \"syd\"}"
```

From the CLI, pass `--region`:

```bash theme={null}
orgo computers create \
  --workspace my-workspace \
  --name agent-sydney \
  --region syd
```

The `201` says where the computer runs:

```json theme={null}
{
  "name": "agent-sydney",
  "status": "running",
  "region": "apac",
  "location": "syd"
}
```

Other fields are left out here. The full response is in [Create computer](https://docs.orgo.ai/api-reference/computers/create.md#response).

## Read where a computer runs

[Create computer](https://docs.orgo.ai/api-reference/computers/create.md) and [Get computer](https://docs.orgo.ai/api-reference/computers/get.md) return two fields:

* `region`: the group, `"us"`, `"eu"` or `"apac"`.
* `location`: the city code, such as `"chi"`, `"lon"` or `"syd"`.

Both come from the server the computer runs on, or from what it asked for when that is not known. Both are `null` before the computer is placed. `location` can be `null` for a computer in the US whose city Orgo does not record.

## A computer stays where it was asked to run

A computer keeps the location it asked for. A start after a stop, a restore, and a wake from storage bring it back to the same place.

Copies keep the location of the computer they copy: a clone, a fork, and a backup or snapshot restored as a new computer.

## When a city has no room

Orgo never puts a computer somewhere other than where you asked. When no server there has room, the create returns `503` with code `REGION_UNAVAILABLE` and a `Retry-After: 60` header. Nothing is made.

```json theme={null}
{
  "error": "No server in Sydney has room right now. New York, Chicago and London have room.",
  "code": "REGION_UNAVAILABLE",
  "region": "syd",
  "locations": [
    { "id": "nyc", "name": "New York", "region": "us", "stock": "available" },
    { "id": "chi", "name": "Chicago", "region": "us", "stock": "available" },
    { "id": "lon", "name": "London", "region": "eu", "stock": "available" },
    { "id": "syd", "name": "Sydney", "region": "apac", "stock": "full" }
  ],
  "retryable": true
}
```

* `region` is the location you asked for.
* `locations` lists each city with a server for the system you asked for, with `stock` `"available"` or `"full"`.

Ask again with a city that is available, or retry later. When no other place has room either, `error` says `Try again in a few minutes.`

## Values that are refused

`400` with code `INVALID_REGION`:

* A word Orgo does not know, such as `"mars"`, or a value that is not a string: `region must be "us", "eu", "apac" or a city code: "nyc", "ash", "mia", "chi", "dal", "lax", "sjc", "lon" or "syd".`
* Any location with `os` `macos`, `android` or `ios`: `A region can be chosen for Linux and Windows computers.`

Older clients sent three letter codes, such as `"dfw"` or `"sjc,lax"`. A three letter code that is not a city above, or a comma separated list, is read as no choice, so those clients keep working. Send one value: `"lon,syd"` is a list, so it is read as no choice too.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.