Docker Cloud Sandboxes

https://www.docker.com/products/docker-sandboxes/

Docker Cloud Sandboxes provide Docker-managed, isolated environments in which AI coding agents and automated workflows run commands and tools. Developers can control them through a CLI or API, or work with an agent through a cloud terminal.

Pricing model Pay-as-you-go, metered per second of runtime at the selected vCPU and memory size
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. Micro (1 vCPU, 2 GiB): $0.07 per hour
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. –
Max runtime The longest a sandbox may run. 24 h per session
Isolation The isolation technology between sandboxes. Docker-built microVM with its own kernel
GPUs Whether GPU instances are available for sandboxes. –
Docker Whether Docker containers can run inside the sandbox. ✓
SDKs TypeScript

✓ yes · ✕ no · – no cited public fact.

Volume-backed cloud sandboxes cannot be stopped.

Sources

Last verified 2026-10-03. Corrections land through the update log.