Getting Started

bensevern.dev is the matching funnel between your SaaS sources (HubSpot, Salesforce, Cvent, Bizzabo, Postgres) and your warehouse / cloud destinations. Match, cluster, review, push.

bensevern.dev is the matching funnel that sits between your SaaS sources and your warehouse. We pull records in, match and cluster them, surface the unauto-merged clusters in a review queue, and push the golden records back out to a destination of your choice. We don't host your data — we collect, filter, and hand back.

The pipeline

StageWhat happensSurface
01 · ingestPull records from CRM / billing / events / warehouseSources (22 connectors live)
02 · autoconfigPropose match rules + survivorship + scorer weights from your schemaWorkbench notebook (one click)
03 · match + clustergoldenmatch 1.18 deduplicates and groups recordsWorkbench notebook
04 · reviewAmbiguous clusters wait for a human label; decisions feed the scorerReview queue
05 · pushWrite golden records to warehouse table or cloud file dropDestinations (7 targets)

Why funnel, not platform

Most MDM tools want to become your source of truth: they sit in the middle, hold the records, and you query them. That works at Reltio scale; it does not work for a RevOps team that already has HubSpot + Salesforce + Snowflake and just needs the duplicates cleaned up.

bensevern.dev runs the matching, stores enough state to make the review queue work (clusters + labels + lineage), and pushes the results back to systems you already own. If you want to walk away tomorrow, your warehouse table is still there.

The Suite engine

The matching engine itself is five MIT-licensed Python packages. You can self-host them if you'd rather skip the SaaS:

ToolPurpose
goldenmatchProbabilistic record linkage + deduplication (the core)
goldenpipeData transformation pipelines that wrap goldenmatch
goldencheckData-quality profiling and validation
goldenflowWorkflow orchestration
infermapAutomatic schema mapping between sources

goldensuite-mcp (on PyPI — pip install goldensuite-mcp) wraps the whole Suite as a single MCP server, so any MCP client — your own agent, an IDE, Claude — can call matching directly. Matching as middleware, not just a SaaS destination.

Next Steps

Was this page helpful?
Edit this page on GitHub