The archive · Developer & Business Tools · Product decision · 2026
smol machines 2026: shipping a whole Linux VM that boots in under 200ms
YC Spring 2026 startup smol machines boots hardware-isolated Linux microVMs in under 200ms, packable into one .smolmachine file; its Show HN drew 499 points.
smol machines
What the business is
smol machines builds smolvm, an open-source CLI and SDK that boots Linux microVMs with their own guest kernel on macOS, Linux, or Windows with sub-second cold starts, packs stateful machines into single-file .smolmachine artifacts, and runs the same artifact in a hosted cloud.
How it started
BinBin He (HN: binsquare), founder of the YC Spring 2026 startup, started from the 'works on my machine' problem: containers isolate weakly because they share the host kernel, while real VMs take seconds to boot. The project aimed to make hardware virtualization as cheap and portable as a container, and the 2026-04-17 Show HN introduced sub-second cold starts plus .smolmachine artifacts.
What happened
The Show HN drew 499 points and 152 comments, with discussion centered on sandboxing untrusted code, AI agents, and running Docker or Kubernetes inside microVMs. The company joined Y Combinator's Spring 2026 batch, and by mid-2026 shipped a hosted smol cloud so the same SDK and .smolmachine artifact run locally, in the cloud, or self-hosted, along with GPU access (Vulkan) and CUDA API remoting.
How it ended up
Active as of 2026-09-02: open-source runtime on GitHub plus a hosted cloud, positioned for AI coding agents and untrusted-code sandboxing rather than as a drop-in Docker replacement.
Background
smol machines builds smolvm, an open-source runtime that runs each Linux workload in its own hardware-virtualized microVM with a separate guest kernel on Hypervisor.framework (macOS), KVM (Linux), or the Windows Hypervisor Platform. The README advertises sub-second cold starts, elastic memory via virtio balloon, and the ability to pack a stateful machine into a single .smolmachine file that boots anywhere the host architecture matches.
BinBin He started the project from the classic 'works on my machine' gap: containers share the host kernel and isolate weakly, while QEMU-style VMs take tens of seconds to boot. He posted smol machines as a Show HN on 2026-04-17, arguing that a full VM could become as convenient as a container if the hypervisor were a library inside one binary and OCI images booted without a Docker daemon.
The post drew 499 points and 152 comments, with the discussion focusing on sandboxing untrusted code, AI agents, and Docker or Kubernetes workloads inside microVMs. The company joined Y Combinator's Spring 2026 batch, and engineering posts through mid-2026 showed a real k3d/k3s cluster running inside one machine, plus GPU and CUDA-remoting support.
As of 2026-09-02 smol machines is active: the Apache-2.0 runtime is public on GitHub and the same .smolmachine artifact can deploy to a hosted smol cloud or self-hosted infrastructure. The company frames itself for agent sandboxes and automated untrusted-code execution rather than as a general replacement for Docker.
What has to be true
- Containers share the host kernel, so their isolation boundary is weaker than the machine boundary developers already trust.
- Classic VMs were correct but slow to boot, which is why developers tolerated weaker container isolation.
- Booting OCI images with no daemon and packing whole machines into one file made the strong option convenient.
- AI agents and untrusted-code execution created a moment where hardware isolation was newly in demand.
- A portable full VM also solved environment drift, not just security, giving developers two reasons to switch.
What can be applied
Making the strongest isolation cheap - a sub-200ms full VM - turns 'works on my machine' and 'untrusted code' into product wedges instead of hard constraints.
Aftermath
As of 2026-09-02 smol machines is an active YC Spring 2026 company: smolvm is Apache-2.0 on GitHub, with a hosted smol cloud and self-hosted deployment of the same .smolmachine artifacts. Engineering posts show workloads containers struggle with - a real Kubernetes cluster and GPU-accelerated rendering inside one machine - and the project targets AI coding agents and automated sandboxing. Limitations are documented openly (Windows lacks GPU support and pack creation), and the security claim is bounded: hypervisor isolation per workload, not a hardened multi-tenant control plane.
Sources
- smolvm - portable, lightweight, self-contained virtual machine
- Show HN: Smol machines - subsecond coldstart, portable virtual machines
- smol machines - Ship software faster with portable, self contained virtual machines
- Running a real Kubernetes cluster inside one microVM
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card