AlloyMDM
Job & App

Lite first, full when you need it.

Both run in your workspace and use the same Unity Catalog tables. The App is the Job plus a workbench for people.

AlloyMDM Job (lite) Built, not yet run on a workspaceAlloyMDM App (full) Designed, not built
What it isA task you add to any Databricks jobThe Job plus a steward workbench
SetupA YAML file and a job taskSetup wizard in the app
Review pairsWrite confirm / reject rows to the decisions table with SQLSide-by-side evidence and one-click decisions
Change rulesEdit YAML or the rules table, run a previewRules editor with preview
Access controlUnity Catalog permissions on the tablesUnity Catalog permissions through user authorization; no roles defined in AlloyMDM
Ongoing costCompute for each run onlyRun compute plus an always-on app and a SQL warehouse
Best forData teams that want golden records in a pipelineTeams with stewards reviewing matches every day

Fits where you already work

  • Any job: run it after your gold tables refresh, in a Databricks Workflow or any scheduler that can run a Databricks task.
  • Your own schema: output goes to a separate schema, so your gold tables are never modified.
  • Several domains: accounts ship first; templates exist for customer, person, product, vendor and location.

Known limits today

  • One engine on one machine. It refuses to run above a configurable record cap (500,000 by default) rather than run for hours, and it slows down on very crowded data.
  • Full refresh on each run, not incremental.
  • Decisions and rule changes take effect at the next run.
  • Larger volumes will need a parallel engine, which is possible but not built.