Documentation

Understand Machinaut

Machinaut is the hosted, multi-tenant trust layer for AI agents — the commercial control plane built on Lodestar OSS. These pages explain what it is, how the govern loop runs, and the trust boundary that makes it different.

Machinaut is where your team governs your agent fleet: approve, audit, prove.

Not “see your agent’s chain” — the open-source Lodestar already does that, locally, for a single operator. Machinaut is the hosted control plane on top: the place a team governs many agents across many projects, and can prove — with signatures that hold up outside our cloud — why each governed action ran.

Not observability. Not model-boundary security. Agentic Security.

Concepts

Positioning

What Machinaut is, the category, and the open-core boundary.

Read

How it works

The govern loop: approve, audit, prove — end to end.

Read

Trust boundary

What stays yours, and why a cloud compromise cannot forge approvals.

Read

Reference

Connect your agent

Wire an agent in — the MCP proxy, guard.wrap(), the runtime gate, or a sample.

Read

Self-host

When the OSS viewer is enough, and how to run the control plane yourself.

Read

Ingest contract

session_ship@1 — the NDJSON wire format Machinaut ingests.

Read

Approval relay

The ApprovalChannel HTTP relay — announce, fetch, consume, resolve.

Read

API reference

Every endpoint, grouped and status-labelled.

Read

Glossary

Every term of art, defined once.

Read

Read the status labels

Machinaut v0.3.0 is live: the explorer and platform are shipped; the governance console and the v0.3.0 enterprise surfaces (SSO, SCIM, verified domains, Fleet) are in beta. Where these docs name a capability, they tag it shipped, beta, or planned — and never present a planned or paid-only surface as if it were live. The always-current, per-feature state is the roadmap, and the live console is the source of truth.

New here? Read in order:PositioningHow it worksTrust boundary