What is Jump OS?
Understand the public architecture, its purpose, and its boundaries.
Read the guide →Jump OS knowledge base · Free public blueprint
Jump OS is a public architectural blueprint for organizations building their own governed agent systems. It explains the contracts and boundaries that keep identity, task authority, policy, execution, evidence, verification, rollback, and interruption from collapsing into one opaque automation layer.
Architecture visual
The model matters, but an enterprise system also needs authority, evidence, verification, recovery, and accountable owners around it.
Read the guide →You do not install Jump OS from this site. You use it to think clearly about how your own enterprise agent system should work. The public repository deliberately avoids prescribing one cloud, queue, database, model provider, policy engine, or deployment topology. That is the point: governance contracts should remain explicit even when implementation changes.
The enterprise version is different. Jump OS Enterprise is a customer-specific implementation designed around real systems, authorized workflows, operational evidence, and ongoing maintenance. The current commercial model is a $100,000 implementation with $25,000 annual maintenance, subject to confirmed scope.
Understand the public architecture, its purpose, and its boundaries.
Read the guide →See what the free public material gives you and what a built system requires.
Compare the paths →Learn how a system records identity, authority, evidence, verification, and rollback.
Read the receipt guide →Understand pause, cancel, terminate, quarantine, rollback, and uncertainty.
Read the stop guide →The Jump OS library connects governance principles to the service, workforce, and implementation decisions that follow.
Read the schema, examples, threat model, lifecycle, policy boundaries, and adapter guidance at the source.