Key capabilities
- Isolated execution per sandbox pod with resource limits
- REST and WebSocket APIs for command execution and streaming output
- File read and write APIs for workspace workflows
- Prebuilt runtime with Node.js, Python, Go, Rust, and common CLI tooling
- Automatic cleanup with per-sandbox timeouts
- Optional warm pool support for faster startup
Architecture overview
Hosted API quickstart
- Register and receive an API key.
- Create a sandbox with a timeout.
- Execute commands inside the sandbox.
TypeScript SDK example
Hosted and self-hosted are the same controller and API, so code written
against one runs unchanged against the other. Start hosted; move to
self-hosted when isolation or data residency requires it, not because the API
is different.
Self-hosted deployment
At a high level, deployment includes:- Build and push the sandbox and controller images.
- Apply the Kubernetes manifests in
k8s/. - Configure secrets for JWT signing and provider keys.
- Deploy the controller and verify pod creation.
API summary
Configuration highlights
Security and isolation
- Sandboxes run as non-root with dropped Linux capabilities.
- Seccomp profiles and resource limits are enforced at the pod level.
- Network policies restrict egress to HTTPS and DNS.
Next steps
Sandbox quickstart
The hosted path in full.
Deployments
Self-hosting on EKS, GKE or AKS.
Security guide
Isolation before untrusted code runs.
Node SDK
The typed client used above.