compare
reviewed
microsandbox runs the microVM on your machine and embeds in your application. Cloudflare Sandboxes connects managed VM-isolated containers to Workers and Durable Objects. [1][2][24][26]
both provide a separate guest kernel in production. local development differs: Cloudflare uses a Docker-compatible engine with Wrangler; microsandbox runs its own microVM runtime on macOS, Linux, and Windows. [1][3][26]
microsandbox includes full local checkpoints and managed settings for employee devices. its hosted cloud is available by request during private beta. [20][21][22]
01
Cloudflare’s local toolchain runs containers through Docker. its production service puts each sandbox in its own VM. [1][3] microsandbox runs the microVM locally, so developers can exercise that boundary without deploying a Worker. [26]
02
Cloudflare’s documented backup flow archives a directory to R2 and restores that tree later. it is not a memory checkpoint. [4] microsandbox’s local full snapshots preserve disk, memory, and running processes; its cloud snapshots currently preserve disk only. [21]
Cloudflare’s SDK is open source, but its hosted compute is billed through the platform. microsandbox’s runtime is also open source and runs on your own hardware without a service subscription. [5][6][26]
common questions
yes. each production sandbox container runs in its own VM. [1] local development instead uses Wrangler and a Docker-compatible engine. [3]
production use requires Workers Paid. Containers, Workers, and Durable Objects contribute usage charges; consult the pricing page for allowances and rates. [2][5]
the Sandbox SDK is Apache-2.0. that is distinct from the managed Containers platform it calls. microsandbox publishes the locally executable runtime as well as its SDKs. [2][6][26]
primary sources
put the boundary on your own machine before you choose anything else.
run it locally