Boss Cloud (hosted HTTP API)

What this is

loopengine.io documents the OSS governed runtime (@loop-engine/*). Boss Cloud is the hosted Integration path: same loop/guard/evidence model, operated by Better Data with tenancy, API keys, and managed connectors (Slack, Google, …).

| Surface | Where to read | | --- | --- | | Boss runtime, taxonomy, adapters | loopengine.io (this site) | | Boss Cloud HTTP contract | This page + monorepo apps/hosted-loops/docs/api.md | | Better Data company, SCM, CCO applications | docs.betterdata.co — not loopengine.io |

OSS runtime defines states, signals, guards, transitions, and events in your infrastructure. Boss Cloud exposes the execution contract over HTTPS when you want managed governance operations.

• Developers & integrations → https://loops.betterdata.co (Bearer JWT for first-party services, le_ API keys for external automation).
• Operators → Automation at app.betterdata.co/automation (product UX; same loops conceptually).

We document shipped Cloud capabilities here and in the monorepo API reference. We do not imply undelivered OSS parity, Studio, docker compose runtime, or a multi-service mesh today — see Runtime Platform Direction and changelog.

Canonical reference

The versioned, route-by-route contract (request/response shapes, errors, connectors, baseline routes, key management) is maintained in the monorepo alongside the apps/hosted-loops implementation:

Boss Cloud HTTP API reference (source)

That file is the developer contract for paths under /api/v1/*. Update pull requests that change route handlers should update apps/hosted-loops/docs/api.md in the same change-set when the public JSON contract moves.

Related OSS docs

• HTTP adapter — webhook-style outbound adapter from the OSS runtime; not the same as Boss Cloud ingress.
• Architecture — core Boss concepts reused by the hosted service.

Pricing

Commercial packaging is described on the product site (do not hardcode prices in integration guides): betterdata.co/pricing.