Analysis updated 2026-07-03
Embed HyperKit as the VM engine inside a macOS developer tool that needs to spin up isolated Linux containers or VMs without installing kernel extensions.
Build a macOS-native application that starts lightweight virtual machines programmatically using Apple's built-in hardware virtualization support.
Run lightweight Linux VMs on a Mac as part of a container orchestration tool, using HyperKit as the low-level engine alongside VPNKit for networking.
| moby/hyperkit | stuckatprototype/racer | neomutt/neomutt | |
|---|---|---|---|
| Stars | 3,722 | 3,722 | 3,717 |
| Language | C | C | C |
| Setup difficulty | hard | hard | moderate |
| Complexity | 5/5 | 4/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires macOS 10.10+ on a 2010-or-later Mac with EPT CPU support, optional qcow disk support needs an OCaml environment and several additional libraries.
HyperKit is a low-level toolkit for running virtual machines on a Mac. A virtual machine is a simulated computer that runs inside your real computer, completely isolated from the host system. HyperKit sits at the core of that process, handling the actual hardware virtualization. It is built on top of macOS's built-in Hypervisor.framework, which means it can create and run virtual machines without needing any kernel extensions or special drivers. It works on macOS 10.10 (Yosemite) or later, and only on Macs from 2010 onward whose CPUs support a feature called EPT. HyperKit is derived from xhyve, which itself came from bhyve, a hypervisor originally developed for FreeBSD. The project refines that lineage with a focus on lightweight virtual machines and containers. It is a core part of Docker Desktop for Mac, where it runs the small Linux virtual machine that Docker uses under the hood on macOS. Most Mac users who run Docker are indirectly using HyperKit without knowing it. As a standalone tool, HyperKit is meant to be embedded inside higher-level applications rather than used directly by end users. It is designed to work alongside companion projects such as VPNKit, which handles networking for virtual machines, and DataKit, which manages data access. Developers building tools that need to spin up virtual machines on a Mac can incorporate HyperKit as the underlying engine. Building it from source requires running make in the cloned repository. Optional support for a disk image format called qcow requires installing an OCaml development environment and several additional libraries. The README is brief and focused on technical setup.
A lightweight hypervisor toolkit for macOS that lets developers run virtual machines using Apple's built-in hardware support, designed to be embedded inside tools like Docker Desktop rather than used directly by end users.
Mainly C. The stack also includes C, macOS, Hypervisor.framework.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.