Agent Sandboxesagentsandboxes.org
Head-to-head

exe.dev vs Upstash Box

Answer in brief

Choose exe.dev for developers who want a fleet of persistent root VMs they and their agents reach over SSH, at a flat monthly price; choose Upstash Box for long-lived per-user coding-agent workspaces where idle time should cost nothing. exe.dev uses VM (VMM per VM) isolation; Upstash Box uses Docker container isolation.

By the Agent Sandboxes editors · Updated

Key differences between exe.dev and Upstash Box

  • Isolation: exe.dev uses VM (VMM per VM); Upstash Box uses Docker container.
  • Session length: No cap (exe.dev) versus No cap (idle pause 1 h / 6 h) (Upstash Box).
  • SDKs and interfaces: Only exe.dev lists HTTPS API. Only Upstash Box lists JavaScript/TypeScript and Python.

What they have in common

  • Both companies are based in the United States.
  • Both are hosted platforms.
  • Neither is open source.
  • Both support snapshots.
  • Both list CLI and MCP server.

exe.dev vs Upstash Box at a glance

Attributeexe.devUpstash Box
What it isPersistent root VMs for people and their agents, driven entirely over SSH (or the same commands via HTTPS and MCP), with replicated NVMe storage, VM copies and flat-rate CPU/RAM pools in nine regions.Persistent Docker-container "boxes" for coding agents with Claude Code, Codex, OpenCode and Cursor built in, billed on active CPU time rather than wall-clock.
TypeHosted platformHosted platform
IsolationEach VM runs as its own VMM process inside a shared CPU/RAM pool; hypervisor not namedDocker container per box with its own filesystem, process tree and network stack; no VM boundary (the product page itself contrasts this with microVM providers)
Open sourceNoNo
Self-host / BYOCNot documented / YesNot documented / Not documented
SDKsCLI (over SSH), HTTPS API, MCP serverJavaScript/TypeScript, Python, CLI, MCP server
Cold start (vendor claim)API explorer: creating a VM takes "about a second" (vendor claim)Not documented
Max sessionVMs are long-lived and persistent with no session limit; stopped standalone VMs keep their diskNo maximum stated (launch post: "You can keep Upstash Box forever"); idle boxes auto-pause after 1 hour on the free plan and 6 hours on paid plans, and keep-alive boxes (paid) never pause
PersistencePersistent VM disks on local NVMe, streamed to other machines in the regional cluster for durability; cp copies a VM's disk and config; S3 backups (development preview) with incremental 1 MB chunks and 7-day minimum retention; no memory snapshots documentedFilesystem (files, packages, git history) persists across pauses and resumes on durable block storage; snapshots capture the filesystem plus agent/runtime settings and can seed many new boxes; memory is not stated to survive a pause
Snapshots / pauseYes / Not documentedYes / Yes
GPUNot mentionedNot mentioned in the docs or pricing
NetworkingEgress all by default or integrations (blocks the public internet, keeps metadata and attached integrations); public or private HTTPS app URLs via an SNI/Host-routed TLS proxy and global load balancer; SSH with public-key auth only; an LLM gateway adds provider keys outside the VMOutbound allow-all by default (HTTP, HTTPS, DNS, WebSockets, raw TCP); deny-all or a custom allow-list of domains and CIDRs with denied CIDRs can be set at creation or updated live; private IP ranges and cloud metadata endpoints are always blocked; "Attach Headers" inject secret HTTP headers on the host so keys need not enter the box; SSH access by box ID
PricingPersonal: $15/month for a 2 vCPU/4 GiB pool, $35 (4/8), $75 (8/16), $155 (16/32), up to 50 VMs, 100 GiB disk, 200 GiB bandwidth. Work: $75/month per team ($37.50 for the first 3 months) including 2 vCPU/4 GiB, extra capacity $0.105 per 2 vCPU/4 GiB unit-hour, pools of 2-512 vCPUs, 1,000 VMs per pool. Standalone VMs metered per second at the same unit rate ($0.0525/h for 1 vCPU/2 GiB to $0.84/h for 16 vCPU/32 GiB). Enterprise custom with dedicated hardware and AWS/GCP VPCPay as you go per active CPU hour: Small 2 vCPU/4 GB $0.10, Medium 4 vCPU/8 GB $0.20, Large 8 vCPU/16 GB $0.40; memory not billed; storage $0.10/GB-month with 10 GB included per box; keep-alive (always-on) boxes $8, $16 or $32 per box per month. The pricing page gives two different disk limits for Medium boxes (30 GB in the size table, 20 GB in the FAQ)
Free tier7-day trial of the Personal plan, no card required when linking a paid ChatGPT subscription; no permanent free tierFree plan: up to 10 concurrent boxes, 5 CPU hours per month, 2 vCPU/4 GB/10 GB boxes, 1-hour idle timeout
ComplianceNot documentedNot documented
RegionsLos Angeles, New York, Dallas, Frankfurt, Tokyo, Sydney, Singapore, London (Oregon closed to new accounts); the account "lobby" server is in the United StatesAWS us-east-1 only, with more regions planned
Company headquartersBerkeley, California, United StatesCalifornia, United States
Good fit forDevelopers who want a fleet of persistent root VMs they and their agents reach over SSH, at a flat monthly priceLong-lived per-user coding-agent workspaces where idle time should cost nothing

Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose exe.dev

  • You want many small persistent VMs for a flat monthly price rather than per-second metering
  • You and your agents work over SSH and want the same commands via HTTPS or MCP
  • You need regions in Asia-Pacific and Europe as well as the US
  • You want app URLs and an LLM key gateway without running a proxy yourself

