Patrimoine
FR Join the beta
Patrimoine · Architecture

Built brick by brick.

Proven open-source bricks, a Business Context Layer in the middle, the agents and the harness on top.

/modelling
01The diagram and the layers

Raw data in. An estate out, augmented by the people who know it.

Your sources stay where they are. Patrimoine collects, transforms and governs them in your cloud. Out comes your data estate, with its Business Context Layer: the definitions, the decisions, the context. Your screens, your BI and your AI assistants all read the same data. The agents run the chain 24/7, through the harness.

Patrimoine architectureYour sources, loose, enter the harness where ten agents collect, transform, test and govern the data in your cloud. Out comes your data estate, built brick by brick, with its Business Context Layer, served to Patrimoine, your BI, your AI assistants and your outbound flows. Your teams’ decisions and explanations come back into the loop. Your sourcesERP, CRM, POS, HR, files, in-house toolsHarness · ten specialised agentsPO · Ingestion · Modelling · Quality · Operations · Insights · Catalogue · Costs · Security · FlowsCollectdlt · DagsterTransform, testdbt · ElementaryGovernCube · catalogueLimited toolsAuthorisationSandboxLog and traceContextModel gatewayBenchthe agents reread them continuously, and actData estate+ Business Context Layergoverned, enriched with contextPatrimoineHQ, morning reportYour BIPower BI, Tableau, MetabaseYour AI assistantsDust, Copilot, Claude · via MCPOutbound flowsERP, CRM, API, emailexposed to your teamstheir decisions and explanations come back into the loopON-PREMGCPAWSAZUREYour cloudInstalled in your cloud · run 24/7 by the agents, through the harnessPatrimoine architecture Your sourcesERP, CRM, POS, HR, files…Harness · ten agentsCollectdlt · DagsterTransform, testdbt · ElementaryGovernCube · catalogueLimited toolsAuthorisationSandboxLog and traceContextModel gatewayBenchData estate+ Business Context LayerPatrimoineHQ, morning reportYour BIPower BI, Tableau, MetabaseYour AI assistantsDust, Copilot, ClaudeOutbound flowsERP, CRM, API, emailON-PREMMULTI-CLOUDYour cloudInstalled in your cloud, run 24/7 by the agents
Your teams’ decisions and explanations come back into the loop: the agents reread them continuously.
01
Your sources

Everything that produces data in your company: the ERP, the POS, the e-commerce site, the CRM, tickets, payroll, projects, databases and files, and your in-house tools. Nothing is migrated: your tools stay in place, Patrimoine reads where the data already lives.

SAPOdooShopifySalesforceJiraLuccaPostgreSQLSFTPAPIand more
02
Collect and orchestrate

Around the clock, connectors drop a raw, timestamped copy of each source into your cloud. A data contract checks on the way in that the expected format is respected; if not, the load waits and the agent opens an incident. Dagster runs the steps in the right order.

dltDagsterPydanticcontainerised jobs
03
Transform and test

Raw becomes clean, then business-ready tables: sales, stock, margin, customers. Every transformation is written in SQL, versioned and tested, and changes go through a sandbox and a review before touching production.

dbtElementaryPostgreSQLDuckDBParquet
04
Your data estate + Business Context Layer

What the platform produces, and what belongs to you: a catalogue of tables with their lineage and history, and on top of it the business meaning: certified KPI definitions, the KPI tree, the contracts, and the decisions and explanations signed by your teams. It is the only thing exposed outside.

See how it is served to your AI tools
CubecataloguedefinitionsKPI treesigned decisions
05
Exposure

This governed data feeds everyone the same way: Patrimoine screens, your existing BI, your AI assistants through MCP, and your outbound flows to the ERP, the CRM or by email. One number for margin, whatever tool displays it.

PatrimoinePower BITableauMetabaseDustCopilotERPCRM
02Business Context Layer · MCP

At last, governed and contextualised data for your AI tools.

The company’s AI assistants and systems receive the same number as the teams, with its definition, its context and its decisions, through MCP, the standard that links an assistant to a service.

Business Context Layer and MCP server In Patrimoineyour teams enter, the agents stateCERTIFIED DEFINITION · V3Revenue minus purchases, over revenue.AGENT FINDING · 06:002/3 of the gap comes from textile.SMCONTEXT · SOPHIE MAREKClearance extended by a week.NBDECISION · NADIA BENSAÏDNo textile promo before 5 Oct.CVADJUSTMENT · AWAITING CERTIFICATIONTarget 29% in October.Your data estatecontextualised, recomputed continuouslyPatrimoine MCP serverlinks an assistant to a serviceread-onlythe person’s rightsevery question loggedYour AI assistantsDust, Copilot, Claude, ChatGPTYour systemsERP, CRM, API, outbound flowsYour analysis toolsBI, notebooks, spreadsheetsYour source of truthany app needing certified datawith everyone’s rights · every read loggedBusiness Context Layer and MCP server In Patrimoineyour teams enter, the agents stateCERTIFIED DEFINITION · V3Revenue minus purchases, over revenue.AGENT FINDING · 06:002/3 of the gap comes from textile.SMCONTEXT · SOPHIE MAREKClearance extended by a week.NBDECISION · NADIA BENSAÏDNo textile promo before 5 Oct.CVADJUSTMENT · AWAITING CERTIFICATIONTarget 29% in October.Your data estatePatrimoine MCP serverread-onlythe person’s rightsevery question loggedYour AI assistantsDust, Copilot, Claude, ChatGPTYour systemsERP, CRM, API, outbound flowsYour analysis toolsBI, notebooks, spreadsheetsYour source of truthany app needing certified data
01

Your teams enter it in Patrimoine: an explanation, a decision, an adjustment. Agents surface the facts, your teams give the context.

02

Continuously, the numbers and their context merge into your data estate: governed, contextualised, yours.

03

The MCP server serves your certified data, your source of truth, back to the company: AI agents, systems, analysis tools, with everyone’s rights.

Example from the Maison Verdier demo, a fictional retailer.

03The foundation

Installed in your cloud in a day, rebuilt elsewhere in a few hours.

An infrastructure module creates everything in your cloud account, your own server or several providers at once. Identities come from your SSO, every action is traced, and nothing depends on one particular provider.

The foundation, in bricks
TerraformDockerGitHub ActionsSSO · Entra ID, GoogleSCIMOpenTelemetryYour cloud accountOn-premise serverMultiple providers

Product names belong to their respective owners. Patrimoine assembles these bricks; it is affiliated with none of them.

Next pageTrust Where your data lives, access and identities, personal data, vulnerabilities.