Skip to main content
A sandbox runs in one region for its whole life. Region names are the same as those of Edge Compute functions. More regions Preview are added as separate deployments. A client learns every region’s base URL from the token response.

Choosing a Region

region on a create picks the region. Without it, the control plane sends the create to the default region. A region the control plane does not know is refused with 404 and the title Sandbox region not found. A create sent directly to a region’s data plane with another region’s name is refused with 422 wrong_region.
Request

Region in IDs

Every ID carries its region, so no lookup is needed to find a resource. The control plane forwards each request to the data plane of the region in the ID, and returns its answer unchanged. A client holding a token sends it to that data plane directly.

What Stays in a Region

  • Sandboxes. A sandbox never moves. A pause, a resume, a snapshot, and a fork all happen in its region.
  • Snapshots and forks. A sandbox created from a snapshot or a fork is in its source’s region.
  • Templates. A template exists in the region where it was created. A template with the same name in another region is a separate template, created there.
  • Quotas. The concurrency quota and the template cap apply per organization and per region.

Listing Across Regions

GET /v2/compute/sandbox at the control plane asks every region at once and merges the results, newest first. A region that does not answer is named in unavailable_regions, and the response is still 200. ?region=us-east-1 limits the list to one region, and an unknown region is refused with 404. At a region’s data plane, the list holds that region’s sandboxes only.