# homemade vs microsandbox

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 microsandbox.

Checked 20 Nov 20264 sources

[Start free](/login?signup=1)[See pricing](/pricing)

## Why people pick homemade over microsandbox

What you get with homemade that microsandbox does not give you in the same way.

- homemade is a finished hosted product today. Microsandbox Cloud is in private beta with a waitlist, and the runtime is beta software with breaking changes expected.
- Import a GitHub repo and get a computer with the repo cloned, install commands run and services started in terminals. microsandbox is a runtime you build that into.
- Claude Code, Codex, OpenCode, pi, Kimi and Grok are installed and signed in on every computer, so you sign in once. microsandbox does not state that it preinstalls agent CLIs.
- Computers sleep when idle and keep disk, memory and running terminals, and wake where you left off. Sleeping is free.
- A dashboard with a Chat tab, preview links with sharing levels, and SSH or VS Code and Cursor over SSH (`homemade open`).
- Hobby is a free plan that renews every month. The microsandbox cloud trial is a one-time $10 credit.

## Side by side

The parts that matter when you build with coding agents. microsandbox facts are from their own pages, checked 20 Nov 2026.

| Feature         | homemade                                                                                                                                                                                                                                                                                    | microsandbox                                                                                                                                                                                                                                                                                                                                |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Coding agents   | homemade Claude 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).                                                                                            | microsandbox An MCP server lets MCP-compatible agents (their homepage names Claude and Codex) create sandboxes, run commands and use files. Not stated on their site: agent CLIs preinstalled in a managed workspace.                                                                                                                       |
| What you get    | homemade A full VM per computer with its own kernel, its own private network and its own firewall. Not a shared container.                                                                                                                                                                  | microsandbox Hardware-isolated microVMs, each with its own kernel, booted from the image you choose. The sandbox works with a placeholder and the real secret is substituted on the host for allowed destinations. Outbound network access can be limited to an allow list or turned off.                                                   |
| Sleep and state | homemade Computers 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.                                                                    | microsandbox Live sandboxes can be forked, and running sandbox state can be saved and restored. Snapshots of a stopped sandbox capture its disk. Cloud paid plans allow persistent sandboxes. Trial sandboxes are ephemeral with 1-hour sessions.                                                                                           |
| Preview links   | homemade A 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.                                                                                                         | microsandbox Cloud plans list services per sandbox (20 per sandbox). URL format and auth options: Not stated on their site.                                                                                                                                                                                                                 |
| Editors and SSH | homemade Browser terminal and editor, SSH (homemade ssh), VS Code and Cursor over SSH (homemade open), a CLI for macOS and Linux, and an HTTP API.                                                                                                                                          | microsandbox SDKs for Rust, TypeScript, Python, Go and Ruby, and a CLI. SSH and IDE support: Not stated on their site.                                                                                                                                                                                                                      |
| Teams           | homemade Teams with projects and members, sharing levels on previews, GitHub pushes as you, PR preview computers and Linear ticket computers.                                                                                                                                               | microsandbox Teams plan at $200/month. Enterprise offers committed usage and bring your own cloud. SSO and roles: Not stated on their site.                                                                                                                                                                                                 |
| Pricing         | homemade Pro $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. | microsandbox Cloud (private beta pricing, waitlist): Builder $20/month and Teams $200/month, each paid as usage credit. Standard CPU $0.048 per vCPU-hour, shared CPU $0.007, memory $0.003 per GiB-hour (standard), root disk $0.0000625 per GiB-hour, volumes $0.15 per GiB-month, snapshots $0.08 per GiB-month. Local use has no price. |
| Free plan       | homemade Hobby, free: 25 computer-hours a month, 1 computer at a time, nano or tiny size.                                                                                                                                                                                                   | microsandbox The open source runtime is free to run locally. Cloud free trial is a one-time $10 credit: 1 sandbox at a time, up to 2 vCPU / 1 GiB, 1-hour sessions.                                                                                                                                                                         |

microsandbox 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](/pricing).

## Moving from microsandbox

Most projects move in an afternoon.

1. microsandbox sandboxes are defined in SDK code and OCI images. On homemade, put the repo, install commands and services in the project config.

2. Local microVMs and BYOC have no homemade equivalent. homemade runs on its hosted platform.

3. Move your secrets into the homemade project's environment variables. microsandbox's host-side secret substitution has no equivalent feature.

4. Snapshots and volumes do not transfer. Rebuild from install commands, then fork running computers.

5. Replace services exposed in microsandbox cloud with homemade services that have a URL enabled.

## When microsandbox is a good fit

Developers embedding sandboxes in their own product, or who need local, self-hosted or bring-your-own-cloud isolation.

- If you embed sandboxes in your own product, microsandbox has SDKs in Rust, TypeScript, Python, Go and Ruby, with the same sandbox locally and in the cloud.
- If you want an Apache-2.0 runtime on your own Mac, Linux or Windows machine with no account, microsandbox fits.
- If you need bring-your-own-cloud, or placeholder secrets that are swapped for real values on the host plus outbound allow lists, microsandbox is designed for that.

homemade fits developers who want a ready cloud computer per project or branch with repo import, previews and agents.

## Questions

### Is microsandbox free and open source?

Yes, the runtime is Apache-2.0 on GitHub and free to run locally. The cloud is a separate paid service in private beta.

### How much does Microsandbox Cloud cost?

Builder is $20/month and Teams is $200/month, paid as usage credit. Standard CPU is $0.048 per vCPU-hour. Pricing is labelled private beta.

### Does microsandbox run locally?

Yes. It needs no daemon, root or account. It runs on macOS with Apple Silicon, Linux with KVM and Windows with WHP.

### Is homemade an alternative to microsandbox?

Yes, if you want a hosted cloud computer per project with repo import and previews. If you want a library to embed or to self-host, microsandbox fits better.

### What does the Microsandbox Cloud free trial include?

A one-time $10 credit, 1 running sandbox, up to 2 vCPU / 1 GiB and 1-hour ephemeral sessions.

## Try homemade next to microsandbox

Create a computer for your project and see for yourself. The Hobby plan is free, with 25 hours a month.

[Start free](/login?signup=1)[See pricing](/pricing)

## More comparisons

- [homemade vs CodeSandbox Sandbox for AI agents](/compare/homemade-vs-codesandbox)
- [homemade vs Vercel Sandbox Sandbox for AI agents](/compare/homemade-vs-vercel-sandbox)
- [homemade vs E2B Sandbox for AI agents](/compare/homemade-vs-e2b)
- [homemade vs Modal Sandboxes Sandbox for AI agents](/compare/homemade-vs-modal)
- [All comparisons Every product we compared](/compare)

## Sources

Every microsandbox fact on this page comes from these pages, read on 20 Nov 2026. Where they did not say, the table says so.

- [Homepage](https://microsandbox.dev)
- [Pricing](https://microsandbox.dev/pricing)
- [GitHub repository](https://github.com/microsandbox/microsandbox)
- [Docs](https://docs.microsandbox.dev)

Make yourself at home.

## Product

- [Pricing](/pricing)
- [Integrations](/integrations)
- [CLI](/cli)
- [MCP](/mcp)
- [API](/api)

## Use cases

- [Claude Code in the cloud](/claude-code-in-the-cloud)
- [Codex in the cloud](/codex-in-the-cloud)
- [AI agent sandbox](/ai-agent-sandbox)
- [Cloud dev environment](/cloud-dev-environment)
- [Preview environments](/preview-environments)

## Compare

- [All comparisons](/compare)

## Resources

- [Docs](https://docs.homemade.dev)
- [Blog](/blog)
- [llms.txt](https://docs.homemade.dev/llms.txt)

## Company

- [Contact](mailto:hello@homemade.dev)
- [GitHub](https://github.com/usehomemade/homemade)

## Legal

- [Impressum](/impressum)
- [Terms](/terms)
- [Privacy](/privacy)

© 2026 homemade.dev

---

Canonical: https://www.homemade.dev/compare/homemade-vs-microsandbox
More pages: https://www.homemade.dev/llms.txt
