Skip to content

Architecture ​

How the multi-app RBS ecosystem fits together (canonical count per apps.json).

The three layers ​

1. Identity & CRM — Camino ​

The front door for every user session, every partner app, every CRM activity. CRM/front door (IdP role retired — issuer is the CPR; see integration/auth.md), multi-tenant org primitives, unified customer timeline. See /apps/camino/.

2. Payments & billing — Colectiva ​

MXN payment rails, subscriptions, wallets, transfers. Webhook delivery hub for payment events. See /apps/colectiva/.

3. Fiscal — Constanza ​

CFDI 4.0 stamping, contabilidad electrónica, multi-tenant fiscal operations for Mexican legal entities. Stamps invoices generated anywhere in the ecosystem. See /apps/constanza/.

Integration backbone ​

Tier 1 apps (full public API surface) ​

Camino, Colectiva, Constanza, Agente

Tier 2 apps (narrow surface) ​

Caracol, Mancha, Agora, Cookie Monster, Patadas

Other apps (internal or future-public) ​

Baul, Comal, Cosmos Pet, Garita, Goodbay, La Hoja, Madriguera, Plenura, Puppy Love, Rito, Servilleta, Continua

Their surfaces are not yet public. See /apps/ for the current T1/T2 set.

SDK ​

One TypeScript SDK unifies all cross-app integration: @r-bsoftware/ecosystem-sdk. See /reference/sdk.

Source of truth ​

  • App registry: ecosystem-sdk/packages/mcp-server/src/registry/apps.json (21 canonical apps)
  • Event registry: ecosystem-sdk/packages/mcp-server/src/registry/events.json (101 events)
  • SDK source: ecosystem-sdk/packages/sdk/src/

Red Broom Software Ecosystem