Boss Loops

Boss Loops is the governed operating-loop product: finite-state operational cycles with actor attribution, guard enforcement, evidence, and an immutable audit trail.

Boss Loops ships in two distribution models — same product, same model:

Boss Loops Cloud — the managed, multi-tenant service. Better Data operates scale, isolation, metering, and upgrades.
Boss Loops OSS — the self-hosted, open-source distribution you run yourself.

Both distributions are powered by the Loop Engine runtime (@loop-engine/*) — the underlying technology, documented under Runtime.

Try it in 5 minutes

The canonical demo is the Spreadsheet Approval Loop — the workflow is the product:

1Google Sheet staged change → Slack approval → Boss Loops transition
2→ Google Sheet apply → confirmation / evidence trail

There are two ways to experience it:

| | Run locally in 5 minutes | Run live with integrations | | - | --- | --- | | Product | Boss Loops OSS | Boss Loops Cloud | | What you get | dry-run of the Spreadsheet Approval loop over seeded evidence | live Slack approval + live Google Sheets apply | | Credentials | none | Slack app + Google OAuth | | Command | pnpm boss-loops:demo --dry-run | request access (below) |

1# Boss Loops OSS — local, credential-free 5-minute proof
2pnpm boss-loops:demo --dry-run

OSS proves the loop. Cloud runs the workflow.

The OSS dry-run walks the real loop state machine and prints the staged change, the approval, the applied result, and an audit trail — with no Slack/Google credentials. Live Slack + Google execution is Cloud-first; see Boss Loops Cloud.

In this section

Boss Loops Cloud — managed runtime, metering, isolation, drift detection.
Boss Loops OSS — self-hosted distribution and packages.
Runtime — Loop Engine technology: state machine, actors, guards, package APIs.
Registry — published loop definitions catalog.
Integrations — connecting loops to your systems.
Governance — guards, evidence, audit, and access control.
API Reference — Boss Loops API (generated from OpenAPI).