Tool list · Entity resolution

    15 Best Entity Resolution Tools in 2026

    Discover the 15 best open-source and managed entity resolution tools in 2026 to find records about the same customer, supplier or product and link them with one ID (identity resolution, when the entities are people), with ML and rule-based matching, real-time APIs, persistent entity IDs, and explainable matches.

    By Ari Bajo - data engineer turned writer.

    Updated on November 19, 2026

    Tools list

    Warehouse-native entity resolution

    Entity resolution that runs as jobs inside your own data platform, so records are matched where they live and IDs are written back to your tables: Zingg on Spark or as a Snowflake Native App (paid editions), and the Splink library on Spark or DuckDB.

    Zingg

    Warehouse-native entity resolution that matches customer, supplier and product records with ML in your own data platform (Databricks, Fabric, AWS, GCP or Snowflake); open source, with paid editions for persistent IDs.

    OSSWarehouse-nativeSpark-nativeentity resolution
    My Opinion

    Best for data engineers who want ML entity resolution as a pipeline step inside their own data platform.

    Entity resolution engines

    Entity resolution engines that load records into their own store or service: an SDK with its own repository, a managed AWS service, or a real-time API that resolves records as they arrive.

    Senzing

    Entity resolution SDK embedded in your application that resolves each record against existing entities in real time with principle-based rules and explains why records matched.

    My Opinion

    Best for engineering teams that need real-time entity resolution inside their own infrastructure, including air-gapped sites.

    AWS Entity Resolution

    Managed entity resolution on AWS that matches S3 records with rule-based, ML or data provider workflows, assigns a match ID, and runs incremental or near real-time rule-based matching.

    My Opinion

    Best for AWS teams that want pay-per-record entity resolution on S3 data.

    Tilores

    Real-time entity resolution engine that matches records as they arrive with explicit rules and ML scoring, keeps an auditable entity graph, and serves entities through GraphQL in about 150 ms.

    My Opinion

    Best for operational entity resolution where every link must be explainable.

    Quantexa

    Decision intelligence platform whose ML entity resolution resolves entities in batch or at request time and feeds network graphs for financial crime and risk.

    My Opinion

    Best for banks that want entity resolution tied to graph analytics and investigations.

    MDM hubs with built-in matching

    MDM hubs whose matching is a product of its own: they resolve entities and then build golden records that data stewards review.

    Tamr

    MDM platform built on ML entity resolution, where models score record pairs with labeled confidence and low-confidence pairs go to curator queues.

    entity resolutionstewardshiphierarchy management
    My Opinion

    Best for enterprises that want ML entity resolution with steward review inside an MDM platform.

    Reltio by SAP

    SaaS MDM whose entity resolution combines pretrained LLM matching models with fuzzy and exact match rules, resolving records in real time with persistent Reltio IDs.

    My Opinion

    Best for teams that need real-time entity resolution feeding operational golden records.

    LakeFusion

    Databricks-native MDM whose entity resolution runs deterministic rules, then a Random Forest trained on steward decisions, then an LLM for uncertain pairs, with SHAP explanations.

    Databricks-nativeentity resolutionstewardshipRDMhierarchy managementPIM
    My Opinion

    Best for Databricks teams that want explainable entity resolution inside Unity Catalog.

    Verato

    Healthcare MDM whose referential matching compares patient and provider records with a reference database of 300M+ identities instead of only with each other.

    entity resolutionstewardshiphierarchy management
    My Opinion

    Best for healthcare teams resolving patient and member identities across systems.

    IBM Match 360

    MDM service whose matching engine combines probabilistic, deterministic and rule-based matching with ML-guided weights and thresholds.

    My Opinion

    Best for IBM Cloud Pak for Data users that need entity resolution inside an MDM service.

    Customer data platforms with identity resolution

    Customer data platforms that resolve customer identities for marketing: deterministic rules on emails and IDs, sometimes ML, for people and households first. Listed for comparison; they have no row in the MDM feature matrix.

    Hightouch Identity Resolution

    Identity resolution that runs in your own warehouse: exact matches on emails, phones and device IDs, then AI probabilistic matching, with profiles for people, households, accounts or any custom entity.

    Warehouse-nativeentity resolution
    My Opinion

    Best for marketing and data teams that want customer profiles built in the warehouse and synced to business tools.

    RudderStack Profiles

    Identity stitching in your own data cloud: an id_stitcher model links identifiers seen together in your data into an identity graph with one canonical ID per user, household, account or device.

    Warehouse-nativeentity resolution
    My Opinion

    Best for teams already collecting events with RudderStack that need deterministic identity stitching, not fuzzy matching.

    Amperity

    CDP whose Stitch identity resolution uses machine learning to match customer records from POS, ecommerce, loyalty and CRM systems into profiles with a unique ID, after the data is ingested into Amperity.

    My Opinion

    Best for consumer brands that want ML identity resolution and customer activation from one vendor.

    Twilio Segment Unify

    Real-time identity graph that merges each customer's web, mobile, server and partner events into one profile with a persistent ID, using ID rules on cookies, devices, emails and external IDs.

    My Opinion

    Best for teams already sending events through Segment, on the Business plan.

    Evaluating data tools in 2026?

    I curate the most comprehensive lists of data tools, up-to-date comparison tables, and actionable market guides for data teams. More useful than a Gartner report. More reliable than asking AI. Next up: Data FinOps.

    By Ari Bajo - data engineer turned writer.

    Compare master data management tools

    The comparison tables behind this list.

    How I check every fact

    Checked against vendor docs

    I check each feature, integration and price against the vendor's docs, pricing page or GitHub repository, and link the fact to that source.

    Open to vendor corrections

    Vendors and users can send corrections. I verify them against the docs before changing anything, and every page shows when it was last updated.

    Spot a mistake? Send a correction →

    Frequently Asked Questions

    What is an entity resolution tool?
    An entity resolution tool finds the records that describe the same real-world entity — a customer, household, supplier, product or location — across or within data sources, and links them under one ID. It compares candidate pairs with rules, a probabilistic model or machine learning, and groups matches into clusters. When the entities are people, the same job is often called identity resolution. Entity resolution is the matching step of master data management; a full MDM tool also builds golden records, lets stewards review matches, and publishes the result. Read more on my master data management tools list.
    How do I choose an entity resolution tool?
    Start with where it runs: in your own data platform (Zingg, Splink, LakeFusion), or in the tool's own store after you load the records (Senzing, Tilores, Tamr, Reltio, Amperity). Then how it learns. Zingg trains an ML model from 40 to 50 labeled pairs and runs inside Databricks, Fabric, AWS or GCP; Splink estimates a probabilistic model without labels on DuckDB or Spark. Senzing is an SDK you embed in your own application, AWS Entity Resolution is a managed service on S3 priced per record, and Tilores matches records in real time as they arrive. Then check whether you need a persistent entity ID that survives re-runs (paid Zingg editions, Senzing, AWS, Tilores, Tamr, Reltio) and whether you need a full MDM hub with golden records and steward review on top (Tamr, Reltio, LakeFusion, Verato).
    What are the best open-source entity resolution tools?
    Zingg (AGPL-3.0) and Splink (MIT) are the two open-source entity resolution tools in this list. Zingg learns from labeled pairs and runs on Spark in your data platform, with paid editions for persistent IDs and incremental runs; Splink is a Python library with no paid edition. Smaller libraries such as dedupe and Python Record Linkage Toolkit exist but are not listed.
    What is the difference between entity resolution and identity resolution?
    Identity resolution is entity resolution for people: it links one person's records, emails, phone numbers, accounts and device IDs into a single profile. Marketing tools and customer data platforms use the term for their customer identity graphs, often with deterministic rules on emails and IDs. Entity resolution is the wider term: the same matching also works for households, companies, suppliers, products and locations. Every tool in this list can match customer records; most also match companies, suppliers or products, while Verato focuses on healthcare identities (patients, members, providers).
    Should I build entity resolution myself?
    Only when matching is simple, such as exact keys on clean IDs. Otherwise the hard part is blocking: comparing every pair of a million records means about 500 billion comparisons, so you must choose which pairs to compare, and retune that choice as the data changes. Open-source libraries remove most of that work while keeping records in your platform: Zingg learns its blocking from the pairs you label, and Splink asks you to write blocking rules but estimates the match model for you. Buy an engine or MDM hub when you need real-time resolution, persistent IDs across runs, or steward review.
    Can a customer data platform do entity resolution?
    For customer records, yes. Hightouch and RudderStack Profiles resolve identities inside your own warehouse, Twilio Segment Unify merges the events sent to Segment into profiles in real time, and Amperity matches records with machine learning after ingesting them. CDPs are built around customer profiles for marketing, and RudderStack Profiles stitches identifiers that appear together rather than fuzzy-matching names and addresses. For suppliers, products or companies with messy names, or when matches need review, use an entity resolution tool or an MDM hub.
    What is the difference between entity resolution and deduplication?
    Deduplication removes duplicate rows inside one table. Entity resolution links records across many sources that may never share a key, keeps them all, and gives the group one entity ID, so you can build a customer 360 view or a golden record without losing the source records.
    Why create yet another tools list?
    Entity resolution lists either cover only open-source libraries or only enterprise MDM hubs. This list puts both side by side, with the customer data platforms that resolve identities for marketing, and each card says how the tool matches records (rules, probabilistic, ML or referential), with a link to the vendor page I read.
    How can I edit this tools list?
    If you think a tool belongs here or you want to suggest an edit, I would love to hear from you. You can fill out the feedback form or DM on LinkedIn.