CluedIn is a graph-native 'agentic data management platform' with schemaless ingestion, golden records as projections over per-source data parts, seven named agents, a public price list and a 60-second deployment with 15,000 free records.
Every CluedIn cell carries its source number; the sources are listed at the foot of the page.
| Question | CluedIn | Lima master data |
|---|---|---|
| Where the master data lives | Three internal stores (search, graph, blob) behind GraphQL; golden records are projections of data parts per source; Streams copy golden records out to Azure SQL, Data Lake, OneLake, Event Hub and HTTP endpoints [1][2]. | Golden records are governed views over the sources, read in place through the federated engine, and materialised only where latency needs it, in your lake, under the same keys. The transactions sit in the same bed, so a merged customer and its orders change together. |
| Reaching SAP, Oracle and the lakes | Crawlers and ingestion copy sources in; Azure SaaS or PaaS in the customer's tenant; Fabric, Purview and Power Platform integrations [1][3]. | SAP S/4HANA and ECC through released read interfaces and change capture; Oracle Fusion through REST and BI Cloud Connector extracts, E-Business Suite through JDBC and open interfaces; Snowflake, Databricks and Fabric read in place; Salesforce, ServiceNow and Workday through their APIs. Write-back through BAPIs, IDocs, REST and web services, acknowledged and logged. |
| Golden record: matching and survivorship | Deduplication projects with Equals, Sift4 fuzzy, DoubleMetaphone, contains, first-token and e-mail functions plus normalisers; identifiers merge proactively; unmerge returns the project to review; survivorship defaults to manual edits then most recent, with custom rules per property and source [4][2]. | Strong keys first (VAT ID, DUNS, GTIN, manufacturer part number), then standardised attribute and address matching, with a language model for the hard pairs; two thresholds per rule (review, merge); survivorship per field by source rank, recency, verification and steward override; unmerge restores the sources; every value keeps its source, rule and time. |
| Hierarchies and reference data | Relationships as graph edges traversed by GraphQL; level-based hierarchy modelling is undocumented; Gartner's noted strength is 'zero upfront modeling' [1][5]. | Levels and several hierarchies per entity, kept as versions with validity dates and validated against the facts they aggregate; reference data and crosswalks kept as small domains with the same history, rules and security. |
| Rules, security and audit | Data-part, golden-record and survivorship rules; 14 built-in roles governing features and data access through source permissions and access-control policies; history excludes changes made by rules [4][6][7]. | Column, row and business rules in one language, evaluated on save and on demand, including rules over aggregates and across tables; twelve security layers for read, write and delete; an append-only audit trail with point-in-time reads and logged reads of sensitive columns. |
| APIs and data services | GraphQL for reads with full-text and property syntax, page sizes shown up to 10,000; Streams for bulk out; API tokens [1]. | REST, SOAP, SQL (JDBC and ODBC), events and an agent endpoint over one policy engine; the golden-record lookup answers with the record, the cross-reference and live related facts; page sizes and rate limits published per endpoint. |
| Analytics: pivots, measures, transactions | Explain log and relations history; analytics through Streams to a lake; pivots and measures are absent [1][7]. | Pivots on any hierarchy level with time on the columns and measures in the cells; calculated measures; data entry with disaggregation by weights, equal shares or a time profile; drill-down from a cell to the transactions and to the source row; charts beside grids; natural-language and SQL querying. |
| Pricing unit and trial | A public SaaS rate card: $0.005 to $0.051 per processed record, the first 15,000 records and $100 of AI credit free, no card required, unlimited users; PaaS per CPU core on Azure Marketplace [8][9]. | Platform capacity tiers (32C to 128C); domains, records, attributes and users included; the price is written before the work starts; a guided first domain on your data in one day; the showcase estate for demonstrations; a self-service sandbox tier is a decision pending (see the review notes). |
| Analyst placements 2025–26 | Gartner Magic Quadrant for MDM Solutions, April 6, 2026: Visionary, with 'performance with bulk historical data' as the noted caution [5]. | Analyst evaluation is the purpose of this page set; placements to date: none. The platform pages are organised on Gartner's eight mandatory features and four implementation styles so a briefing lands in the right market. |
Choose CluedIn when a schemaless, graph-first start on Azure with a public price and an instant trial is the priority, and when the data team prefers agents and rules over an upfront model. Its rate card and 60-second start are real advantages for a small team proving value before a bigger commitment [8].
Lima suits the enterprise whose master data should be governed on the rows in place across SAP, Oracle, the CRM and the lakes, with the transactions in the same bed: the golden record and its orders in one query, rules over totals, pivots on golden dimensions with data entry and disaggregation, drill-downs to the source row, and a headless lookup that answers with live related facts. Twelve security layers and an append-only audit trail apply to every door, and the price is written before the work starts.
The domain catalogue shows thirty domains with, for each, the objects read in place in SAP S/4HANA, Oracle Fusion, Salesforce, Workday, ServiceNow, Snowflake and Databricks and the interface used for the write-back.
Facts change; re-check the sources at each review and re-date the page.
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.