Provisa / Fits your stack
It feeds the catalog you already bought.
Catalog metadata goes stale the moment it falls out of sync with the systems it describes. Someone renames a column; the catalog still says it means something else. Nobody notices until an agent or a report uses it wrong. The model that governs queries here is already correct, because nothing runs otherwise. Publishing from it keeps the catalog in step without anyone maintaining it separately.
Publishes to your catalog
Catalog assets maintained by hand drift from the systems they describe. A table moves; the lineage breaks. A column is renamed; the classification no longer applies. Keeping multiple catalog destinations in sync is a recurring job nobody hired for.
One registration publishes to eight destinations: OpenMetadata,
DataHub, Collibra, Atlan,
Apache Atlas, OpenLineage, BigQuery
Dataplex and Snowflake Horizon. Tables, columns,
tags, classifications, and lineage flow out as first-class catalog assets, from
the admin console or from provisa metadata export on a cron.
The metadata comes from the model that runs and governs your queries, which already has to be correct. Nobody maintains a second description by hand, so there is nothing to drift.
Lineage that survives re-platforming
Assets are stitched on business identity, not physical location. Move a table from Oracle to Postgres and its catalog entry, lineage, and history follow the business entity, instead of starting over as a new asset with no past.
Data quality, without a second engine
Point Soda at a governed table and register the contract as a source. You get scan history, a quality scorecard, and lineage from each failing check back to the table it guards. Scans run when the table changes, not on a guessed schedule. Provisa ships no data-quality engine and doesn't ask you to retire yours.
Every value has an address
A governed value is addressable as
provisa://<org>/<domain>/tables/<table>/pk=<id>/<column>
and resolves over REST or MCP, optionally as of a point in time.
Exported documents, lineage nodes, audit records, and AI-agent citations carry
links that resolve back to the live governed value, under the same policy as any
other read.
Only semantic addresses dereference. Physical URIs are refused, so a citation never leaks a location. That matters most when an agent writes the citation and nobody reviews its output line by line.