Agent Sandboxesagentsandboxes.org
Head-to-head

Arrakis vs Celesto (SmolVM)

Answer in brief

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.

By the Agent Sandboxes editors · Updated

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

AttributeArrakisCelesto (SmolVM)
What it isSelf-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.
TypeOpen-source projectOpen-source project
IsolationMicroVM per sandbox using Cloud Hypervisor as the VMM on Linux/KVM; overlayfs protects each sandbox root filesystemMicroVM 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 sourceYes (AGPL-3.0)Yes (Apache-2.0)
Self-host / BYOCYes / NoYes / Not documented
SDKsPython, REST API, CLI, MCP serverPython, JavaScript/TypeScript, CLI, MCP server
Cold start (vendor claim)Not documentedREADME: a local computer "starts in about 500 ms"; the website says hosted agent sandboxes "start in under 2 seconds"
Max sessionNot documentedNot documented
PersistenceSnapshot-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 hostSnapshots "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 / pauseYes / Not documentedYes / Yes
GPUNot documentedNot documented
NetworkingEach 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 proxyRestricted-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
PricingFree to self-host under AGPL-3.0; commercial licensing by emailCloud 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 tierFree to self-hostOne-time $5 Micro runtime credit, no card, expires 30 days after activation (two retained Micro sandboxes); free to self-host
ComplianceNot documentedNot documented
RegionsNot documentedNot documented
Company headquartersNot documentedNot documented
Good fit forSelf-hosting a GUI-capable microVM sandbox with snapshot/restore for computer-use and code-execution agentsRunning 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?
Neither is better for every workload. Arrakis suits self-hosting a GUI-capable microVM sandbox with snapshot/restore for computer-use and code-execution agents. Celesto (SmolVM) suits running agent computers as microVMs on your own Linux or Apple Silicon machine, with the same API available as a hosted cloud computer.
What is the difference between Arrakis and Celesto (SmolVM)?
Arrakis uses Cloud Hypervisor microVM; Celesto (SmolVM) uses Firecracker / QEMU microVM. Arrakis is licensed AGPL-3.0; Celesto (SmolVM) is licensed Apache-2.0. Only Arrakis lists REST API. Only Celesto (SmolVM) lists JavaScript/TypeScript.
Which is open source, Arrakis or Celesto (SmolVM)?
Both are open source (Arrakis: AGPL-3.0; Celesto (SmolVM): Apache-2.0).
How do Arrakis and Celesto (SmolVM) isolate code?
Arrakis: MicroVM per sandbox using Cloud Hypervisor as the VMM on Linux/KVM; overlayfs protects each sandbox root filesystem. Celesto (SmolVM): 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.
How does Arrakis pricing compare with Celesto (SmolVM)?
Arrakis: Free to self-host under AGPL-3.0; commercial licensing by email. Celesto (SmolVM): 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. Rates change, so check the Arrakis and Celesto (SmolVM) pricing pages before deciding.
Can you self-host Arrakis or Celesto (SmolVM)?
Yes, both can be self-hosted.
Do Arrakis and Celesto (SmolVM) support snapshots or pause and resume?
Arrakis: snapshots yes, pause and resume not documented. Celesto (SmolVM): snapshots yes, pause and resume yes.

Sources

  1. github.com/abshkbh/arrakis
  2. github.com/abshkbh/arrakis/releases
  3. celesto.ai
  4. celesto.ai/docs/
  5. celesto.ai/docs/cloud/overview.md
  6. celesto.ai/pricing

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/