Give every agent a computer
Full Ubuntu virtual machines for AI agents. Each one is ready in under 90 ms, with root, Docker, and systemd.
From $0.017 an hour, billed by the second.
const headers = { Authorization: `Bearer ${process.env.VMS_API_KEY}`, "Content-Type": "application/json",};const { vm } = await fetch("https://vms.dev/api/v1/sandboxes", { method: "POST", headers, body: JSON.stringify({ size: "medium", name: "agent-42" }),}).then((response) => response.json());await fetch(`https://vms.dev/api/v1/sandboxes/${vm.id}/commands`, { method: "POST", headers, body: JSON.stringify({ command: "npm test", cwd: "/home/user/app" }),});Agents at these teams run on VMS
- Customer logo
- Customer logo
- Customer logo
- Customer logo
- Customer logo
- Customer logo
Fast, isolated, and saved each minute
Your agent installs packages, starts Docker, and runs services under systemd, as it does on a server.
Ready in under 90 ms
A new sandbox takes its first command in under 90 ms, so your agent does not wait for a boot.
A kernel of its own
Each sandbox boots its own Linux kernel under KVM. A kernel panic or a bad module stays inside it.
Saved every minute
Each minute, the sandbox saves its changed files. A stopped sandbox keeps them for 30 days, and the next start restores them.
Fork in one call
Start a second sandbox from the latest snapshot of the first, and let two agents try two fixes.
Control every sandbox from code
One REST API for the full life of a sandbox.
- Commands
- Run a command and stream its output and exit code.
- Files
- Read, write, and delete files, or upload a folder in one call.
- Snapshots and forks
- Stop a sandbox with its disk, then start it again or fork it.
- Templates
- Save a sandbox with your tools, and start new ones from it.
const fork = await fetch("https://vms.dev/api/v1/sandboxes", { method: "POST", headers, body: JSON.stringify({ size: "medium", fromSandbox: vm.id }),}).then((response) => response.json());await fetch(`https://vms.dev/api/v1/sandboxes/${vm.id}`, { method: "PATCH", headers, body: JSON.stringify({ state: "stopped" }),});Pay for the seconds your agents run
Plans start at $20 a month, and the fee comes back as usage credit. Try it for 14 days first.
small$0.017 an hour2 vCPU and 4 GiB of RAMmedium$0.034 an hour4 vCPU and 8 GiB of RAMlarge$0.068 an hour8 vCPU and 16 GiB of RAMxlarge$0.136 an hour16 vCPU and 32 GiB of RAM
- Unused credit carries over for one month.
- Members are free, with no limit.
- Every size on every plan, xlarge included.
- A 14-day trial with 30 hours of medium.
creatingNo usagestartingNo usagerunningBilled by the secondstoppingNo usagestoppedNo usage
A stopped sandbox keeps its disk. The next start boots from it.
Your agent can sign itself up
Your agent can create its own account, connect over MCP, or call the REST API with a key.
- auth.md sign-up
- Point your agent at vms.dev/auth.md. It registers itself, then acts for you after you enter its 6-digit code.
- MCP server
- Connect Claude, Cursor, or Visual Studio Code. The client signs in with OAuth, so you do not paste a key.
- API keys
- Call the REST API with a workspace key. Each key can do only what its scopes allow.
What teams say
A quote from a customer about what their agents run in a sandbox.
Customer nameRole, company A quote from a customer about what their agents run in a sandbox.
Customer nameRole, company A quote from a customer about what their agents run in a sandbox.
Customer nameRole, company
What agents do in a sandbox
- Coding agentsGive each coding agent a full Ubuntu virtual machine where it can install packages, run tests, and start servers.
- Agent evalsRun each eval task in a clean sandbox from one template. Fork many runs from the same state.
- Background agentsStop a sandbox while the agent waits. It starts again with the same files, name, and URL.
Questions
What is a sandbox?
A sandbox is an Ubuntu virtual machine for one agent. It has its own kernel, disk, name, and URL, and it keeps them from create to delete.
How does billing work?
Usage counts each second that a sandbox runs. Starts are free, and a stopped sandbox has no usage charge. A medium sandbox costs $0.034 an hour, and plans start at $20 a month.
Where do sandboxes run?
On bare-metal servers with AMD Ryzen CPUs in Vint Hill, Virginia, in the United States.
How is a sandbox different from a container?
A container shares the kernel of its host. A sandbox boots its own kernel, so code in it cannot reach the host kernel.
Get your agents a workspace
Create a workspace, or copy the setup prompt and let your agent sign itself up.