What is OpsChain?

OpsChain automates and governs enterprise operations at scale, with human teams and AI operators working under the same policies. You model your estate as a tree of projects, environments and assets, describe the work as actions and workflows kept in Git, run that work with full logging and approval gates, and then let events and triggers run the estate for you. Every action is recorded as it runs — who asked, who approved, what ran and what it touched — so the proof of how a change happened is a query, not a reconstruction.

Everything ships in one binary: the opschain CLI, the server (with its web GUI and API), and the runner that executes work. The same commands work locally against a repository on your machine or against a shared server.

What you can do with it

• Model the estate — projects, environments and assets, each addressed by a path. Properties, settings, access rules, maintenance windows and artifacts all attach to nodes in that tree.
• Author work as code — actions are YAML files in a Git repository, composed into larger actions and reusable packs, pinned to exact revisions through templates, so what an asset can run is always a reviewable Git fact.
• Run and govern changes — create changes and workflow runs against estate nodes, follow their logs, gate them with approval policies, and answer the gates from the CLI or the GUI.
• Automate with events and triggers — every API write and run emits events; standing when/then rules turn those events into new changes and workflow runs, with correlation chains for one-command root cause.
• Operate it day to day — runner fleets with placement and drain controls, a secret vault with external provider bindings, federated sign-in, path-based access control, backup and restore, and retention that keeps the record auditable.
• Enrol agents under governance — operator processes and AI agents work under the same authorisation, approval and audit machinery as people, with tiered trust grants and layered kill switches.

The recorded history supports your evidence for standards such as ISO 27001, SOC 2 and APRA CPS 230 and 234 — it is material for your assessors, not a compliance claim in itself.

Where to start

• Getting started — the hands-on learning path, from a fresh install to an estate that runs itself. The same runbooks are embedded in the binary: opschain learn.
• Concepts summary — the OpsChain vocabulary in one page, and architecture for how the pieces compose.
• The opschain CLI — the command reference, with a manual page per command.
• The v2 API and the interactive OpenAPI reference — the integration contract.

The reference pages are also served by the product itself — opschain docs in the CLI, and the Documentation area of the web GUI — so the copy you read there always matches the version you are running.