CleanDims

CleanDims roadmap.

What works today, what we are building next, and what comes after. No dates: items move when they are ready.

Now

In use on English data

With early clients, through our partner InclinedPlane Technologies.

Canonical dimensions

Stable IDs, hierarchy levels and aliases for places, industries and vendors.

Confidence scores and review

Ambiguous values go to a person. Decisions become aliases.

Hierarchy-aware joins

Finer levels roll up so sources meet at the right one.

Pricing on effort

Half the estimated manual effort, per join.

Next

Spanish, and a production release

The same canonical layer, with labels in more than one language.

Production release

The platform hardened for paying customers.

Spanish–English joins

A Spanish source and an English source map to the same ID.

Chilean open data

Territory and economic activity first: comunas and regions, SII activity codes against ISIC, SACH tariff codes against HS.

Bundles for teams that join often

Annual bundles of joins and maintenance subscriptions, now being tested.

Later

More languages, more open data

Each new language reuses the dimensions already built.

Further languages

New labels, aliases and crosswalks on the existing IDs.

Open canonical dimensions

Spanish–English dimensions for public data, published free.

SOC 2 Type II

For enterprise procurement. Private data can already stay in your own cloud.

Next, in detail

One ID, labels in every language.

A canonical value is not tied to one language. It carries a label and aliases in each, so the join does not care which language a source was written in.

In development · territory example
idCL-RM
levelregión
esRegión Metropolitana de Santiago
enSantiago Metropolitan Region
aliasesRM, Región Metropolitana, Metropolitana de Santiago

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.