Islo
Islo provides persistent, isolated cloud computers in which AI coding agents can run commands, browsers, and application services. Developers use its sandboxes to run agents and reconnect to their work later.
| Pricing model | Hourly rates for provisioned vCPU, memory, and disk while running; no charge when stopped |
|---|---|
| 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.07 per CPU-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. | No fixed limit documented; an optional active-runtime limit can be set |
| Isolation The isolation technology between sandboxes. | MicroVM with its own kernel |
| GPUs Whether GPU instances are available for sandboxes. | – |
| Docker Whether Docker containers can run inside the sandbox. | – |
| SDKs | Python, TypeScript, Go |
✓ yes · ✕ no · – no cited public fact.
Lifecycle policies must be set when a sandbox is created; they cannot be changed afterward.
Sources
- https://islo.dev/sandboxes/
- https://docs.islo.dev/getting-started/quick-start.md
- https://islo.dev/pricing
- https://docs.islo.dev/concepts/sandbox-lifecycle
- https://docs.islo.dev/cli/snapshots.md
Last verified 2026-10-06. Corrections land through the update log.