
runtimeClassName: k7, the ~5 ms MAP_PRIVATE fork) or a stock, sha-pinned Firecracker under the stock jailer (runtimeClassName: k7-fc) when the VMM must sit outside the daemon’s address space — same guest, agent, fork/tree/pool verbs and in-guest Docker service. See Backends.
For sandboxes at scale with a CLI / API / Python SDK, see K7.
Installation
scripts/quickstart.sh — doctor-check the host, fetch the release, boot a 3-node tree, fork 4 branches. Five minutes.CoW fork
How a 5 ms VM fork works: shared memory until write, dirty pages, reflink keyframes, byte-identical copies.
Cluster mode
Create or adopt an N-node k3s cluster and fork it without agent restarts.
Ubuntu nodes
Stock Ubuntu 24.04 guests: k3s, Cilium, Tetragon, Longhorn, ML operators on mock GPUs — all forked live.
Time warp
Lockstep clock jumps and ×N dilation: delete idle wall time without touching what the guest computes.
GRPO / tree search
Wire k7d into a trainer or an MCP agent: fork_batch, protect, prune, auto_evict under RAM budgets.
Daemon API
JSON-lines protocol on /run/k7d/k7d.sock — every VM, tree, and clock verb.
Benchmarks
Hardware, exact commands, and every enforced latency budget — both clocks.
Backends
Native rust-vmm or stock Firecracker under the jailer (
k7-fc): selection rules, feature matrix, fork mechanics.Security model
One daemon, many VMs; the tree jailer (nft, cgroup, seccomp), guest-controlled path rules, the Firecracker profile, Docker as a guest service.
Formal verification
Kani on unsafe paths; Aeneas→Lean on the tree budget model.
Watch it
- A frontier agent with a fork button — an MCP agent forks a live Ubuntu Cilium+Tetragon cluster three ways to peel a planted incident. How the demo works.
- The same incident seen from the tree —
examples/k7view/, a read-only SSE dashboard on the snapshot tree. - A ×8 dilated fork tree recorded in real time — guests run at
dilation: 8; fork latency chips are wall-clock.
