Sandboxes

Disposable VMs for AI agents,
billed by the second.

A sandbox is a Linux VM with its own vCPUs and memory. Create one for each run, then delete it.

# create a sandbox, run a command in it, delete it
$ ssh exe.dev new --sandbox --name=sbx1
$ ssh sbx1.exe.xyz nproc
2
$ ssh exe.dev rm sbx1

# the same run over the HTTPS API
$ exe() { curl -sX POST https://exe.dev/exec \
    -H "Authorization: Bearer $EXE_TOKEN" -d "$*"; }
$ exe 'new --sandbox --name=sbx1'
$ exe 'ssh sbx1 nproc'
2
$ exe 'rm sbx1'

A sandbox an agent can actually live in.

It is a Linux VM, not a container in a shared cluster. Your agent can install packages, run services, and come back to the same disk later.

Its own capacity. Reserved vCPUs and memory that your other VMs don’t share.
Isolated. A virtual machine, not a container on a shared kernel.
Persistent. Its disk stays until you delete the sandbox.
Reachable. An HTTPS hostname at name.exe.xyz, private until you share it.

An agent session

# your agent, from anywhere
$ ssh exe.dev new --sandbox --name=agent-sbx
$ ssh agent-sbx.exe.xyz \
    "sudo apt-get install -y ripgrep && rg TODO"

# 30 minutes later, the agent comes back
$ ssh agent-sbx.exe.xyz cat notes.md

Tokens your security team will sign off on.

An API token carries its permissions inside it. --cmds lists the commands an agent may run, and --exp sets when the token stops working.

A token that expires in a day

$ ssh exe.dev ssh-key generate-api-key \
    --label=agent --cmds=new,rm,ssh --exp=1d

# revoke it early
$ ssh exe.dev ssh-key remove agent

Secrets your agent can use, but never see.

An integration adds the auth header on the way out. The key stays on exe.dev, out of the VM and out of the model’s context.

Stripe for every VM tagged sandbox

$ ssh exe.dev integrations add http-proxy \
    --name=stripe --target=https://api.stripe.com \
    --bearer=sk_live_... --attach=tag:sandbox
$ ssh exe.dev new --sandbox --tag=sandbox

# inside the sandbox, no key in sight
$ curl https://stripe.int.exe.xyz/v1/balance

Pay by the second.

$0.105 / hour

for each unit of 2 vCPUs and 4 GiB memory

$0.00175 per minute

about $0.000029 per second ($0.105 ÷ 3,600)

Metered from new until the sandbox stops or you rm it. No minimum, no rounding up to the hour.

Run (2 vCPUs / 4 GiB unless noted)	Cost
10 seconds	$0.0003
1 minute	$0.00175
10 minutes	$0.0175
1 hour	$0.105
8 vCPUs / 16 GiB for 15 minutes	$0.105
1,000 runs of 2 minutes each	$3.50

Personal

Billed on top of your plan.

Work

Counts against the included capacity together with your pools.

Enterprise

Covered by your contract.

Stopped sandboxes are not billed for vCPUs or memory. They keep their disk.

Usage adds up on your monthly invoice, rounded to the cent.

How standalone VMs work → How usage is measured →

There are many sandboxes for AI agents,
but this one is a real computer.

Get started Read the docs