# Islo

Persistent microVM sandboxes ("Islo Machines") for coding agents, with a credential-injecting gateway, billed per CPU-hour, GB-hour of memory and GB-hour of disk.

- Operated by: Incredibuild
- Status: Active [1]
- Website: https://islo.dev
- Categories: Agent sandboxes, Devboxes
- Checked: 31 Oct 2026

## Islo Machines (Agent sandboxes)

- Price: $0.07 /vCPU-h (+ $0.04 per GB-hour)
- 1-hour session: ≥ $0.3 (2 vCPU / 4 GB · rank 24 of 26)
- Fleet month: ≥ $2,640 (50 × 8 h × 22 days)
- Billed on: Running time (increment unknown)
- Isolation: unknown (max session unknown)

### Billing

- Payment: Metered: usage billed afterwards [1]
- Plan minimum: None [1]
- Billing increment: unknown (Not published; the pricing page only says charges apply while the machine runs) [1]
- Minimum charge: unknown (Not published) [1]
- Per-job fee: None [1]

### Runtime

- Billed on: Running time [1]
- Isolation: unknown (A microVM with its own kernel per Islo Machine; the hypervisor is not named) [1]
- Max session: unknown (Machines stay up for hours; no maximum is published (pause_after is an optional per-sandbox cap)) [1]
- Concurrent sandboxes: unknown (Not published) [1]
- Largest vCPU: unknown (vCPU count is configurable (--cpu); no maximum is published) [1]
- Largest memory: unknown (Memory is configurable (--memory, MB); no maximum is published) [1]

### Lifecycle

- Survives a stop: Disk [3]
- Snapshots: Yes [3]
- Pause and resume: Yes [3]
- Fork: Disk copy [3]
- Compute billed while stopped: No [3]
- Auto-stop: unknown (Idle pause (pause_after_idle) is opt-in per sandbox; no default is published) [3]
- Start time (vendor claim): unknown (Not published) [3]

### Capabilities

- GPU: unknown (Not mentioned on Islo's pages) [4]
- Desktop: Browser [4]
- Coding agents installed: Claude Code, Cursor CLI, Codex [4]
- Agent prompt API: Yes [4]
- SSH: Yes [4]
- Docker inside: unknown (Not stated in the docs) [4]
- SDKs: Python, TypeScript, CLI, REST [4]
- SOC 2: unknown (The security page lists no certification; it refers compliance questions to support) [4]

### Storage and network

- Disk included: None [1]
- Extra disk: unknown (Published per hour only: $0.0007 per GB-hour of disk) [1]
- Snapshot storage: unknown (Not published) [1]
- Egress: unknown (Not published) [1]

### Platform

- Regions: unknown (The API lists tenant compute regions, but no region names are published) [2]
- Your cloud (BYOC): Yes [2]
- Self-host: unknown (BYOC deploys the control plane in your VPC; an open-source runtime is not stated) [2]

### Free allowance

- Minutes a month: None [1]
- Credit a month: None [1]
- One-time credit: unknown (Sign-up credits with no card required; the amount is not stated on Islo's pages) [1]

### Prices

| Resource | Price | Per hour |
|---|---|---|
| per vCPU | $0.07 /h [1] | $0.07 |
| per GB of memory | $0.04 /h [1] | $0.04 |

- Pay as you go: $0.07 per CPU-hour (per core while the machine runs), $0.04 per GB-hour of provisioned memory, $0.0007 per GB-hour of disk; no plans.
- Pausing (manual or by lifecycle policy) snapshots the VM and releases compute; paused machines keep their filesystem and can auto-resume on activity.
- The default image includes Claude Code, Cursor CLI and Codex CLI; `islo use --agent claude --task "..."` starts an agent with a prompt in the background.
- BYOC (control plane and machines in your VPC) is offered through enterprise deals.
- Harbor users get $250 in credits (docs.islo.dev/integrations/harbor).

## Sources

[1] https://islo.dev/pricing (checked 31 Oct 2026)
[2] https://islo.dev/security (checked 31 Oct 2026)
[3] https://docs.islo.dev/concepts/sandbox-lifecycle (checked 31 Oct 2026)
[4] https://docs.islo.dev/cli/agent-integration (checked 31 Oct 2026)