Set up once. Start from there every time.
Save a sandbox after the slow part, like installing dependencies, and start new sandboxes from that point instead of from scratch.
Snapshots
Save a sandbox after the slow part, like installing dependencies, and start new sandboxes from that point instead of from scratch.
01$ sandscale exec sbx_9a20 -- npm ci
02added 1,214 packages in 48s
03$ sandscale snapshot sbx_9a20 --name deps-installed
04snapshot deps-installed saved
05$ sandscale up --from deps-installed
06sbx_9a21 running from deps-installed
- What is saved
- The sandbox’s files, as they are when you take the snapshot
- Starting from one
- New sandboxes start with the same files and the same template
- Where
- In your sandboxes’ region, US East or EU, or your own cloud
- Audit
- Every snapshot and every start from one is in the audit log
How it works
Three steps, the same from the API, the CLI or your agent over MCP.
01Set it up
Start from a template and do the slow work once: clone, install, build.
02Snapshot it
Save the sandbox under a name. The running one carries on.
03Start from it
New sandboxes boot from the snapshot with everything already in place.
Which plans
Snapshots come with Pro and up, because they use storage. Free sandboxes can still pause and resume.
See pricing →Give every agent
a box of its own
Start free with 100 vCPU-hours a month. Upgrade when your agents need more.
A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI