agents-sandbox vs Celesto (SmolVM)
Choose agents-sandbox for developers who want each coding agent confined to a per-project microVM on their own Linux or Apple Silicon machine; choose Celesto (SmolVM) for running agent computers as microVMs on your own Linux or Apple Silicon machine, with the same API available as a hosted cloud computer. agents-sandbox uses microsandbox microVM isolation and is open source; Celesto (SmolVM) uses Firecracker / QEMU microVM isolation and is open source.
Key differences between agents-sandbox and Celesto (SmolVM)
- Type: agents-sandbox is a tool that runs on your own machine; Celesto (SmolVM) is an open-source project you run yourself.
- Isolation: agents-sandbox uses microsandbox microVM; Celesto (SmolVM) uses Firecracker / QEMU microVM.
- Licence: agents-sandbox is GPL-3.0; Celesto (SmolVM) is Apache-2.0.
- Self-hosting: Celesto (SmolVM) documents a self-hosted option; agents-sandbox does not.
- SDKs and interfaces: Only Celesto (SmolVM) lists Python, JavaScript/TypeScript and MCP server.
What they have in common
- Both use microVM isolation.
- Both are open source.
- Both list CLI.
agents-sandbox vs Celesto (SmolVM) at a glance
| Attribute | agents-sandbox | Celesto (SmolVM) |
|---|---|---|
| What it is | GPL-3.0 launcher that gives each project and coding agent its own microsandbox microVM on Linux/KVM or Apple Silicon macOS, with secrets kept on the host. | Open-source microVM "computers" for agents from Celesto AI, formerly published as SmolVM, with Firecracker on Linux and QEMU on macOS, plus a hosted cloud option. |
| Type | Local / OS-level | Open-source project |
| Isolation | Dedicated microsandbox microVM per project and agent with a "separate microVM and Linux kernel"; the README does not name the hypervisor | MicroVM per computer with hardware-level separation from the host: Firecracker on Linux (KVM), QEMU on macOS; the PyPI listing also names libkrun as a backend |
| Open source | Yes (GPL-3.0) | Yes (Apache-2.0) |
| Self-host / BYOC | No / No | Yes / Not documented |
| SDKs | CLI | Python, JavaScript/TypeScript, CLI, MCP server |
| Cold start (vendor claim) | Not documented | README: a local computer "starts in about 500 ms"; the website says hosted agent sandboxes "start in under 2 seconds" |
| Max session | Not documented | Not documented |
| Persistence | VM is built or reused per project; agent state persists in a /home/dev volume; the project directory is mounted read-write at /workspace, or an isolated VM-internal worktree for some agents | Snapshots "pause and restore memory, disk, and active processes"; persistent state survives across sessions; in the cloud, stopped computers keep files, packages and workspace state, and stopped root disks are kept free for 30 days |
| Snapshots / pause | Not documented / Not documented | Yes / Yes |
| GPU | Not documented | Not documented |
| Networking | Egress profiles: public (default), private and host extend it, none is allowlist-only "deny-by-default egress, not a complete air gap"; links can open in the host browser for allowlisted schemes | Restricted-destination network controls are documented for Linux only (Firecracker, or QEMU with TAP); QEMU slirp supports open and off modes on macOS and Linux; the QEMU backend uses user-mode (slirp) networking with port forwarding; cloud computers can expose public ports |
| Pricing | Free (GPL-3.0) | Cloud computers billed per hour of running time, prepaid with no monthly fee: Micro 1 vCPU/2 GB $0.015/h, Small 1 vCPU/4 GB $0.020/h, Standard 2 vCPU/4 GB $0.030/h, Memory 2 vCPU/8 GB $0.040/h, Large 4 vCPU/16 GB $0.080/h, XL 8 vCPU/32 GB $0.160/h; root disk included; paid accounts start with a default limit of 20 running sandboxes. Local runtime is free |
| Free tier | Free | One-time $5 Micro runtime credit, no card, expires 30 days after activation (two retained Micro sandboxes); free to self-host |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | Hamburg, Germany | Not documented |
| Good fit for | Developers who want each coding agent confined to a per-project microVM on their own Linux or Apple Silicon machine | Running agent computers as microVMs on your own Linux or Apple Silicon machine, with the same API available as a hosted cloud computer |
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 agents-sandbox
- You want one microVM per project rather than one shared sandbox
- You need secrets kept off the guest while the agent still works
- You want configurable egress without a full air gap
Reasons to choose Celesto (SmolVM)
- You want a microVM runtime that works on an Apple Silicon laptop (QEMU) and on Linux (Firecracker) behind one API
- You need snapshots that capture memory and running processes, not just a disk image
- You want a cheap hosted fallback with the same SDK when a local machine is not available
- You are building computer-use agents and want a browser or desktop inside the VM
Trade-offs to check first
- agents-sandbox: Five of the seven agent profiles are marked experimental
- agents-sandbox: Hypervisor and boot behaviour are inherited from microsandbox and not documented here
- Celesto (SmolVM): Alpha-labelled on PyPI; renamed from SmolVM to Celesto, with the smolvm command and Python import removed
- Celesto (SmolVM): Restricted-destination network controls are Linux only; QEMU on macOS supports only open and off modes
Both are worth piloting with your own image and region. See the full agents-sandbox profile and Celesto (SmolVM) profile, or the complete comparison.
More comparisons
Frequently asked questions
Is agents-sandbox or Celesto (SmolVM) better for AI agents?
What is the difference between agents-sandbox and Celesto (SmolVM)?
Which is open source, agents-sandbox or Celesto (SmolVM)?
How do agents-sandbox and Celesto (SmolVM) isolate code?
How does agents-sandbox pricing compare with Celesto (SmolVM)?
Can you self-host agents-sandbox or Celesto (SmolVM)?
Do agents-sandbox and Celesto (SmolVM) support snapshots or pause and resume?
Sources
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). agents-sandbox vs Celesto (SmolVM). agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/agents-sandbox-vs-smolvm/