Better Data

Hosted

Hosted Loop Engine

Edit this page

Hosted Loop Engine

Better Data’s managed loop engine — run governed, observable commerce-chain loops without operating the runtime yourself.

What is the hosted loop engine?

The hosted loop engine at loops.betterdata.co runs the Better Data loop model as a multi-tenant service. You integrate via APIs and module manifests; Better Data operates scale, isolation, and upgrades.

Monorepo services: the running hosted stack includes hosted-loops (runtime + loops database API) and registry-loop (published loop definitions catalog). See Hosted platform apps for how they relate to hosted-gateway-mcp and registry-mcp-server.

OSS alternative: @loop-engine/sdk and loopengine.io for self-hosted runtimes.

What you get with hosted

  • Multi-tenant org isolation
  • Outcome-based metering (billing tied to loop completions — contact us for current model details)
  • TenantCapabilitySnapshot-style capability enforcement for RBAC
  • Tamper-evident loop audit trail and export paths for compliance workflows
  • Drift detection (scheduled validation of expected vs observed state)
  • Outbox relay for cross-module event delivery
  • Industry Pack policy overlays (hosted-only; not published as OSS)

Pricing model

Hosted Loop Engine pricing is outcome-based (per loop completion, not per seat).
Contact hello@betterdata.co for current packaging and terms.

Loop types (canonical)

| Loop | Module | What it governs | | ---- | ------ | ---------------- | | scm.procurement | SCM | AI-assisted PO recommendation + human approval gates | | scm.fulfillment | SCM | Multi-step order fulfillment | | scm.quality | SCM | Inspection, deviation, CAPA-style disposition | | scm.replenishment | SCM | Demand signal → reorder / replenishment | | dcm.demand | DCM | Demand signal detection and replenishment triggers | | dcm.order | DCM | Channel order routing and lifecycle | | dcm.returns | DCM | Return authorization and reverse logistics |

See also Loops for the conceptual model.

Runtime HTTP API (hosted-loops)

The hosted-loops service exposes versioned HTTP routes under /api/v1/... for loop lifecycle, runs, baselines, connector health, and related integrations. Production base URL mapping (for example loops.betterdata.co) is environment-specific — confirm with your deployment or support.

| Prefix | Purpose (high level) | | --- | --- | | /api/v1/loops | List/create loop concerns; catalog, start, transition, cancel, events, history, and integration helpers | | /api/v1/loops/runs | Run detail and comparison | | /api/v1/loops/definitions | Definition-scoped run listings | | /api/v1/baselines | Baselines CRUD, transitions, true-ups, delivery routes | | /api/v1/connectors/* | Connector health and OAuth/event surfaces (e.g. Slack, Google) |

External callers should use the service’s authenticated API only; exact auth header and tenancy claims are defined by the hosted-loops implementation — treat field names and JWT contracts as implementation details to verify in source or release notes.

Getting started

OSS vs hosted

| | OSS (@loop-engine/sdk) | Hosted (loops.betterdata.co) | | - | ------------------------- | ----------------------------------------------------------- | | Cost | Free (OSS) | Per agreement — contact us | | Setup | You operate | No infrastructure setup | | Multi-tenant | No | Yes | | Industry Packs | No | Yes | | Audit / compliance exports | Your pipelines | Platform aggregation + reports | | SLA | Self-managed | Better Data SLA |