arcbox builds a from-scratch Rust VMM for local agent sandboxes

arcbox gives each AI agent its own microVM instead of a container namespace. The project, licensed Apache-2.0, pitches itself as an OCI-compatible local alternative to Docker Desktop and OrbStack on macOS, and claims boot times under 100 milliseconds.

That speed claim matters because it's the whole argument for using a VM instead of a container. Containers share a kernel with the host, which is fast to start but means one agent process can see and touch more of the system than you'd want when you're running code you didn't write. A microVM gives each agent its own kernel and its own network path, closer to real isolation, and arcbox's bet is that it can make that isolation boot fast enough to feel like a container anyway.

To get there, arcbox didn't wrap an existing hypervisor. It wrote its own VMM, VirtIO devices, filesystem sharing and network datapath in Rust, from scratch. That's a bigger commitment than most local dev tools make. A VMM is low-level systems code: get the VirtIO block or network device wrong and you get silent corruption or a hung guest, not a stack trace pointing at the bug.

The release history is uneven. Three releases went out on August 14, then v0.7.0 on August 15, then nothing since. For a project this young, with this much custom low-level code, a quiet stretch after a burst of releases doesn't tell you whether development slowed down or the team just moved to a bigger internal milestone. If you're evaluating this for anything beyond a laptop experiment, the open question is whether a solo-maintained VMM gets the same scrutiny a shared-kernel container runtime already has from years of production use.