Next to KVM instances, Kubernetes clusters and managed databases, customers can launch sandboxes: Firecracker microVMs built for AI coding agents, disposable CI runners, preview environments and batch jobs, reachable through an E2B-compatible API.
pip install e2b
export E2B_API_KEY=<key from the panel>
export E2B_API_URL=https://<your panel host>/api/e2b
from e2b import Sandbox
sbx = Sandbox.create("sandbox-base")
print(sbx.commands.run("echo hi").stdout)
sbx.kill()Ready-made kits for AI coding agents, installed from a catalog that VirtConsole signs, so a sandbox starts with the agent already in place.
Claude Code, Codex CLI, GitHub Copilot CLI, Gemini CLI, OpenCode, OpenCode 2 and a plain Shell kit, each on the same Debian 13 base with git, Python and Node, with the agent pinned to a specific version.
Kits are pulled from the Kits Hub with signature checks and installed by the provider. A new agent version never changes a kit underneath a customer, and older versions stay selectable in the launcher.
Build a kit from a Dockerfile, a container image or a git repository on top of a platform base kit, and use a saved registry credential for private images. Every build is a new version.
The launcher reads like a sentence: pick the kit, the secrets, the location, the size and the lifetime, then press Launch.
Keep API keys as encrypted, write-only secrets in the account and tick them at launch. They arrive as environment variables inside the sandbox, so nobody pastes a key twice.
Save a GitHub token once and git inside any sandbox signs in to github.com with it, so clone and push over HTTPS work without a prompt. The helper sends the token to github.com.
Copy a launch as a cURL command, or generate OpenTofu and E2B starting points. Saved secret values are replaced with placeholders. Use the API or the panel to preserve selected MCP tools; the E2B snippet uses the account and kit defaults for launch settings. Save a launch as a preset to reuse it in one click.
Give the agent in a sandbox access to external services without handing the sandbox your credentials.
Add hosted tool servers from a provider catalog, or your own Streamable HTTP MCP server with OAuth sign-in, a static token or no sign-in.
Sign-in tokens are managed by the panel and delivered to the node gateway. The sandbox receives local gateway endpoints and server metadata, without upstream provider credentials, and each person connects with their own account.
Choose which tool servers each sandbox can use at launch, and see their status on the sandbox page. Admins control the gateway switch and per-provider registrations.
One artifact, versioned, that runs the same way every time it boots.
A Dockerfile on top of a platform base image, an existing container image imported from any registry, or a git repository the platform builds for you.
Debian 13, Ubuntu 24.04, Ubuntu 26.04, AlmaLinux 10 and Amazon Linux 2023 are published and signed by VirtConsole and synced into every installation automatically, with Rocky Linux 10 available as an option. No customer or admin ever supplies a kernel or a root filesystem.
A sandbox always runs a named kit version. Rolling forward or back is picking a different version, not rebuilding anything.
The launcher asks for a kit and version, a location, a size and a network. From there, it is running.
Leave it uncapped, or set a maximum of up to 8 hours and decide whether the sandbox pauses or is killed when time runs out. Extend a running one’s timeout at any point.
Pause automatically after a period of no activity, or mark a sandbox always-on so it never idles. A paused sandbox keeps its memory and disk on the node and resumes exactly where it left off.
The same primitives as a KVM instance, sized for compute that lives for minutes instead of months.
A sandbox gets a public IP, a VPC address, or both. VPC-only sandboxes leave through the VPC’s NAT gateway, and the same security groups apply.
Pick account SSH keys at launch time and they land in authorized_keys before first boot. The show page prints the ssh command for the public IP, or the VPN gateway route for a VPC-only sandbox.
Expose a port on a wildcard sandbox domain or attach a custom domain; certificates are issued and renewed by the platform.
A terminal into the running sandbox from the panel, a streaming console log, and CPU, memory, disk and network charts sampled every 15 seconds on the node.
Sell sandboxes to developers building agents, without asking them to learn a new SDK.
Point the official e2b SDK at your panel with two environment variables, E2B_API_KEY and E2B_API_URL, and existing Python or JavaScript code can run against your own infrastructure.
The API keys page ships copy-paste quick starts in Python, JavaScript, the CLI, cURL, the Anthropic SDK and the OpenAI SDK, plus docs for LangChain, the Vercel AI SDK and the Pi coding agent.
A REST API covers sandbox lifecycle, kits and connectors. Existing /api/microvm paths and image field names remain compatible; some launcher conveniences use panel-specific requests.
Disposable compute for agent and CI workloads.
Install the provider’s GitHub App on an organisation and every CI job gets its own sandbox, booted from the kit and plan you choose.
Register a GitLab runner token the same way. No shared runner state between jobs, no idle runner fleet.
Connectors create a fresh sandbox for each selected job and clean it up afterward.
Enabled per hypervisor group, the same switch already used for managed databases and load balancers.
Walks through setup and says what is missing before customers can use the feature: nodes reporting, Firecracker version, the group switch, base kit catalog, plans mapped through a plan group, networking, sandbox domain, wildcard certificate and the API mount. Each failing check links to the page that fixes it.
Plans carry vCPU, memory and disk; plan groups map plans to locations from the same drawer design used across Cloud Service, managed databases, load balancers, volumes and VPN gateways.
List every customer sandbox with the node’s live view, force-stop a run, audit API key use, and manage connectors, all from the admin panel.
Free 30-day trial. Every feature included. No credit card required.
30 days, every feature, no credit card, VirtConsole installs with the trial active by default. Just run the installer on your own hardware.
Debian 11/12/13 · Ubuntu 22.04/24.04/26.04 · Rocky / Alma / CentOS Stream 9/10 · run as root.