the operating system
for AI agents
no ssh. no shell. no attack surface.
just agents.
your agents run on an OS built for humans.
ssh exists. a shell exists. an attack surface exists.
every layer you don't need is a layer that can break.
00 — WHAT WE REMOVED
every traditional OS ships with layers built for human operators. NullBox strips all of them. what's left is only what agents need.
01 — ARCHITECTURE
16 layers from bare metal to skill registry. click any layer to see how it works.
02 — HOW IT WORKS
four steps from bare metal to a running, sandboxed AI agent.
Write NullBox to a USB drive or SD card. Boot it. The entire OS is a ~100MB read-only image — no installer, no setup wizard, no configuration. It just runs.
$ dd if=nullbox.img of=/dev/sdX bs=4M
Define your agent in a single AGENT.toml file. What APIs it can call, what files it can read, how much memory it gets. If it's not declared, it doesn't exist.
network.allow = ["api.openai.com"]
Each agent boots inside its own microVM with a dedicated kernel and filesystem. One compromised agent can't touch another — hardware-enforced, not just namespaces.
agent → microVM → own kernel → own rootfs
Everything is default-deny. Network, filesystem, shell access — all blocked unless explicitly allowed in AGENT.toml. The OS enforces the rules, not the agent.
deny * → allow only what's declared
03 — CAPABILITY MANIFEST
[agent] name = "researcher" version = "1.2.0" [capabilities] network.allow = ["api.openai.com", "api.exa.ai"] # default deny filesystem.read = ["/data/research"] filesystem.write = ["/data/research/output"] shell = false max_memory_mb = 512 [tools] read_files = { risk = "low" } delete_files = { risk = "critical" } # human approval required
04 — TARGET HARDWARE
nothing unnecessary.
everything enforced.
open source — MIT / Apache-2.0