Crème Data Platform — one governed data layer, two access paths

The apps you already use keep their own database access. The MCP connector adds a second, governed path — the same data, now reachable in plain English by people and by AI agents (including many parallel Cowork sessions). One connector, and every data domain becomes conversational — safely, per person, per brand.

Availability: Live today Near-term Future (data exists in the warehouse)

Variant A

Layered stack — two access lanes forking off one governed data layer

Web apps — humans clicking

CRM front-end
relationships & pipeline
Reporting portal
dashboards & reports
Warehouse-automation
fulfillment & billing

Conversational — people & AI

Claude app
ask in plain English
Cowork
agentic — many parallel sessions doing work

App backends & APIs

Each app's own API + direct database access (unchanged).

CRM API
Portal API
Warehouse API
soon

MCP Connector

The governed conversational path — one entry point for people and AI.

Governance ring

  • Identity — per-user OAuth (portal login)
  • Access — brand × domain permissions
  • Reads — read-only, brand-scoped views / RLS
  • Writes — via each app's validated API
  • Audit — every call logged to the user

Governed data layer — brand-scoped views / RLS · creme_portal + warehouse

CRMdeals·contacts·retailers·brands·comms
Performancesell-through·SKU·wholesale·reports
Inventory
Sales & transactions
Fulfillment & billing
FinancialsP&L·balance sheet

Pipeline & sources (by type — current vendor in parentheses)

creme-elt → warehouse
bronze → silver → gold (dbt) · Postgres warehouse + creme_portal
CRM
Custom CRM (repl. HubSpot)
DTC / storefront
Shopify
EDI / B2B
Bamboo Rose·Spring·SPS
WMS / 3PL
Camelot
Accounting
QuickBooks

Both paths read the same governed data; the MCP connector adds the identity + brand/domain scoping for the conversational lane. Who sees what: brand users (e.g. Wonder Valley) → their brand only; Crème employees → cross-brand, per permissions.

Variant B

Governed data core — apps on one wing, people + AI on the other

Web apps — humans clicking

CRM front-end
relationships & pipeline
Reporting portal
dashboards & reports
Warehouse-automation
fulfillment & billing

App APIs + direct DB

each app's own access, unchanged

Governed data core

brand-scoped views / RLS
CRM
Performance
Inventory
Sales & transactions
Fulfillment & billing
Financials

creme_portal + warehouse ← creme-elt (bronze→silver→gold) ← sources

Conversational — people & AI

Claude app
ask in plain English
Cowork
agentic — many parallel sessions

MCP Connector

governed path for people + AI

Governance ring

  • OAuth identity
  • Brand × domain access
  • Read-only views · API writes
  • Audit per user

One governed core; two ways in. The apps keep direct access for point-and-click work. The connector opens the same data to natural-language and agentic use — every request identity-checked and brand/domain-scoped. Sources by type, current vendor in parentheses: CRM (Custom CRM, replacing HubSpot) · DTC (Shopify) · EDI/B2B (Bamboo Rose·Spring·SPS) · WMS/3PL (Camelot) · Accounting (QuickBooks).