EBX is the model-driven, multidomain platform for master, reference and metadata that Orchestra Networks built, TIBCO acquired in 2018 and Cloud Software Group carved out as the autonomous unit 'ON EBX' on March 26, 2026.
Every ON EBX cell carries its source number; the sources are listed at the foot of the page.
| Question | ON EBX | Lima master data |
|---|---|---|
| Where the master data lives | Datasets and tables live in the EBX repository inside dataspaces (branches and snapshots give versioning); the Data Exchange add-on loads copies; on-premises, hybrid and cloud-supported deployment [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 | REST and SOAP data services generated from the data model, CSV, XML and Excel import and export, and middleware for target systems; SAP and Oracle read paths run through integration tools [2][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 | A Match and Merge add-on with matching, golden-record life cycle and merging; the comparator list and survivorship policies sit in documentation that moved to docs.onebx.com and was unreachable at the time of checking [4]. | 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 | Hierarchical views built from foreign keys or group-by dimensions, with ragged support and time-based dimensions; reference data management as a named pillar [1][2]. | 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 | Schema constraints with severities (error, warning, information); five permission levels (dataspace, dataset, table, record, field) with programmatic access rules; history tracking across dataspaces and snapshots [1][5]. | 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 and SOAP APIs listed on the platform page; a GraphQL add-on in the add-on catalogue; 'Governed Data Services' as a pillar [2][6]. | 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 | The Insight add-on provides indicators and dashboards about the repository; pivots and measures over transactions are absent [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 | Pricing and trial are absent from onebx.com; the demo request is a form; a third-party benchmark reports renewals 15 to 30% above prior terms (unconfirmed); reviewers report instability after the version 6 upgrade [2][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: Niche Player (as TIBCO); 2021 MQ: Leader; PostNL cites 30 to 40% lower MDM technology cost [10][2]. | 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 ON EBX when a flexible, model-driven repository for reference data and metadata with dataspace versioning is the priority, when on-premises deployment is required, and when an existing EBX estate should be extended in place. Its data-model flexibility, noted by Gartner, is a real advantage for reference-data-heavy financial services [10].
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.