Skip to content

Sandboxes · 1 November 2026

spreadFrom keeps a new sandbox off its peers' servers

POST /v1/sandboxes accepts spreadFrom again: 1 to 16 IDs of your own sandboxes. The new sandbox starts on a server that none of them is running on, and stays apart from them each time it is placed again. When no other server has room, the create returns 503 capacity_unavailable immediately and nothing is made or charged. An ID this key cannot read returns 400 invalid_request. Snapshot IDs are not accepted in spreadFrom, and a create that copies a snapshot returns 501 feature_unavailable when it sets spreadFrom.

Same day.

Cut your cloud billby 75%.

No card to start. Billed by the second after.

Start free, no card