back to microsandbox

compare

microsandbox vs modal

reviewed

microsandbox gives every sandbox a guest kernel and runs on your own devices. Modal is a managed compute platform with GPU support, standard gVisor sandboxes, and a separate beta VM option. [1][2][24][26]

choose microsandbox when the runtime needs to live inside your application: local execution, full checkpoints, and device policy are built in. cloud is also available by request during private beta. [20][21][22]

Modal’s VM option now handles workloads that need a full Linux kernel. those VMs are CPU-only; GPU support belongs to its other compute offerings. [2]

microsandbox
local + cloud
modal
managed cloud compute
runtime ownership
apache 2.0 runtime and SDKs [26]
managed service; client libraries do not provide a local runtime [1]
isolation
microVM and separate guest kernel [24]
standard gVisor · beta full-Linux VM option [1][2]
local execution
macOS · Linux · Windows [26]
clients run locally; sandbox execution is hosted [1]
offline execution
runs offline after provisioning dependencies and images [23]
requires the managed service [1]
SDKs
rust · typescript · python · go · ruby · CLI [25][26]
python · javascript/typescript · go [1]
snapshots
local snapshots save disk state, or disk, memory, and running processes with --full. cloud currently supports disk snapshots from stopped persistent sandboxes and disk restore. [21]
filesystem snapshots; alpha memory snapshots expire after seven days [3]
memory capture
local running source resumes after capture [21]
memory capture terminates source; VM memory access is limited [2][3]
GPU
CPU sandboxes
GPU compute available; beta VM sandboxes are CPU-only [1][2]
pricing
free local runtime · cloud free tier and paid plans [27]
Starter: $0 base + usage, with $30 monthly compute credit [4]
pick microsandbox

choose microsandbox when

  • you need execution on employee laptops or disconnected machines. [22][23]
  • you want local memory checkpoints that leave the source running after capture. [21]
  • you need an Apache-2.0 runtime, not only an API client. [26]
pick modal

choose modal when

  • you need managed GPU resources or batch compute. [1]
  • you want hosted capacity and your workload fits Modal’s sandbox limits. [1][2]

01

check what happens to the running sandbox

Modal’s alpha memory snapshots terminate the source and expire after seven days. memory snapshots for its beta VM sandboxes require access to be enabled. [2][3] microsandbox’s local full capture briefly pauses a running source, then resumes it. restore creates a new sandbox and can share unchanged memory pages between children. [21]

microsandbox cloud currently offers disk snapshots from stopped persistent sandboxes. local memory support should not be read as cloud feature parity. [20][21]

snapshot behavior

02

keep execution where the work is

microsandbox can run next to a local repository and use administrator settings distributed with Jamf or Intune. provision dependencies and images before going offline. [22][23] Modal’s local SDK connects to remote compute. [1]

managed device deploymentcloud pricing

common questions

does Modal use gVisor or VMs?

both. standard sandboxes use gVisor; beta VM sandboxes run a full Linux kernel. the VM option currently has no GPU support. [1][2]

can Modal sandboxes run locally?

the clients can, but the sandboxes run on Modal’s service. microsandbox runs the microVM itself on macOS, Linux, or Windows. [1][26]

are memory snapshots available on both?

microsandbox supports full snapshots locally. Modal documents alpha memory snapshots with a seven-day lifetime and source termination; its VM memory support is access-limited. [2][3][21]

primary sources

  1. [1] Modal sandbox clients and managed compute · last verified 2026-09-26
  2. [2] beta VM sandbox capabilities and restrictions · last verified 2026-09-26
  3. [3] filesystem and alpha memory snapshot behavior · last verified 2026-09-26
  4. [4] Modal plan and compute pricing · last verified 2026-09-26
  5. [20] microsandbox cloud availability and backend compatibility · last verified 2026-09-26
  6. [21] microsandbox disk snapshots, full checkpoints, and local branching · last verified 2026-09-26
  7. [22] microsandbox managed deployment with Jamf and Intune · last verified 2026-09-26
  8. [23] microsandbox offline provisioning of runtime dependencies and images · last verified 2026-09-26
  9. [24] microsandbox microVM isolation · last verified 2026-09-26
  10. [25] microsandbox runtime, CLI, images, and language SDKs · last verified 2026-09-26
  11. [26] microsandbox source, Apache-2.0 license, and supported host platforms · last verified 2026-09-26
  12. [27] microsandbox cloud plans and usage pricing · last verified 2026-09-26

run it locally.

put the boundary on your own machine before you choose anything else.

run it locally