OpsChain documentation

Overview

What OpsChain is, what you can do with it, and where to start.

The hands-on learning path — numbered runbooks from a fresh install to an estate that runs itself.

Operator guides per feature family, with the governance and integration guides alongside.

Concepts, architecture, governance, operations, integrations and packs — a page per component.

The opschain command tree, with a manual page for every command.

The v2 API guide and the interactive OpenAPI reference.

Governance is not a layer bolted on top — it is the execution engine. Each capability below links to its reference page.

Explicit authorisation on every request, secrets in vault custody, and a tamper-evident history — supporting the evidence your auditor asks for.

Approvals enforced as policy on the path where changes run: quorum, self-approval excluded, and change windows with audited overrides.

AI operators work as governed teammates — a named human owner, trust earned through evidence, server-side transcripts, and an emergency stop.

Versioned, schema-validated workflows and actions orchestrated across your estate — humans, automation and AI operators under the same governance.

Inbound events arrive signed and replay-protected; outbound credentials are issued just-in-time, scoped and masked; every crossing is audited.

Live step logs, statuses and events for every change and workflow run, with a queryable history across the estate.