Regions
Every Computer and every Sandbox is created in exactly one region and stays there for its lifetime. A resource does not span regions, and there is no live migration between them today.
Available regions
| Slug | Location | City | Status |
|---|---|---|---|
us-west | US West | Los Angeles, CA | Live |
us-east | US East | New York, NY | Live |
us-mia | US East 2 | Miami | Live |
All three are generally available and none is restricted. us-west is the default when you do not specify a region.
Pin a resource to a region
Pass region on create; the same field works on Computers and Sandboxes.
If you omit region, Computers and Sandboxes both default to us-west, and the response still includes the resolved region. You can change your tenant’s default region in dashboard settings; the override applies to API calls that omit a field.
| Status | Error | Cause |
|---|---|---|
| 400 | invalid_region | Slug not in the list above |
| 409 | region_unavailable | Transient capacity issue; retry or pick another |
List regions
GET /api/v1/regions returns the regions available to your tenant, so a region picker in your UI does not need a hardcoded list.
curl https://api.miosa.ai/api/v1/regions
-H "Authorization: Bearer $MIOSA_API_KEY"Each entry has id (the region slug), label, active_nodes, available, small_slots_free, and a headroom object with free slots per size and the region’s total and used memory. See the Regions API for the full response shape.
What is region-local
- Compute. The VM runs in one region. All VM sizes are available in every region for both Computers and Sandboxes.
- Data. Data services and volumes live in the region of the resource that uses them.
- Latency. The three US sites are roughly equidistant for the median US user, so compute performance is effectively identical. Pick by data residency first; otherwise pick by proximity to your users or CI runners, which lowers RTT for desktop streaming and terminal round-trips.
Cross-region
There is no live migration between regions. To run work in more than one region, create one resource per region, and federate bring-your-own hosts with OpenComputers if you want a single logical workspace across them.
EU and APAC regions are on the roadmap and will appear in GET /api/v1/regions alongside the current three.