Data Unification
Every source. One record. Yours to expose.
Meld harvests data from the tools you already run, maps it into a schema you define, and converges many sources into one golden record around the key you choose. Every value shows which source it came from. Records that fail to align are held for review, and records whose sources vanish follow lifecycle rules. Browse them with saved filter views, then expose the result as a page, an API and an AI tool under platform permissions.
Most master-data tools serve one domain and stop at the record. Meld converges data from the tools you run into golden records on the key you choose, shows which source supplied every field, holds conflicts for review instead of merging silently, and exposes the result to people and AI agents as a page, an API, or a tool under one field-level policy. Connect 600+ sources through the Airbyte connector specification.
- Connect to 600+ sources through the Airbyte connector specification, plus a first-party source for your own device fleet
- Define your own data classes and fields, or describe them and review an AI-drafted proposal before it applies
- Converge many sources into one golden record, with per-field provenance, conditional match rules, conflict resolution and manual merge
- Quarantine records that fail to align; lifecycle rules retire records whose sources vanish, with review and a brake
- Filter, save and share record views, then expose records to people and AI under platform permissions
What you get
What Meld gives your team.
Connect through the Airbyte spec
Harvest from sources you can connect through the Airbyte connector specification, authored in a designer or imported as a manifest, or start from platform-published recipes with version pins.
Your fleet as a source
A first-party source brings in your own device and IoT fleet data in one click, with no credentials to configure.
Schema you define
Model categories, fields, nested lists and locations in a versioned schema, or describe it and review an AI-drafted proposal.
Convergence with provenance
Match on a key or several fields in priority order, with different rules for different kinds of rows. Resolve conflicts by survivorship, merge by hand, and see every field's source.
Quarantine and record lifecycle
Records that fail to align are held with a reason. Lifecycle rules mark records inactive or send them to the recycle bin when sources go missing, with review and a safety brake.
Expose to people and AI
Browse with a full filter bar and saved views, open one list across every record, and publish a governed page, API and AI tool with field-level access, masking and encryption.
How it works
- 1
Connect a source
Pick a source reachable through the Airbyte connector specification, import a manifest, or switch on the first-party fleet source in one click. Enable the streams you need.
- 2
Define your schema
Model categories, fields and nested lists, or describe the data class and review an AI-drafted proposal. It applies only after you approve it.
- 3
Converge on a key
Match on a key or on several fields in priority order, and pick survivorship rules for conflicts. Records that fail to align are quarantined with a reason.
- 4
Expose to people and AI
Publish a converged record set once as a governed page, API and AI tool. Field-level grants apply to people and agents alike.
Ask AI about Meld
Every Meld page has an Ask AI button. It opens a chat that already has the page, its rows, and your selection. Try asking:
- List the transforms on this page by kind, with the number of versions each has.
- Which records in this view are missing a value in the fields shown?
- Run my saved cleanup function on the records I ticked and show me the result.
How teams use it
- Build one trusted device record from several management tools.
- Reconcile users or assets across systems and see which source supplied each value.
- Give AI agents governed access to converged records without exporting data.