Sailboxes
https://sailresearch.com/sailboxes
Sailboxes are persistent, kernel-isolated Linux virtual machines built as execution environments for long-horizon AI agents. They support Docker-in-Docker, provide root access, and allow workloads to pause, resume, and fork without losing in-memory state. A CLI/TUI and SDKs in Python, TypeScript, and Rust are provided.
| Pricing model | Observed-usage billing for CPU, RAM, and disk, plus a one-time size-based creation charge on the Free plan and separate volume-storage charges |
|---|---|
| Pricing The headline compute price as the provider states it. Sorting ranks prices stated per vCPU over time, converted to hourly. Other pricing models sort after, unranked. | $0.015 per used vCPU-hour; $0.008 per used RAM GiB-hour; $0.0007 per used NVMe disk GiB-hour; $0.000411 per volume-storage GiB-hour; $0.005-$0.012 per creation on Free |
| Free while idle Whether a stopped, paused, or sleeping sandbox costs nothing. | ✓ |
| Elastic Resources flex with what the sandbox actually uses, and the bill follows: yes when the provider bills on active or observed use, no when capacity is reserved or allocated and billed while it runs. | ✓ |
| Memory snapshots Whether RAM state survives a pause and resume, not just disk. | ✓ |
| Wake on request Whether a stopped sandbox wakes automatically on inbound traffic. | ✓ |
| Start / resume Typical time from create or resume to running. Sorting ranks stated times, converted to seconds; claims with no figure sort after, unranked. | <2s start/resume; waking from sleep takes a few seconds |
| Max runtime The longest a sandbox may run. | Unlimited by default; optional max lifetime up to 4,294,967,295 s |
| Isolation The isolation technology between sandboxes. | Kernel-isolated Linux VM (full VM, not microVM) |
| GPUs Whether GPU instances are available for sandboxes. | ✕ |
| Docker Whether Docker containers can run inside the sandbox. | ✓ |
| SDKs | Python, TypeScript, Rust |
✓ yes · ✕ no · – no cited public fact.
Checkpoints save a Sailbox's writable disk and memory, not a version of its shared volumes: volume changes remain shared between the source and its children, and restoring an older checkpoint does not roll them back. If Sail cannot resume the saved memory, a checkpoint child starts cold with its disk intact and no saved processes.
Sources
- https://www.sailresearch.com/sailboxes
- https://docs.sailresearch.com/reference/python-sdk
- https://docs.sailresearch.com/reference/typescript-sdk
- https://docs.sailresearch.com/reference/rust-sdk
- https://docs.sailresearch.com/sailboxes-lifecycle
- https://docs.sailresearch.com/sailboxes-images
- https://sailresearch.com/
- https://docs.sailresearch.com/sailboxes
- https://docs.sailresearch.com/pricing
- https://docs.sailresearch.com/sailboxes-pricing
- https://sailresearch.mintlify.app/sailboxes-pricing
- https://sailresearch.mintlify.app/sailboxes-networking
- https://www.sailresearch.com/blog/introducing-sailboxes-persistent-sandboxes
- https://sailresearch.com/sailboxes
Last verified 2026-10-01. Corrections land through the update log.