homemade vs Vercel Sandbox
homemade gives every project its own computers in the cloud, with your repo, your running services, a link for each one, and Claude Code and Codex signed in. Here is how it compares with Vercel Sandbox.
Why people pick homemade over Vercel Sandbox
What you get with homemade that Vercel Sandbox does not give you in the same way.
- homemade is where you do the work: a persistent cloud computer per project or branch, with your repo cloned and services running. Vercel Sandbox is a code-execution backend you call from your app.
- A sleeping computer keeps its memory as well as its disk, so terminals and running processes are still there when it wakes. Vercel's docs describe filesystem snapshots, not running memory.
- SSH and VS Code or Cursor over SSH (
homemade open) are built in, next to a Chat tab and an MCP server. Vercel's pages we read do not state SSH or desktop IDE support. - Every service gets a preview link you can share as public, organization or owner only, and a visit wakes a sleeping computer. Vercel's pages we read do not state access options for exposed ports.
- Claude Code, Codex, OpenCode, pi, Kimi and Grok are installed and signed in on every computer, so you sign in once.
- Simple per-size hourly prices with disk included, plus a free Hobby plan, instead of several meters at once (Active CPU, memory, creations, snapshot storage).
Side by side
The parts that matter when you build with coding agents. Vercel Sandbox facts are from their own pages, checked 20 Nov 2026.
| Feature | homemade | Vercel Sandbox |
|---|---|---|
| Coding agents | homemadeClaude Code, Codex, OpenCode, pi, Kimi and Grok on every computer. Sign in once and every new computer starts signed in. A Chat tab in the dashboard, and an MCP server (homemade mcp). | Vercel SandboxDocs say the default image includes coding agents. Multi-agent isolation gives each agent its own Linux user. Guides cover the Claude Agent SDK and the OpenAI Agents API. Vercel also lists MCP tools for sandboxes. |
| What you get | homemadeA full VM per computer with its own kernel, its own private network and its own firewall. Not a shared container. | Vercel SandboxEach sandbox runs in its own Firecracker microVM with a dedicated kernel, own filesystem and own network namespace. Full root access. |
| Sleep and state | homemadeComputers sleep when idle (after 30 minutes by default, or never on Pro) and keep their disk and running state. Sleeping is free. Kept 7 days on Hobby, 30 on Pro, and forever with the Unlimited sleep add-on. | Vercel SandboxPersistent by default: the filesystem is snapshotted when the sandbox stops and restored on the next call. Snapshots expire 30 days after last use by default (configurable, or none). Default session timeout is 5 minutes. Max session is 45 minutes on Hobby and 24 hours on Pro and Enterprise. The docs describe snapshotting the filesystem, not running memory. |
| Preview links | homemadeA link for every service port, shared as public, organization or owner only. A visit can wake a sleeping computer. Your own domains with the Custom domains add-on on Pro. | Vercel SandboxUp to 15 open ports per sandbox. Docs mention live previews of dev servers. Traffic to and from exposed ports is billed as network. Access control options for exposed ports: Not stated on the pages we read. |
| Editors and SSH | homemadeBrowser terminal and editor, SSH (homemade ssh), VS Code and Cursor over SSH (homemade open), a CLI for macOS and Linux, and an HTTP API. | Vercel SandboxSDK, CLI (sandbox exec with an interactive TTY) and dashboard management. SSH and desktop IDE support: Not stated on the pages we read. |
| Teams | homemadeTeams with projects and members, sharing levels on previews, GitHub pushes as you, PR preview computers and Linear ticket computers. | Vercel SandboxHobby, Pro and Enterprise plans. Spend management, tags, an Observability tab, and Secure Compute for static IPs and VPC peering. |
| Pricing | homemadePro $20/mo includes $20 of usage, then per second by size: nano 0.5 vCPU / 1 GB $0.012/h, tiny 2 vCPU / 4 GB $0.0162/h, small 4 vCPU / 8 GB $0.0324/h, medium 8 vCPU / 16 GB $0.0648/h, large 16 vCPU / 32 GB $0.18/h. Disk included. 1 TB egress a month included, then $0.05/GB. | Vercel SandboxPro and Enterprise list rates (iad1): Active CPU $0.128/hour, provisioned memory $0.0212/GB-hour, $0.60 per 1M creations, snapshot storage $0.08/GB-month, drive storage $0.05/GB-month. Active CPU counts only time the CPU is busy. Pro usage is charged against the $20/month Pro credit. Rates vary by region. |
| Free plan | homemadeHobby, free: 25 computer-hours a month, 1 computer at a time, nano or tiny size. | Vercel SandboxHobby is free: 5 Active CPU hours, 420 GB-hours of memory, 5,000 creations and 20 GB data transfer per month, 15 GB snapshot storage (lifetime), 10 concurrent sandboxes, up to 4 vCPUs and 8 GB. When the quota is used up, creation pauses until the next cycle. |
Vercel Sandbox prices are list prices in their own units, and plans change, so check their page before you buy. homemade prices are in US dollars without VAT, see pricing.
Moving from Vercel Sandbox
Most projects move in an afternoon.
Vercel sandboxes are created from code. On homemade you create a project from a GitHub repo, then put install commands and services in the project config.
Custom images from their container registry have no direct equivalent. Put the setup in install commands or a template.
Move the secrets your sandboxes use into the homemade project's environment variables.
Exposed ports map to homemade services with a URL enabled. Pick public, organization or owner only for each.
For programmatic use, homemade has an HTTP API, a CLI and an MCP server. It is built around long-lived computers, not millions of short sandbox creations.
When Vercel Sandbox is a good fit
Teams building an app or agent that runs generated code on demand through an SDK.
- If your product runs generated code on demand from the JS or Python SDK, Vercel Sandbox is built for that, with up to 10,000 concurrent sandboxes on Pro.
- If you need many regions, Vercel Sandbox lists 19, including Frankfurt, Paris, London, Tokyo and Sydney.
- If you want Active CPU billing, custom OCI images or root access with FUSE or VPN clients, Vercel Sandbox is a good fit.
homemade fits people and teams who want a persistent cloud computer per project or branch to code in, with AI agents already installed and signed in.
Questions
Is Vercel Sandbox free?
There is a free Hobby allotment: 5 Active CPU hours and 420 GB-hours of memory per month, with 45-minute sessions. When it runs out, creation pauses until the next cycle. Pro bills usage against the $20 monthly credit.
Does Vercel Sandbox keep my files between sessions?
Yes. Sandboxes are persistent by default and the filesystem is snapshotted on stop. Snapshots expire 30 days after last use unless you change it.
How long can a Vercel Sandbox run?
The default timeout is 5 minutes. The maximum session is 45 minutes on Hobby and 24 hours on Pro and Enterprise. Resuming starts a new session.
Is homemade an alternative to Vercel Sandbox?
Partly. For running code in an isolated machine, both work. homemade is a persistent cloud computer per project that you and your agents work in, and it keeps memory while asleep. Vercel Sandbox is an SDK-first backend for running code from your app.
How does Vercel Sandbox pricing compare to homemade?
Vercel charges Active CPU at $0.128/hour plus memory at $0.0212/GB-hour. homemade's small computer (4 vCPU, 8 GB, 30 GB disk) is $0.0324 per hour with disk included, and Pro includes its monthly price as usage.
Try homemade next to Vercel Sandbox
Create a computer for your project and see for yourself. The Hobby plan is free, with 25 hours a month.
More comparisons
Sources
Every Vercel Sandbox fact on this page comes from these pages, read on 20 Nov 2026. Where they did not say, the table says so.