Skip to content- Sources: primary
- Summary: hyperlight-unikraft runs a Unikraft unikernel inside a Hyperlight micro-VM, so unmodified binaries for Python, Node.js, .NET, Java, PHP, Go, Rust, C, Bash and PowerShell run on x86_64 and arm64 with no SDK or recompile. It snapshots a warmed runtime: a script importing numpy, pandas and scikit-learn took 45 ms from snapshot against 1,119 ms natively, while a Python hello world was slower at 22 ms against 17 ms. Integrations include urunc for containerd and Kubernetes, an MCP server with a stateful run_python tool, smolagents, an OpenAI Agents SDK sandbox provider, ClickHouse Python UDFs and verl reward execution.
- Why it matters: Teams sandboxing agent-generated code get a hypervisor boundary with startup costs near or below native for heavy runtimes, deny-by-default mounts and network, and a containerd path into Kubernetes.
- Background: Hyperlight is a CNCF Sandbox project. Unlike QEMU or Firecracker, which run as separate processes, it is a library virtual machine monitor that an application links in, using KVM or MSHV on Linux, WHP on Windows and Hypervisor.framework on macOS. A unikernel is a single-application operating system with one address space and only the kernel components that application needs. The digest covered a Firecracker microVM escape on 2026-11-07, a reminder that the hypervisor boundary narrows risk but does not remove it.