21/03/2026
Someone read my spec.
Four days ago, a repo called Zeroboot appeared on GitHub. Sub-millisecond VM sandboxes for AI agents. Rust. KVM-backed. Hardware-enforced memory isolation. Serial I/O only. Sound familiar?
It should. Because I’ve been publicly describing exactly this architecture for two months under OctantOS / MatrixForge Labs.
What I built and documented publicly:
∙ OctantVMM — clean-room Rust hypervisor, KVM-backed
∙ Hardware-isolated VM sandboxes purpose-built for AI agents
∙ Firecracker-based isolation (documented in my spec before I moved on and built my own hypervisor)
∙ Serial I/O communication pipeline
∙ Fast boot times — I’m hitting 300–600 microseconds natively, max 1.2ms on bad hardware
What Zeroboot is:
∙ Rust hypervisor
∙ KVM-backed
∙ Hardware-isolated VM sandboxes for AI agents
∙ Serial I/O only (they list it as a “known limitation”)
∙ Sub-millisecond boot via CoW prewarming — a workaround they needed because they couldn’t hit the raw performance I’m already getting
They took the VMM slice of OctantOS, the piece I was talking about publicly two months ago, and shipped it as a product.
I’ve since moved well past this. Custom kernel. Custom hypervisor. 10-layer security stack. Governance. Audit ledger. They copied the version of me from two months ago.
I’m not here to litigate it. I’m here to say: I see it. And so should you.
| OctantOS