Skip to main content

​
Rigbox

Rigbox is an open platform for running untrusted code in secure, isolated Firecracker micro-VMs. Each workspace is a full Linux VM with SSH access, app routing, snapshots, and live metrics — provisioned and managed entirely through the API.
New to Rigbox? Start with the Quickstart to deploy your first workspace in under a minute.

​
Key capabilities

Workspaces

Provision isolated Firecracker VMs with configurable CPU, memory, and disk. Start, stop, snapshot, and delete through the API.

Apps & Routing

Expose ports from inside your workspace as public subdomains on rigbox.dev. Control visibility and monitor health.

AI Configuration

Run AI workloads with managed API keys or bring your own. Credit tracking, provider routing, and usage analytics built in.

Quick Deploy

Go from zero to a running workspace in one API call using pre-configured templates.

Tools & Automation

Install development tools into workspaces. Define setup scripts and service specs to automate initialization.

Snapshots

Capture and restore full workspace state. Useful for checkpointing long-running work or creating reproducible environments.

​
Architecture

Rigbox uses a two-zone security model:
  • Control Plane — holds agent runtimes, API keys, and user state. Runs the API gateway, auth service, and admin portal.
  • Data Plane — runs untrusted generated code in Firecracker VMs with no access to platform secrets.
All communication between zones goes through authenticated internal APIs over an encrypted mesh network.

​
Integration guides

Building on top of Rigbox? These guides map exactly which API endpoints power each frontend:

Sandbox

How sandbox.rigbox.dev uses the API for workspace lifecycle, terminal access, and log streaming

Clawd

How clawd.rigbox.dev uses the API for AI bot deployment, billing, and managed proxy

Clawd Runtime

Internal service contracts for the managed AI proxy, credit enforcement, and config injection

​
Base URL

https://api.rigbox.dev/api
All endpoints are relative to this base. Authentication is required for most endpoints — see Authentication for details.

​
Response format

All responses are JSON. Errors include a message field: 
{
  "message": "Workspace not found"
}
StatusMeaning
2xxSuccess
401Missing or invalid authentication
403Insufficient permissions
404Resource not found
429Rate limited — retry with exponential backoff
5xxServer error