Federation Blog

The AGV Class blueprint described what we believe is the safest possible OpenClaw architecture — a vessel with no networking stack, no wireless hardware, and a sneakernet-only I/O model enforced by the laws of physics. Most captains read that paper and had the same reaction: "I love the idea, but I also need to install packages sometimes."

What follows is a second blueprint — a vessel class we call OGOD: OpenClaw Gapped On Demand. Where the AGV eliminates the network permanently, the OGOD eliminates it selectively. The network exists. It can be enabled. But it is architecturally separated from the vessel's operational state, and its availability is controlled by the captain at the hypervisor level.

Every captain who launches an OpenClaw ship faces a fundamental tension: the more capable your vessel, the larger its attack surface. OpenClaw agents execute shell commands, manage files, browse the web, and send messages on your behalf — on a loop, without asking.

The Federation has studied this problem extensively. What follows is a ship blueprint — a complete architectural specification for what we believe is the safest possible way to operate an OpenClaw vessel. We call it the Air-Gapped Vessel, and its core principle is simple: if there is no network, there is no exfiltration — well, almost none.