SmolVM: Skip the Container, Ship the Entire Machine

Docker solves "it works on my machine" with containers. SmolVM takes a more literal approach: pack your software into a single executable .smolvm file that boots an entire virtual machine in under a second. Real hardware isolation via hypervisor, not container namespaces. Built by a former AWS Firecracker engineer.

How SmolVM Differs From Docker

	Docker	SmolVM
Isolation	Container namespaces (shared kernel)	Full hypervisor VM (separate kernel)
Boot time	Sub-second	Sub-second
Artifact	Container image (layers)	Single `.smolvm` executable
Security boundary	Kernel-level (escapable)	Hardware-level (hypervisor)
Backend (macOS)	Linux VM + containerd	Hypervisor.framework (native)
Backend (Linux)	cgroups + namespaces	KVM via LibKrun

The key distinction: containers share the host kernel and use namespace isolation. SmolVM runs a real VM with its own kernel, giving hardware-grade isolation — the same security boundary AWS Firecracker provides for Lambda.

Why This Matters

Three use cases where the difference between container isolation and VM isolation matters:

Multi-tenant workloads — running untrusted code from different customers needs a hard security boundary, not a namespace
Agent sandboxing — AI agents executing arbitrary code should be VM-isolated, not container-isolated
Compliance environments — some regulatory frameworks require hardware-level isolation, which containers technically don't provide

The Pedigree

Built by a former AWS Firecracker engineer. Firecracker is the microVM technology behind AWS Lambda and Fargate — purpose-built for sub-second boot times with full VM isolation. SmolVM applies the same philosophy to developer-facing packaging.

What's on the Roadmap

Live migration — moving a running SmolVM instance from one host to another without downtime. That's a capability even most container orchestrators handle awkwardly (stateful containers don't migrate cleanly). If SmolVM ships this, it becomes interesting for long-running agent workloads that need to survive host maintenance.

Key Takeaways

SmolVM packs software into a single executable that boots a full VM in under a second
Uses Hypervisor.framework (macOS) or KVM (Linux) for real hardware isolation
Built by a former AWS Firecracker engineer — same philosophy, developer-facing packaging
Not a container replacement for everything — specifically valuable where security isolation matters more than ecosystem compatibility
Live migration on the roadmap

Resources

SmolVM on GitHub — Source and documentation
AWS Firecracker — The microVM technology SmolVM's creator previously worked on
Hypervisor.framework (Apple) — macOS hypervisor API SmolVM uses