Boss Loops is open core — inspect and self-host the Apache-2.0 engine, or run governed decisions on Boss Loops Cloud.
Explore Boss Loops Cloud →Loading
Governed Decision Intelligence
Every day your operation approves, releases, holds, and commits — decisions made by humans, AI assistants, and autonomous agents together. Your systems record the transactions, the workflow state, the analytics. Almost none of them preserve why the decision was made.
Boss Loops is the system of record for decisions — the evidence it was made on, the policy it cleared, and every participant, human or AI, preserved on one immutable Decision Record. Your ERP records what happened. Boss Loops remembers why.
Decision memory
The transaction lands in the ERP. The steps land in the workflow engine. The metrics land in the BI stack. The decision itself — what was known, which policy applied, what the AI recommended, who judged it and why — evaporates into chat windows, screenshots, and threads nobody can find.
What's lost is more than auditability. Institutional knowledge walks out with the people who made the calls. The same case gets decided differently on different days. An AI recommendation that can't be explained afterward is autonomy you can't extend. And you can't improve decisions you never captured.
“When someone asks why it was approved — leadership, operations, or audit — you don't reconstruct the story. You retrieve it.”
Boss Loops preserves organizational decision memory: evidence frozen at the moment of capture, approvals signed on the record, every decision answerable years later — by construction, not by discipline.
The control layer
Boss Loops sits between intelligence and execution as the governance runtime. Four layers, one linear flow — and every consequential decision culminates in an immutable Decision Record.
01 · The spark of action
Models analyze, classify, and recommend transitions. They are the proposers in the system — they cannot commit operational state.
02 · Truth, frozen in time
Governed data snapshotted the moment it informs the decision — not a link that might change, a value with provenance inherited from your warehouse.
03 · Deterministic trust
The Boss Loops engine, where intelligence and evidence are fused and verified against policy. Guards are structural gates, not prompt-based instructions — they decide whether a transition may commit before any side effect occurs.
04 · Accountable execution
Your systems of record are updated only after policy passes — every write downstream of a governed, recorded decision.
The Decision Record
One immutable, auditable artifact: the situation, the frozen evidence, the policy that applied, the humans and AI that participated, and the outcome that followed.
Your data context, unchanged
Your ERP holds the invoice. Snowflake and Looker hold the metric definitions your business already runs on. Boss Loops links to them — frozen at decision time — and records why you acted.
No ontology project
No re-modeling your business to get there. You consume the metrics your business already runs on — no second definition to populate and maintain.
Qualification inherited from the source
Evidence carries how governed it is. If your warehouse calls it a golden record, the auditor sees a golden record on the decision.
Frozen, not linked
A link might change. Evidence is snapshotted the moment it informs a decision — so it's answerable years later.
A pattern, not a vertical
The same governed flow — a signal opens the loop, policy gates the commit, the record holds the answer — applied to the decisions your operation already makes.
Life Sciences
A monitoring signal opens the loop. Release cannot commit without validated readings and multi-party sign-off — and the record shows exactly what the reviewers saw.
See the pattern →
Finance
A request beyond threshold opens the loop. Approval requires qualified evidence and named authority — the AI recommends, the record attributes.
See the pattern →
Operations
An exception opens the loop. The commitment carries frozen evidence and the exact rationale — retrievable when someone asks why, quarters later.
See the pattern →
Request a demo
Alpine walkthrough — no signup →Build OSS
Quick start + GitHub →Run Cloud
Talk to us about your tenant →Sign in
Production workspace →Governance you can verify
The claims on this page aren't marketing you have to take on faith. The Boss Loops engine, the evidence contracts, and the conformance suite are Apache-2.0 — inspect the code, run the suite, and prove the invariants yourself before you trust a single consequential decision to it.
SDK install steps, package reference, and adapter guides live in the docs — where builders need them.
Latest update
Product · May 19, 2026
How workflows become governed AI-assisted decision systems with runtime guards, human oversight, evidence capture, and continuous learning.
Read more →
Announcements · Jan 12, 2026
One platform to sense demand, decide allocation, execute moves, govern access, and improve over time — so your supply chain runs like a system, not a scramble.
Read more →
Better Data blog
Follow the Better Data blog for Boss Loops release notes, evidence-provider previews, and governed-decision patterns from the field.
Read more →
