Semarchy's Data Platform (formerly xDM, xDI and xDG) is an independent MDM whose hub lives in a customer-owned PostgreSQL, Oracle or SQL Server database, with SemQL for matching, rules and security, and a 30-day trial.
Every Semarchy cell carries its source number; the sources are listed at the foot of the page.
| Question | Semarchy | Lima master data |
|---|---|---|
| Where the master data lives | The hub is a relational database you own, with source (SD), master (MD) and golden (GD) tables per entity; golden data can be read by SQL directly; a Snowflake Connected App keeps processing inside the Snowflake tenant with 'zero data egress' [1][2][3]. | 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 | Loads arrive through a SQL API (load ids), REST and continuous loads; native SAP and Oracle read paths are unpublished; SaaS, Snowflake-native, self-hosted on AWS, Azure, GCP, on-premises and, since September 14, 2026, OpenShift and Rancher [1][4][5]. | 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 | A certification process: enrich, validate, match with SemQL rules (fuzzy lookups since 2025.1), consolidate with strategies (custom ranking, longest, most frequent, preferred publisher), then publish and historise; source keys kept as PublisherID.SourceID [6][7][8]. | 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 | Hierarchies as business views over foreign keys with balanced, ragged and relationship-entity patterns for alternate roll-ups; hierarchy versioning is undocumented; reference entities are ordinary entities [9]. | 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 | Validations for mandatory, list of values, unique keys, referential integrity and SemQL row rules; model, entity and attribute privilege grants with SemQL row-level filters (a stated limitation on some views); golden and master data historised with 'as of' reads by batch or date, empty until the model is redeployed after enabling [6][10][11]. | 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 | REST query, count and named-query endpoints with field selection ($expr), default page size 100; a SQL API for loads and direct SQL on hub tables; generated REST APIs for publishing golden records [12][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 | A Dashboard Builder charts query results and can embed a chart in a form bound to the current record; pivots and measures over transactions are absent [13]. | 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 | Pricing is unpublished on the site; a Carahsoft AWS Marketplace private offer lists $705,200 for a 12-month, 20-million base-object contract; a 7-day licence is issued instantly and a 30-day licence on approval; Snowflake Marketplace trials on request [14][15][16]. | 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: Leader; Gartner Peer Insights Customers' Choice 2024; Forrester TEI: 315% three-year ROI [17][18]. | 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 Semarchy when a hub in your own database with direct SQL access is the intended architecture, when SemQL-style configuration suits a technical team, and when a Snowflake-native deployment or a sovereign self-hosted option matters. Its 30-day trial and '12 weeks to production' record are real advantages for a team that wants to prove the model before buying [15][19].
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.