A master-data hub loads a copy of the sources, matches there, and publishes a second copy to a warehouse for analytics; the copies then need syncing, reconciling and stewarding.
| Line | What it is | Your number |
|---|---|---|
| Hub licence per record or per domain | the unit most hubs price on; grows with sources and domains | … |
| Warehouse re-publish | pipelines, storage and compute to copy golden records to the warehouse or lake | … |
| Sync back to the sources | integration work and licences per system, per object | … |
| Reconciliation | the effort to explain why the hub, the warehouse and the source disagree | … |
| Stewardship with names and addresses alone | time spent deciding hard pairs with names and addresses alone | … |
| Analytics on a copied dimension | BI models rebuilt when a hierarchy changes; reports that show merged customers with unmerged orders | … |
| Second security model | row and column policies re-implemented in the warehouse and in BI | … |
| Upgrade and environment promotion | the hub's own upgrade cycle and configuration migration | … |
With golden records as governed views over the sources and the transactions in the same bed, the warehouse re-publish, the second security model and the reconciliation lines fall away; the sync line becomes the acknowledged write-back per object; the stewardship line shrinks because the transactions are on the proposal. The platform is priced by capacity with domains and users included. Put your numbers beside each line and compare the totals.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.