Head-to-head · updated 13 September 2026
DataShield vs Stibo Systems: who should master your customer data for agents?
Stibo Systems has been doing master data management since 1994, and the parent company has been in business since 1794. That is not a typo. If your problem is 200,000 product SKUs, 1.7 million digital assets, supplier onboarding and channel syndication, Stibo is one of the two or three names that should be on your list. Gartner made them a Leader in April 2026. They booked a record fiscal year in June. Their STEP platform spans product, customer, supplier, location and sustainability domains, and they now ship an MCP server so agents can read all of it. We are not going to pretend any of that away.
We compete on one slice of it: customer and party data. Ontology masters people and organisations with Fellegi-Sunter probabilistic linkage, LSH blocking and five survivorship strategies, and you can open the match config and retrain it. Then the part nobody else in this market ships: datasets are tokenized at ingest; agents query tokenized data over MCP; detokenization is a privileged, audited operation. Every governed tool call is re-checked against the agent's current authority, and every decision lands in a hash chain you can verify yourself. Here is the honest split, rows Stibo wins included.
The short version
Pick DataShield when
- The domain you actually need mastered is people and organisations, not SKUs. Customers, patients, members, counterparties, claimants.
- Someone will ask you to prove an agent's access log was not edited. An auditor, an examiner, or Article 12 of the EU AI Act. Our chain answers with math, not a policy PDF. Run the verifier.
- You need to pull an agent's authority mid-session and have the very next tool call fail. Not the next token refresh. The next call.
- You want the match logic, the vault, the policy decisions and the evidence running on your own infrastructure, on keys you hold, with a price you can see before you book a call.
Pick Stibo Systems when
- Product data is the job. PIM, digital assets, supplier onboarding, channel syndication, GDSN. We do none of it and we are not going to start.
- You need many domains at once under one roof: product, customer, supplier, location, sustainability. Their six data clouds are a real portfolio, not a slide.
- You are a big enterprise with an SI already booked. Gartner MQ Leader, Forrester Wave Leader, 18 offices, and a foundation owner that has no exit to chase. That is a safe board-level answer.
- Your front office lives in Salesforce and you want mastered customer records pushed back into it, with duplicate prevention at the point of entry.
Bottom line: Stibo is the safe buy for product data at enterprise scale. For customer and party data that AI agents will read, we think the interesting question has moved from "is the record right?" to "who let the agent read it, and can you prove it?" That is the question this page is really about.
Feature by feature
Competitor cells describe what Stibo's public site and press releases say as of the date above. If we have got something wrong, email support@myorg.ai and we will fix it, credited.
| What matters | DataShield | Stibo Systems | Edge |
|---|---|---|---|
| Product MDM, PIM and syndication | None. No PIM, no digital asset management, no supplier onboarding, no GDSN, no channel syndication. Ontology has product identifier classes and taxonomy lookup (UNSPSC, GPC, ETIM, HS, INCI), which is not the same thing and we will not dress it up as one. | The core franchise and thirty years deep. Product Experience Data Cloud, PIM, DAM, syndication, plus ProductGen AI for generated and localized product content with approval workflows. Hager Group runs 200,000+ products and 1.7M assets on it. | ◇ |
| Customer and party mastering | Fellegi-Sunter probabilistic record linkage with Jaro-Winkler, normalized Levenshtein, Soundex and Double Metaphone comparators, LSH blocking, EM-trained m/u parameters, five survivorship strategies, hierarchies, and Population Stability Index drift monitoring on every promoted match config. Match configs can be drafted, trialled, explained, trained and promoted from the tool surface. An absolute-identifier tier routes identifier conflicts to a human instead of blind-merging. | Customer Experience Data Cloud: single customer view, address validation, real-time data quality, and MDM SmartSync for Salesforce with search-before-create duplicate prevention and bidirectional golden-record sync. Mature and widely deployed. The underlying match algorithms are not published. | ◆ |
| Multidomain breadth | An open entity-type vocabulary with a People/Places/Things business category and per-type matching modes. You can model a supplier or a location. You will not get a packaged supplier-onboarding or sustainability application. | Six packaged data clouds covering product, customer, business partner, supplier, location and sustainability, with industry accelerators behind them. | ◇ |
| Audit evidence | SHA-256 hash chain with Ed25519-signed checkpoints that are themselves chained. Verification returns a three-valued verdict (clean, attested damage, tampered) and names the failure: tampering, insertion, deletion or truncation. Re-tampering an attested-damaged chain un-attests it automatically. Try the verifier. | The MCP launch says AI decisions should be "explainable, auditable, and human-in-the-loop where required," and STEP carries an immutable governance audit trail for data changes. We found no published cryptographic tamper-evidence mechanism for agent or tool actions. | ◆ |
| Agent authorization | Every governed tool call passes a scope gate, a consented-tool allowlist, a declarative authority gate and a mid-session revocation re-check before dispatch, then metering, then a sealed audit row. It fails closed. Cedar decides admin, config, token, role and vault questions, not the dispatch hot path, and we say so. | "Compliance controls and data policies remain intact as AI agents operate within defined parameters." That is the whole public statement. We could not find a per-call decision point, a scope ceiling or an authority model in the announcement. | ◆ |
| Break-glass | Scoped, time-boxed emergency access for agents, admin plus IP-allowlist plus step-up gated, auto-revoking and fully audited. It cannot be quietly deleted from the log. | Not described in their public material. | ◆ |
| GDPR erasure | Crypto-shred: deleting the subject key destroys every ciphertext for that subject at once, cited to ISO/IEC 27040 and GDPR Art. 17. Actor identities in the chain are HMAC-committed, so the audit chain still verifies afterwards. ISO 27560 consent receipts are signed at grant and at withdrawal, and MDM carries a consent-validity substrate per subject and purpose. | STEP has governance workflows, validation rules and an audit trail. What happens to a golden record already syndicated downstream when a subject asks for erasure is not described publicly. Worth asking on the call. | ◆ |
| Tokenization and PII handling | Datasets are tokenized at ingest; agents query tokenized data over MCP; detokenization is a privileged, audited operation. Tokens are deterministic, join-preserving and vault-reversible, so mastering still works across sources. Golden reads mask PII, and a tokenized-at-rest matching field makes the run refuse with a typed error rather than mega-merge. Plus 129 field classes for PII, PHI, financial data and secrets, deterministic and reproducible from a config digest. | Data quality, validation and governance rules. Tokenization is not vocabulary Stibo uses in public material, and we found no built-in PII or PHI classification library. | ◆ |
| MCP and agents | More than 200 MCP tools across Ontology, Auth, Corpus and Lighthouse, with 99 commands on the MDM tool alone. MCP tool tokens carry scope ceilings, delegation is RFC 8693 token exchange with an enforced ceiling, and per-call metering is attributed to the agent. | A real open MCP server, shipped 29 June 2026, exposing semantics, relationships and hierarchies from the STEP semantic data graph. Platform-agnostic, with a Microsoft shopping-agent demo. Their surface is MDM-scoped; ours spans mastering, catalog, classification and identity. | ◈ |
| Deployment | Self-hosted in your own cloud or data center, or a dedicated single-tenant server we operate. Docker images for Auth, Ontology, Corpus and Lighthouse, with a signed deploy manifest Guardian verifies. Ed25519 audit-signing keys can live in your KMS or HSM. HMAC tokenization keys sit in your environment or derive from your machine key today, not in a KMS. | SaaS first, and winning at it: 77% of customers were on SaaS as of June 2026, with SaaS revenue up 17%. On-prem and private deployment options are referenced in their materials, plus an Azure Marketplace listing since 2023 and a native Microsoft Fabric integration. | ◈ |
| Maturity signals | Auth, Guardian and Lighthouse are live in production (Guardian and Lighthouse since April 2026). Entity resolution is tested against real Chicago open-data sets, not only synthetic ones. SOC 2 not yet certified, and we say so. | Founded 1994, foundation-owned, roughly 600 to 840 staff across 18 offices, DKK 1.31B revenue in FY2026, Gartner MQ Leader 2026, Forrester Wave Leader Q2 2025. We cannot match any of that and would be lying if we tried. | ◇ |
| Pricing and time to value | Published model, scoped instant quote, no sales wall. Self-hosted, so there is no mandatory implementation programme. | Quote only, subscription priced by users, volume and modules. Third-party review sites put enterprise MDM implementations in the six to seven figure range, though Stibo publishes no figures. G2 reviewers score STEP's ease of use at 6.9 out of 10, below several category peers. | ◆ |
◆ DataShield leads◇ Stibo Systems leads◈ comparable
Stibo claims are drawn from stibosystems.com and Stibo Systems' own press releases, last checked 13 September 2026. Sources are linked below rather than recalled from memory.
Three things you get here that you won't get from an enterprise MDM suite
Proof that survives an audit
A log that can be quietly edited proves nothing. Ours is a hash chain with signed checkpoints, and the verifier tells you what broke, not just that something did. That is the property EU AI Act Article 12 and HIPAA §164.312(b) reviewers care about. Try it in your browser, no signup.
Authority that can change mid-flight
A steward resigns on a Friday. Their agent is 20 minutes into a 40-minute merge job against your customer golden records. With DataShield the next governed tool call is re-checked against current authority and fails closed. A suite with a nightly sync finds out on Monday. How Auth does it.
Match logic you can open up
Our matching is Fellegi-Sunter with named comparators, EM-trained parameters and five survivorship strategies. You can trial a config, ask it to explain a decision, retrain it, and watch a drift score on the live score bands. Nothing is a black box you file a ticket about. See the ontology.
Where Stibo Systems is genuinely stronger
Start with the obvious. Stibo has been mastering product data since 1994 and the company behind it dates to 1794, which makes our production track record look like a rounding error. They are a Gartner Magic Quadrant Leader for MDM as of April 2026 and a Forrester Wave Leader from Q2 2025. In June 2026 they reported a record year: DKK 1.31 billion in revenue, SaaS revenue up 17%, and 77% of customers already on the SaaS platform. Their product side is a different weight class from ours. PIM, digital assets, supplier onboarding, syndication, and ProductGen AI for generated product content in many languages. If that is your problem, buy Stibo. And their June 2026 MCP server is a serious piece of work, not a press release: an open server that hands agents the semantics, relationships and hierarchies from the STEP graph. They got there before most of the MDM field.
Here is the push-back, and it is narrow on purpose. Read what the MCP announcement actually promises about control. "Compliance controls and data policies remain intact as AI agents operate within defined parameters." We read that release closely and could not find the mechanism underneath it. What decides a given call? What happens the moment you revoke an agent's access, on the call after that? What artefact do you hand an examiner who asks whether the March agent log was altered? Those are answerable questions, and a thirty-year-old governance suite should be able to answer them in public. Until it does, an agent reading mastered customer records is running on trust. We would rather it ran on a scope ceiling, a revocation check, and a signed chain.
Questions worth asking both of us
These are the questions we would ask if we were the ones signing. Put them to every vendor on your list, us included.
Can you cryptographically prove an audit log entry wasn't deleted?
DataShield: yes. Each record commits to the one before it, checkpoints are Ed25519-signed and chained, and verification tells deletion apart from truncation and from tampering. Run it against a sample chain at /verify. Stibo: STEP keeps an audit trail of data changes and the MCP release calls agent decisions "auditable." We found no published tamper-evidence mechanism. Ask them to show one, and ask whether it covers agent tool calls or only record edits.
What happens to a revoked agent mid-session?
DataShield re-checks authority on every governed tool call, so revocation lands on the very next call and the context drops to anonymous. Stibo's MCP server says agents operate "within defined parameters." We could not find a revocation model in their public material. Ask how long a compromised agent keeps reading your customer golden records after you pull its access.
How does GDPR erasure interact with the audit trail?
DataShield crypto-shreds the subject key, which destroys every ciphertext for that subject at once, and issues a signed ISO 27560 consent receipt. Actor identities in the chain are HMAC-committed, so the evidence still verifies once the subject is gone. Stibo has governance workflows and validation rules. What happens to a golden record already syndicated to downstream systems is the harder question. Ask for the mechanism, not the workflow.
Is DataShield a Stibo alternative for product data and PIM?
No. We have no PIM, no digital asset management, no syndication and no GDSN. If the buying trigger is a product catalogue, Stibo or one of its PIM rivals is the right call and we will tell you that on the first call. Where we compete is customer and party mastering, and specifically when AI agents are going to read those records.
Stibo shipped an MCP server too. What's different?
Theirs, from June 2026, hands an agent the STEP semantic graph: entities, relationships, hierarchies. It is a good design and it beat most of the MDM field to market. Ours is where the governed data is queried, so the tool token carries a scope ceiling, the call is authorized and metered before dispatch, PII comes back tokenized unless detokenization is explicitly allowed, and the decision is sealed into a chain. Their surface is MDM-scoped. Ours spans mastering, catalog, classification and identity in one stack. Score it even on the fact of shipping, and ask each of us what the server refuses to do.
Does DataShield have SOC 2?
Not yet, and we will not imply otherwise. Auth is live with a public threat model and a verifier anyone can run. Guardian and Lighthouse have been in production since April 2026. Design-partner terms include source escrow, so a small vendor is not a single point of failure. Details on the security page.
- Stibo Systems launched an open MCP server on 29 June 2026, positioning "MDM as the active intelligence layer for the agentic enterprise" and stating "compliance controls and data policies remain intact as AI agents operate within defined parameters." — PR Newswire, 29 Jun 2026
- Record fiscal year: DKK 1.31 billion revenue, up 6.0%; SaaS revenue up 17.0%; 18.1% EBITDA margin; 77% of customers on SaaS; growth in customer MDM led by financial services and pharma. — PR Newswire, 25 Jun 2026
- Named a Leader in the 2026 Gartner Magic Quadrant for Master Data Management Solutions. — PR Newswire, 9 Apr 2026
- MDM SmartSync for Salesforce: search-before-create duplicate prevention, real-time golden-record sync and bidirectional CRM integration for customer data. — PR Newswire, 25 Sep 2025
- ProductGen AI: generative product content creation, governance and localization with human-in-the-loop approval before publishing. — PR Newswire, 30 Sep 2025
- Named a Leader in The Forrester Wave for Master Data Management, Q2 2025. — Stibo Systems press release, Jun 2025
- Current hero positioning: "Trustworthy Intelligence. Your AI is only as good as what you feed it," with six data clouds spanning product, customer, business partner, supplier, location and sustainability. — stibosystems.com, 13 Sep 2026
Other head-to-heads
DataShield vs Reltio
Cloud-native customer MDM, versus authority at the tool call.
MDMDataShield vs Informatica MDM
The incumbent suite, and the evidence layer it doesn't ship.
MDMDataShield vs Profisee
Mid-market multidomain MDM, versus agent-first mastering.
AllEvery comparison
One honest scorecard per vendor.
See both mechanisms run in your browser: break a live audit chain, revoke an agent mid-session, then ask your MDM vendor what happens on the next call. Demo Center access is free with a work email.
Get free Demo Center accessYou've seen the proof
Ready for a number? Scope your deployment and we'll price it against your own economics.
Get your quote →