Train and run Zingg privately on your own data in Fabric’s familiar notebook interface. Resolved entities with a persistent ZINGG_ID feed LLM applications, customer data platforms, enterprise knowledge graphs and the rest of your downstream applications.
Runs on Fabric’s own Spark environment.Train and run Zingg from Fabric notebooks with the Zingg Python API. No new tools for your team to learn.
Zingg runs on Fabric’s Spark environment, so your records stay in your workspace.
Resolved entities feed LLM applications, customer data platforms and enterprise knowledge graphs directly.
A set of Fabric notebooks on the Zingg Python API that take you from setup to labeling training pairs, model documentation, and training and matching, on Parquet, Delta or other file formats.
Fabric notebooksThe Enterprise Python API with every supported source and sink, incremental flow, persistent ZINGG_IDs, explainability and model diff, plus support.
Talk to usA persistent, global identifier for every resolved entity, so every team and agent joins on the same key.
Learn moreMatch only new, updated and deleted records against the clusters already resolved. IDs persist between runs.
Learn moreSee the evidence behind every match, so you can explain results to business users.
Learn moreConfidently add new signals, update configuration and deploy models in production.
Learn moreYes. Zingg is a Spark-based application, so it runs on Fabric’s Spark environment from Fabric notebooks.
No. Zingg trains and runs in your workspace, on your own data.
Zingg Community reads Parquet, Delta or other file formats. Zingg Enterprise supports every Zingg source and sink on Fabric.
Import the Zingg Community notebooks into Fabric and run them in order, or follow the step-by-step guide.
Use resolved entities and their ZINGG_IDs in LLM applications, customer data platforms, enterprise knowledge graphs and reporting.
Start with the open source notebooks, or talk to us about Zingg Enterprise on Microsoft Fabric.