InstaBox

Developers building AI agents that need to write code, browse the web, or run Android apps need isolated, disposable compute environments for each agent session. Standing up and tearing down cloud VMs by hand, wiring up exec and file access, and managing lifecycle (start, stop, pause, snapshot, resize) is slow and not built for programmatic, high-volume agent use. Generic containers or VMs also lack agent-specific conveniences like streaming command output, background jobs, or prebuilt templates with browsers and Android already installed.

InstaBox provisions a Firecracker microVM per agent on request, reachable through a JSON HTTP API (api.instabox.sh) or an `instabox` CLI, with one-command setup via `npx instabox@latest sh` that also installs agent skills for Claude, Gemini and other agent runtimes. Machines come from templates such as `agent-browser` (Debian, Docker, Node, Python, Go, Rust, a desktop and Chromium), `android` (Android 14 as a container with adb, no emulator), and `ci` (Ubuntu), or from a saved snapshot. It exposes an `exec` endpoint that runs shell or argv commands with optional real-time streaming, plus background jobs, file transfer endpoints for reading output safely, a 20 GiB persistent `/data` disk, automatic swap, idle auto-pause, resizing of vCPU/memory/disk on paid plans, and OOM-kill reporting.