Sandboxes
PreviewA fresh machine for every task, human or agent.
Start a sandbox from a template in seconds, run commands, edit files and open preview ports, then snapshot it or let it expire. Agents drive the same API with scoped keys, and every exec is authorized and audited.
- Pricing
- Per vCPU, memory and disk hour
- Layer
- Compute
- Drive it from
- The console, The API, TypeScript client, MCP, Pipelines, Git, Datasets
Why Sandboxes
Short-lived by design, safe by default.
A sandbox is an isolated environment you start from a template, use and let expire. Developers work in it from the browser, agents drive it through the same API with scoped keys, and every command is authorized and audited.
Exec, files and git
Run commands, stream logs and work with files from the console or the API.
Preview ports
Share a running port behind a signed, expiring link.
Templates and snapshots
Build once, start fresh copies, and save state when you need it.
How it works
Isolated, short-lived environments for developers and AI agents.
In the console
Everything in one place.
Sandboxes lives in the LegionEdge cloud console, next to every other service in the workspace, under one account and one identity.
Pricing
Per vCPU, memory and disk hour
Sandboxes are metered on the vCPU, memory and disk they reserve, for as long as they hold them, with GPU time metered separately when a template asks for one.
- Stopped or paused sandboxes pay for disk only.
- Archived sandboxes pay nothing.
- Your organization sets the longest a sandbox may live, so nothing runs forgotten.
Related products