Product registry & catalog
A data product is governed data with a name, an owner, and a certification status you can check. The registry holds every product your teams publish: what it contains, who stands behind it, and whether the evidence behind it is current. When an examiner asks who owns the data feeding a report, you answer from the registry entry and the sealed history behind it.
Every product carries a named owner, a steward, and a stated purpose, tied to the same governed knowledge graph the rest of the platform runs on.
Certification status is derived from live evidence, including contract health, lineage, and data quality, with no manual override to make it look better than it is.
Lineage runs from each product back through the systems that feed it, federated through the connector library without copying data out of your environment.
Records imported from an existing catalog land as claims, and they stay marked as claims until checks against evidence verify them.
Versioning and deprecation live in the registry, so consumers see when a product is retiring and what replaces it.
Filters cover domain, certification state, and regulatory scope, so you can pull every product carrying BCBS 239 CDEs in one view.
Federate
Connectors read metadata from your source systems and warehouses, and nothing copies out of your environment.
Publish
An owner names the product, binds it to governed datasets, and declares what it is for.
Derive
Certification computes from the product's evidence and updates itself when the evidence changes.
Seal
Every change to the entry, including ownership, status, and contents, lands on the hash-chained ledger.
“Who owns this product, and is that ownership current?”
Every registry entry names an owner and a steward, and every ownership change lands on the hash-chained ledger. You read the current owner from the entry and verify the history behind it in the sealed record.
“Which products feed our regulatory reports, and are they certified?”
Filters cover regulatory scope and certification state, so you can pull every product carrying BCBS 239 CDEs in one view. Certification is derived from live evidence, so the status you see reflects checks that are actually passing.
“Is this catalog entry verified, or is it still an unverified record from our catalog migration?”
Imported records land as claims and stay marked as claims until checks against evidence verify them. The registry always shows you which entries are verified and which are still waiting on evidence.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.