Skip to content

Jump OS knowledge base · Free public blueprint

Build enterprise agents you can govern, inspect, and explain.

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.

Created and published by Christopher Amaya through Jumpstart Scaling. Free to read. No login required.

Abstract AI model engine visual for enterprise control-plane architecture
Jump OS public blueprint visual · Jumpstart Scaling / Christopher Amaya

Architecture visual

The engine is only one layer

The model matters, but an enterprise system also needs authority, evidence, verification, recovery, and accountable owners around it.

Read the guide →
Start here

This is a blueprint, not a download.

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.

Public source: the repository contains architecture, contracts, examples, and research guidance. It does not disclose Jumpstart Scaling's private enterprise implementation.
Knowledge base

Learn the control-plane questions before choosing tools.

What is Jump OS?

Understand the public architecture, its purpose, and its boundaries.

Read the guide →

Blueprint vs enterprise implementation

See what the free public material gives you and what a built system requires.

Compare the paths →

Durable execution receipts

Learn how a system records identity, authority, evidence, verification, and rollback.

Read the receipt guide →

Use the canonical source

Read the schema, examples, threat model, lifecycle, policy boundaries, and adapter guidance at the source.