Mera Commerce OS — Runtime Architecture

Mera Commerce OS — Runtime Architecture An architecture diagram generated by Archify. Browser · Customer / Operator · Vercel Edge + Mera Control Plane Browser Customer / Operator Web App · Mera Astro / Next · Vercel Edge + Mera Control Plane Web App Mera Astro / Next Mera API · Domain commands · Vercel Edge + Mera Control Plane › sg-mera :443 · authoritative Mera API Domain commands authoritative Auth · JWT + RBAC/ABAC · Vercel Edge + Mera Control Plane · policy-aware Auth JWT + RBAC/ABAC policy-aware Redis · cache / queue · Vercel Edge + Mera Control Plane Redis cache / queue PostgreSQL · canonical store :5432 · Vercel Edge + Mera Control Plane › sg-mera :443 · source of truth PostgreSQL canonical store :5432 source of truth 01 Commerce Foundation · 97% accuracy · Mera Commerce OS — 6 Systems 01 Commerce Foundation 97% accuracy 02 D2C Growth · 3x pipeline · Mera Commerce OS — 6 Systems 02 D2C Growth 3x pipeline 03 Marketplace · 0 oversells 43d · Mera Commerce OS — 6 Systems 03 Marketplace 0 oversells 43d 04 Omnichannel · 8 min recon · Mera Commerce OS — 6 Systems 04 Omnichannel 8 min recon 05 Operations · 60% fewer stockouts · Mera Commerce OS — 6 Systems 05 Operations 60% fewer stockouts 06 AI Agents · 22% → 9% RTO · Mera Commerce OS — 6 Systems 06 AI Agents 22% → 9% RTO Integrations · Shopify / Amazon / WhatsApp · Architecture component · provider-agnostic Integrations Shopify / Amazon / WhatsApp provider-agnostic HTTPS REST /api verify JWT + policy read-through fallback on miss Vercel Edge + Mera Control Plane sg-mera :443 Mera Commerce OS — 6 Systems Legend Frontend Backend Database Security External

Edge + Identity

  • • Browser → Web App → API → PostgreSQL (canonical) via Data Harness boundary
  • • Data Harness (00) is a named system in mera-systems.json — policy + PII + retrieval before AI
  • • Redis read-through with PG as source of truth

Commerce Systems

  • • Six productized systems own canonical entities (01–06)
  • • Each card reuses the same metric string as Platform and Command Center
  • • Provider-agnostic integrations normalize into the same entities

Trace-ready

  • • Every node/edge has stable ID including Data Harness
  • • Trace shows: Where did answer come from? + Why was AI allowed? (Harness)
  • • One manifest → Platform → Docs → Command Center