compare
reviewed
for agent-generated or user-supplied code, microsandbox adds a separate guest kernel per sandbox. Docker Engine runs ordinary containers against a shared kernel and supplies a broad image-building and deployment ecosystem. [1][24]
you can keep using OCI images with microsandbox. the runtime adds local SDKs, host-side credential handling, network policy, and disk or full-memory checkpoints. [21][25][28][29]
this page compares ordinary Docker Engine containers. Docker Sandboxes is a separate microVM product with different pricing and licensing. [4]
01
namespaces and cgroups isolate and limit ordinary Docker containers, but those containers still use the same kernel. Docker Desktop’s Linux VM separates Linux from the desktop host; it does not give each ordinary container its own kernel. [1][7] microsandbox gives each sandbox a guest kernel from the start. [24]
custom container runtimes can change Docker’s isolation model. compare those separately rather than treating every Docker deployment as identical.
02
Docker Engine’s open-source components remain free. Docker Desktop requires a subscription for commercial use outside its free eligibility limits. Docker Sandboxes has a free local tier and a proprietary runtime. [2][3][4][8] microsandbox’s local runtime is Apache-2.0 and does not require a commercial-use subscription. its hosted cloud is priced separately. [26][27]
common questions
Docker Engine / Moby is Apache-2.0. Docker Desktop has separate subscription terms. Docker Sandboxes is a different, proprietary product with free local use. [2][3][4][8]
yes. it runs OCI images from standard registries without a Docker daemon. image compatibility does not make it a drop-in Docker Engine or Compose replacement. [25]
yes. Docker documents an experimental checkpoint/restore feature using CRIU. [5] microsandbox provides disk snapshots and full local VM checkpoints through its CLI and SDKs. [21]
primary sources
put the boundary on your own machine before you choose anything else.
run it locally