Skip to main content

​
Platform architecture

How the four layers of the Better Data platform connect: Loop Engine, Commerce Gateway, SCM/DCM modules, and Signal Tags.

​
The four layers

LayerWhat it doesOSSHosted
Loop EngineGoverns decisions — AI, human, and automation@loop-engine/* · loopengine.ioloops.betterdata.co
Commerce GatewayConnects LLMs to commerce data@betterdata/commerce-gateway · commercegateway.iogateway.betterdata.co
SCM/DCM modulesSupply and demand chain operations@betterdata/scm-*, @betterdata/dcm-*app.betterdata.com
Signal TagsPhysical product authentication@betterdata/signal-tags-schema · tagd.shverify.betterdata.co

​
How they connect

Signal Tags scan
      ↓
Loop Engine          ← decision governance
      ↓
Commerce Gateway     ← LLM commerce data
      ↓
SCM/DCM modules      ← supply / demand operations
      ↓
Better Data platform ← AI, compliance, analytics
A tag scan, procurement approval, or order event can open or advance a loop. The gateway exposes tooling to LLMs against the same operational data the SCM/DCM modules maintain.

​
OSS vs hosted

Every layer is available as Apache-2.0 open source (self-hostable). The hosted platform adds:
  • Multi-tenant isolation
  • AI-assisted demand intelligence and forecasting
  • Industry Pack policy overlays (Healthcare, Pharma, Retail, Manufacturing, Food & Beverage, Construction)
  • Compliance reporting (DSCSA, EU FMD, FDA UDI/FSMA, and related regimes)
  • Enterprise SLA and support
Industry Packs and parts of the control plane are proprietary; domain packages and loop definitions remain OSS.

​
The loop model

Everything important in the platform is modeled as a loop: a governed workflow with named actors, guard policies, evidence, and an audit trail. Examples:
  • Procurement loop — AI recommends → guard evaluates → human approves → PO executes
  • Quality loop — Signal Tag scan → verification → quarantine or release
  • Returns loop — RMA request → inspection → disposition
See Loops and Hosted Loop Engine.

​
Where to go next