Profisee is an independent multidomain MDM platform aligned with the Microsoft ecosystem, available as SaaS, PaaS, IaaS, hybrid or on-premises, with the Aisey assistant and agents and an MCP server.
Every Profisee cell carries its source number; the sources are listed at the foot of the page.
| Question | Profisee | Lima master data |
|---|---|---|
| Where the master data lives | Master and reference data are stored in Azure SQL Database on Kubernetes; Microsoft's reference architecture loads master data through Data Factory, loads transactions directly into Synapse, and publishes golden records to the analytics platform; Fabric Open Mirroring writes golden records to OneLake [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 APIs, webhooks, SQL subscription views, Data Factory templates, a Fabric connector, Parquet exchange with ADLS, Databricks and Snowflake connectors; a reviewer notes weak real-time SAP connectors [3][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 | Continuous matching with auto-match and auto-survivorship; 2026 R1 added semantic matching with locally processed embeddings, combinable with similarity methods and thresholds; 'explainable matching' on the platform page [3][6]. | 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 | Relationship management with an interactive graph viewer; Reference Data Management in the Application Edition as the migration path from Microsoft Master Data Services; the depth of alternate-hierarchy support is undocumented publicly [1][7]. | 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 | Expression-language validation rules, REGEX rules and standardisation services; role-based permissions with attribute-level calculations; transaction log with reversals and a full transaction audit trail through web and API (2026 R2); SOC 2 Type II and ISO 27001:2022 published with auditor and dates [6][8][9]. | 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 Gateway generated per entity (OpenAPI), a .NET SDK, webhooks, a Power Platform connector throttled to 100 calls per 60 seconds, and an MCP server that 'enforces existing Profisee permissions' [3][4][10]. | 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 | Analytics is delegated to Fabric, Synapse, Databricks and Snowflake; inside the product, ML anomaly detection ('Augmented Stewardship') and Power BI connectivity; pivots and measures are absent [2][3]. | 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 | Volume-based pricing on total records with 'unlimited data domains and attributes at no extra cost', two editions, SaaS or PaaS, quotes only; Azure Marketplace listings count toward Azure commitments; a tailored demo then a Business Impact Assessment, and no self-service trial [7][11][12]. | 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; Microsoft cites Gartner Peer Insights for 'more implementations that take fewer than 90 days than any other MDM vendor' [13][1]. | 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 Profisee when the estate is Microsoft-first (Fabric, Purview, Power Platform, Azure), when a hub in your own Azure tenant with Open Mirroring to OneLake is the intended architecture, and when volume-based pricing with unlimited domains suits the plan. Its 45-minute PaaS deployment and its published certifications are real advantages for a mid-market or Azure-standardised buyer [1][9].
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.