Reasons to choose Upstash Box

  • You want a box an agent returns to for days with files and git history intact
  • You need idle time to be free, or a flat monthly price for an always-on box
  • You want Claude Code, Codex, OpenCode or Cursor preconfigured rather than installing an agent yourself
  • You are already on Upstash and want the same console, API keys and MCP server

Trade-offs to check first

  • exe.dev: Hypervisor and compliance are not documented
  • exe.dev: Language SDKs are not documented; the API is one POST endpoint wrapping SSH commands with a 30-second timeout and no stdin
  • Upstash Box: Container isolation rather than a VM; the product page describes microVMs as "a stronger boundary than Box's container"
  • Upstash Box: Single region (AWS us-east-1)

Both are worth piloting with your own image and region. See the full exe.dev profile and Upstash Box profile, or the complete comparison.

More comparisons

Frequently asked questions

Is exe.dev or Upstash Box better for AI agents?
Neither is better for every workload. exe.dev suits developers who want a fleet of persistent root VMs they and their agents reach over SSH, at a flat monthly price. Upstash Box suits long-lived per-user coding-agent workspaces where idle time should cost nothing.
What is the difference between exe.dev and Upstash Box?
exe.dev uses VM (VMM per VM); Upstash Box uses Docker container. Session length: No cap (exe.dev) versus No cap (idle pause 1 h / 6 h) (Upstash Box). Only exe.dev lists HTTPS API. Only Upstash Box lists JavaScript/TypeScript and Python.
Which is open source, exe.dev or Upstash Box?
Neither is open source.
How do exe.dev and Upstash Box isolate code?
exe.dev: Each VM runs as its own VMM process inside a shared CPU/RAM pool; hypervisor not named. Upstash Box: Docker container per box with its own filesystem, process tree and network stack; no VM boundary (the product page itself contrasts this with microVM providers).
How does exe.dev pricing compare with Upstash Box?
exe.dev: Personal: $15/month for a 2 vCPU/4 GiB pool, $35 (4/8), $75 (8/16), $155 (16/32), up to 50 VMs, 100 GiB disk, 200 GiB bandwidth. Work: $75/month per team ($37.50 for the first 3 months) including 2 vCPU/4 GiB, extra capacity $0.105 per 2 vCPU/4 GiB unit-hour, pools of 2-512 vCPUs, 1,000 VMs per pool. Standalone VMs metered per second at the same unit rate ($0.0525/h for 1 vCPU/2 GiB to $0.84/h for 16 vCPU/32 GiB). Enterprise custom with dedicated hardware and AWS/GCP VPC. Upstash Box: Pay as you go per active CPU hour: Small 2 vCPU/4 GB $0.10, Medium 4 vCPU/8 GB $0.20, Large 8 vCPU/16 GB $0.40; memory not billed; storage $0.10/GB-month with 10 GB included per box; keep-alive (always-on) boxes $8, $16 or $32 per box per month. The pricing page gives two different disk limits for Medium boxes (30 GB in the size table, 20 GB in the FAQ). Rates change, so check the exe.dev and Upstash Box pricing pages before deciding.
How long can sessions run on exe.dev and Upstash Box?
exe.dev: VMs are long-lived and persistent with no session limit; stopped standalone VMs keep their disk. Upstash Box: No maximum stated (launch post: "You can keep Upstash Box forever"); idle boxes auto-pause after 1 hour on the free plan and 6 hours on paid plans, and keep-alive boxes (paid) never pause.
Do exe.dev and Upstash Box support snapshots or pause and resume?
exe.dev: snapshots yes, pause and resume not documented. Upstash Box: snapshots yes, pause and resume yes.

Sources

  1. exe.dev
  2. exe.dev/docs
  3. exe.dev/pricing
  4. exe.dev/security
  5. upstash.com/docs/box/overall/how-it-works
  6. upstash.com/docs/box/overall/getstarted
  7. upstash.com/docs/box/overall/snapshots
  8. upstash.com/docs/box/overall/network-policy

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). exe.dev vs Upstash Box. agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/exe-dev-vs-upstash-box/