Arrakis vs Celesto (SmolVM)
Choose Arrakis for self-hosting a GUI-capable microVM sandbox with snapshot/restore for computer-use and code-execution agents; 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. Arrakis uses Cloud Hypervisor microVM isolation and is open source; Celesto (SmolVM) uses Firecracker / QEMU microVM isolation and is open source.
Key differences between Arrakis and Celesto (SmolVM)
- Isolation: Arrakis uses Cloud Hypervisor microVM; Celesto (SmolVM) uses Firecracker / QEMU microVM.
- Licence: Arrakis is AGPL-3.0; Celesto (SmolVM) is Apache-2.0.
- SDKs and interfaces: Only Arrakis lists REST API. Only Celesto (SmolVM) lists JavaScript/TypeScript.
What they have in common
- Both are open-source projects you run yourself.
- Both use microVM isolation.
- Both are open source.
- Both can be self-hosted.
- Both support snapshots.
- Both list Python, CLI and MCP server.
Arrakis vs Celesto (SmolVM) at a glance
| Attribute | Arrakis | Celesto (SmolVM) |
|---|---|---|
| What it is | Self-hosted microVM sandbox for agent code execution and computer use, with snapshot-and-restore and a VNC-accessible GUI in every VM. | 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 | Open-source project | Open-source project |
| Isolation | MicroVM per sandbox using Cloud Hypervisor as the VMM on Linux/KVM; overlayfs protects each sandbox root filesystem | 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 (AGPL-3.0) | Yes (Apache-2.0) |
| Self-host / BYOC | Yes / No | Yes / Not documented |
| SDKs | Python, REST API, CLI, MCP server | 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 | Snapshot-and-restore "out of the box" so an agent can return to an earlier state; a restored VM currently reuses the original IP, so the original must be stopped or destroyed first on the same host | 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 | Yes / Not documented | Yes / Yes |
| GPU | Not documented | Not documented |
| Networking | Each sandbox gets a tap device on a Linux bridge on the host; SSH access and automatic port forwarding; VNC exposed through port forwarding with a noVNC proxy | 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 to self-host under AGPL-3.0; commercial licensing by email | 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 to self-host | 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 | Not documented | Not documented |
| Good fit for | Self-hosting a GUI-capable microVM sandbox with snapshot/restore for computer-use and code-execution agents | 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 Arrakis
- You want a self-hosted microVM sandbox that includes a desktop for computer-use agents
- You need snapshot/restore so agents can roll back
- You want an MCP server so desktop agent clients can use the sandbox directly
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
- Arrakis: Linux/KVM hosts only; no macOS or Windows support documented
- Arrakis: AGPL-3.0 licence; commercial licensing is by email
- 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 Arrakis profile and Celesto (SmolVM) profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Arrakis or Celesto (SmolVM) better for AI agents?
What is the difference between Arrakis and Celesto (SmolVM)?
Which is open source, Arrakis or Celesto (SmolVM)?
How do Arrakis and Celesto (SmolVM) isolate code?
How does Arrakis pricing compare with Celesto (SmolVM)?
Can you self-host Arrakis or Celesto (SmolVM)?
Do Arrakis 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). Arrakis vs Celesto (SmolVM). agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/arrakis-vs-smolvm/