What is Kiri?
Kiri runs Docker images in one small Linux VM on macOS and Windows (through WSL 2), or directly on the kernel on Linux, and exposes the Docker Engine API so the docker CLI, Compose and buildx work against a `kiri` context. The VM boots a custom 10 MB kernel whose PID 1 is a Rust agent of under 1 MB that starts containers with a single clone3 call: no runc, shim or dockerd.
Around that sit a native window for containers, images, volumes and networks, single-node Kubernetes through k3s, Linux dev machines, local `.kiri.local` domains with HTTPS from Kiri's own certificate authority, USB pass-through in beta, import from OrbStack and Docker Desktop, and Kiri Share, which publishes a local port on the internet. The repository was created on 2 November 2026; v0.2.2 shipped on 19 November.
Is Kiri worth it?
Kiri attacks the cost Docker Desktop charges for sitting there. On the project's Apple Silicon benchmark, a container starts and exits through the Docker API in 2.55 ms at the median, against 213 ms for Docker Desktop and 380 ms for OrbStack; the daemon idles at about 15 MB while the VM sleeps after 60 s and wakes in about 150 ms. On a 16-core Ubuntu 24.04 machine it starts containers 3.4 times faster than Docker Engine and reads bind mounts 2.9 times faster. These are the maintainer's numbers, with the method and raw results committed and a `kiri bench` command to repeat them.
The same tables are honest about the weak spot. Published ports are relayed in user space, so bulk traffic through one ran at 10.3 Gbit/s against 100.7 Gbit/s for Docker Engine: invisible to a web app, noticeable for large transfers.
The catch: age. The repository is 19 days old, at version 0.2.2, and its 12,018 stars arrived faster than any track record could. Replacing runc with a custom agent means container isolation rests on new code rather than the industry's most audited path; it does apply Docker's default capabilities and seccomp filter. Kiri Share deserves a separate warning: it opens a tunnel to edge.runkiri.com, requires a GitHub-linked Kiri Cloud account, and the docs say a shared address is public with no password or allowlist. The app also updates itself, after checking each release's signature.
Our take: for a Mac or Windows developer whose fans spin up every time Docker Desktop wakes, Kiri is worth a week as a second context, which costs one `docker context use` to reverse.
Where it earns its place
A freelance web developer on a 16 GB MacBook Air
Run a Compose stack all day without the laptop slowing down
Install with Homebrew, run `kiri import` to bring images and volumes over from Docker Desktop, and switch with `docker context use kiri`. The VM sleeps after 60 s idle and gives memory back while running. Free; switching back is one command.
A platform engineer at a 400-person company paying for Docker Desktop seats
Find out whether a free runtime covers the team's local workflows
Trial Kiri on a few machines alongside Docker Desktop, run `kiri bench` on real hardware and check the known issues in docs/features.md. Disable or document Kiri Share before any wider rollout, since its links are public.
Before you commit
- Setup
- `brew install --cask libracoder/kiri/kiri` on macOS 14+, an .msi on Windows 10 or 11 with WSL 2, or a .deb or .rpm on Linux; first launch creates the `kiri` Docker context.
- Integrations
- Docker Engine API, so the docker CLI, Compose, buildx and docker login; k3s as a `kiri` kubectl context; Rosetta for amd64 images on Apple Silicon; import from OrbStack and Docker Desktop.
- Data and privacy
- Containers, Kubernetes and Linux machines need no account. Kiri Share tunnels to edge.runkiri.com and stores its credentials in ~/.kiri/share.json; anyone with a share link can open it. Self-updates check a SHA-256 and signature.
- Limits
- Published-port throughput is lower than Docker Engine's; Windows cannot share by container name; USB pass-through is beta; Kiri Share has monthly transfer and link caps per plan.
What’s good
- Works with the docker CLI, Compose and buildx unchanged
- 2.55 ms container start in the project's Mac benchmark
- VM sleeps when idle; about 15 MB daemon
- Free for work use, unlike Docker Desktop at larger firms
What’s not
- Weeks old; isolation rests on a new custom runtime
- Published ports far slower for bulk traffic
- Kiri Share links are public with no access control
- Kiri Cloud plan prices not published
Best for
Mac and Windows developers who want Docker compatibility without Docker Desktop's idle weight, and can tolerate young software.
Kiri alternatives
Kiri: common questions
- Is Kiri worth it?
- Kiri's benchmarks make Docker Desktop look sluggish, but a three-week-old runtime should earn its place on a laptop before it earns one in CI. We rate it 3.8 out of 5.
- How much does Kiri cost?
- Free and open source (Apache-2.0), including for work use. Kiri Share needs a Kiri Cloud account; plan prices are not published.
- What are the downsides of Kiri?
- Weeks old; isolation rests on a new custom runtime; published ports far slower for bulk traffic; kiri Share links are public with no access control; kiri Cloud plan prices not published.
- Who is Kiri best for?
- Mac and Windows developers who want Docker compatibility without Docker Desktop's idle weight, and can tolerate young software.
- Is Kiri safe for company data?
- Containers, Kubernetes and Linux machines need no account. Kiri Share tunnels to edge.runkiri.com and stores its credentials in ~/.kiri/share.json; anyone with a share link can open it. Self-updates check a SHA-256 and signature.
- What are the best Kiri alternatives?
- The closest alternatives we have reviewed are OpenSandbox and Anthropic Sandbox Runtime (srt).
Answers checked Nov 21, 2026.