Key characteristics
- Persistent by default — configure
onTimeout: 'pause'and sandboxes preserve their full state (filesystem + memory) indefinitely. Resume at any time. - Auto-resume — when enabled, paused sandboxes wake automatically when SDK calls or HTTP traffic arrive. No manual state management needed.
- Snapshots — capture a running sandbox’s state and spawn multiple new sandboxes from it. Useful for checkpointing, forking, and rollback.
- Configurable timeouts — sandboxes run for up to 24 hours (Pro) or 1 hour (Base) continuously. Pausing resets the runtime window.
- Isolated and secure — each sandbox runs in its own microVM with network controls, access tokens, and rate limits.
Quick setup: persistent sandbox
Core
Lifecycle
Timeouts, sandbox info, metadata, listing, connecting, and shutdown.
Pause, resume & snapshots
Pause/resume, auto-pause, auto-resume, snapshots, and state transitions.
Commands
Interactive terminal (PTY) and SSH access.
Configuration
Environment variables and storage bucket integration.
Security
Secured access, network controls, and rate limits.
Observability
Metrics, lifecycle events API, and webhooks.
Guides
Runtime customization
Install packages, upload files, and configure sandboxes dynamically.
Git integration
Clone repos, manage branches, push changes.
Proxy tunneling
Route sandbox traffic through a proxy server.
Custom domain
Set up a custom domain for sandbox access.