Join any datasets, even without common keys.
Sales and census population. Suppliers and company registries. One department’s figures and another’s. They rarely share an ID. CleanDims builds the missing key from the text columns they do share: places, industries, vendors.
New York Countycounty_population.county_nameCounty, rolls up to the state
NYSTORE_SALES.REGIONAlias of the state
New YorkSTORE_SALES.REGIONState or city? Sent to review
New York
- id
- PLC-0036
- level
- state
- parent
- PLC-0001
- aliases
- NY, N.Y., New York State
Store sales by state and population by county now join at state level.
The problem
The only link is a text column, and it breaks in three ways.
When there is no shared ID, analysts rebuild lookup tables by hand for every project. The work is slow, error-prone and never reused.
Spelling
One vendor, three strings. An exact-match join drops two of them.
Hierarchy
“New York” is a state and a city. One source reports by state, another by county, and nothing says which.
Vocabulary
One industry, named three ways by three systems.
How it works
From connected sources to one canonical ID.
CleanDims reads the schemas and distinct values of your sources, never whole rows. Every step a machine scores, a person approves, and each decision is kept and reused.
The dashed boxes are the two human gates: a mapping takes effect only when someone approves it, and a grouping below the threshold waits for a reviewer. Everything else runs on its own.
The product
Connect sources, approve the mappings, download the IDs.
The demo is the product with a sample workspace loaded: your own databases, open datasets attached, one dimension already published and two waiting for review.
Open data
Public datasets, already cleaned.
CleanDims maps public datasets to the same canonical dimensions your data uses. Two examples from the open data catalogue:
Federal contract awards
Contract awards to suppliers, with place of performance and industry code. Recipient names are typed by contracting offices and vary widely.
VEN-0080 DellVEN-0047 Oracle DatabaseVEN-0033 Amazon Web ServicesVEN-0042 SalesforceBusiness establishments by county and industry
Establishments and employees by county and industry. County and industry names are written several ways across state submissions, often with codes attached.
PLC-0055 New York CountyPLC-0084 Cook CountyPLC-0062 Los Angeles CountyPLC-0087 Fulton CountyWhere it fits
CleanDims matches dimension values. Other tools match records or fields.
A text join needs the values inside a column to agree. That is a different job from deduplicating customers or wiring one system’s fields to another’s.
| Approach | What it matches | What that means for a join |
|---|---|---|
| Entity resolution | Records about the same customer or company, in data you hold | Links rows, but gives two datasets no shared dimension |
| Master data management | Internal master data | Costly, and takes months to deploy |
| Integration mapping | Fields between systems | Does not touch the values inside those fields |
| SQL, scripts and LLM prompts | Whatever this project needs | Restarts on every project, with no shared canonical layer |
| CleanDims | Dimension values across open and internal datasets | One canonical layer with hierarchy levels, reused by every later join |
Pricing
Half the effort a join would take by hand.
We estimate the hours an analyst team would spend on the join and charge half of that. Joins on dimensions you have already mapped take less work, so they cost less.
Open data, mapped once
Public datasets are mapped ahead of time. You see which ones join with yours, and at which level.
Your own data
Upload files or connect systems. Your columns map to the same dimensions.
A person for the hard cases
Every mapping carries a confidence score. Uncertain ones wait for review, and each decision is reused.
Have two datasets that should join and don’t?
Tell us what they are. We will tell you whether they join, at which level, and what the join would cost.