Ready before you ask.

A warm pool keeps sandboxes from a template already booted, so when your agent asks for one it gets a running microVM straight away.

Sandboxes › Warm pools

Warm pools

A warm pool keeps sandboxes from a template already booted, so when your agent asks for one it gets a running microVM straight away.

Warm poolillustration, not to scale
TemplateReadyClaimed in the last minutePool
python-3.1283boots 3 more
node-2261boots 1 more
go-1.2540full
Start
In seconds
Isolation
A pooled sandbox has never run anyone’s code before you claim it
Templates
A pool per template
Billing
You pay from the moment you claim it

How it works

Three steps, the same from the API, the CLI or your agent over MCP.

01Booted ahead

The pool keeps sandboxes from each template ready.

02Claimed

Your agent is handed one that is already running, so it starts in seconds.

03Refilled

The pool boots a replacement for the next claim.

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