Every capability has its own page: what it does, the mechanism behind it, and the same thing shown on one domain with real screens and figures.
Turn many source records into one agreed record, and keep it that way as the sources change.
Construct, deduce and piece together an entity's attributes from every source; match, survive, keep the cross-reference, unmerge.
Read the page →Queues sorted by confidence and value at stake, proposals with their evidence, large clusters worked in a grid.
Read the page →Models propose, rules validate, people approve where judgement matters; autonomy earned per action type.
Read the page →Change capture on the way in, write-back through released interfaces, with the acknowledgement stored.
Read the page →Give the records the structures the business reports and plans on, and keep the code lists behind them.
Place entities in levels; several hierarchies per entity; versions with dates; validated against the facts.
Read the page →Code lists and crosswalks as small domains with the same history, rules and security.
Read the page →Reference, hierarchical, dimension, master and transaction data in one place, with the keys enforced.
Read the page →Decide what a correct record is, who may see and change which part of it, and keep the evidence.
Column rules, row rules and business rules across tables and over totals, in one language.
Read the page →Read, write and delete controlled at column level and row level, with each source's own permission passed through.
Read the page →Every change and every sensitive read, append-only, with point-in-time reads.
Read the page →Answer whoever asks: applications, services, warehouses, lakes and agents, under one policy.
Satellite applications pass the keys they hold and receive the golden record, its cross-reference and live related facts.
Read the page →REST, SOAP and SQL for any combination of fields, read and written under one policy.
Read the page →Read external systems, warehouses and lakes in place, by the level of authorisation.
Read the page →Put the records in front of people in a form they can read, mark up and follow to the source.
Infinite scrolling over any table size, with sort, filter and aggregation pushed down to the source.
Read the page →Colour, icon, mask or note per cell by rule; provenance visible in the grid.
Read the page →From a golden record or a pivot cell to the orders, invoices and tickets behind it, across systems.
Read the page →Read, compare, plan and query on the golden records with the transactions beside them.
Dimensional views, measures, multi-measure comparison, calculated measures, transposed views.
Read the page →Type a number at any node; split it by weights, equal shares or a time profile; every split audited.
Read the page →Two measures side by side from two systems for the same golden record, with the difference explained.
Read the page →SQL, Python and statistics on the bed under the same security; results published as attributes.
Read the page →Charts beside grids over one query, for storytelling with the data itself.
Read the page →A plain-language quick query and a SQL interface, both governed.
Read the page →The rules, the stewardship queue, the audit trail and the write-back are the parts the quality section runs on; it adds the agents, the scoring, the correction loop and the enforcement gate.
The order that suits a programme depends on what it is being asked to fix first.
| If the first problem is | Read in this order |
|---|---|
| Duplicate customers or suppliers | Golden records → stewardship → AI-assisted → integration and sync |
| Reports that disagree after a reorganisation | Hierarchies and levels → the data bed → time series and pivots |
| An audit finding or a security question | Twelve security layers → audit trail → rules at three levels |
| Every new application needing its own data load | Headless API → data services → federated display |
| Planning numbers maintained in spreadsheets | Time series and pivots → data entry and disaggregation → comparing measures |
Yes. They are capabilities of one platform under one licence tier, and a domain uses the ones it needs. Pricing is by platform capacity, with domains, records, attributes and users included in the tier.
The eight mandatory features of the market definition map onto these pages; the mapping table is on what master data management is, and the analyst guide goes through the scoring.
The demonstrations page lists what can be shown live, with the length of each walkthrough.
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.
