Veracy

It authors · Data Catalog

A data catalog that documents itself

Documented as it happens

A catalog is only useful when it is complete and current, and that is exactly what hand-maintained catalogs never are. In Veracy the catalog is not a separate product to fill in; it is a view of what the contract already says and what the engine actually built.

Today

Teams buy a catalog, run a crawler, and then ask everyone to add descriptions and owners by hand. Six months later half the entries are stale and the other half are empty, and people go back to asking in chat who owns a table.

What Veracy does

  1. 01

    Every asset the engine builds is registered as it is built: tables, columns, contracts, quality rules, metrics, and who signed them.

  2. 02

    Business vocabulary is seeded from open standards (SKOS, GS1, FIBO, PROV-O) and aligned to the words your organisation already uses.

  3. 03

    Lineage and history are recorded with each change, so an entry shows not only what a thing is but where it came from and what it became.

What you get

  • Nothing to fill in

    descriptions, owners and definitions come from the contract and the build, not from a campaign to get people to type.

  • Definitions people recognise

    vocabulary starts from industry standards, then adapts to your own terms.

  • Works with the catalog you own

    the same facts can be published to an existing enterprise catalog; Veracy is the source, not a silo.

Questions

Do I need to replace my existing catalog?
No. Veracy is the source of truth for what it builds and can feed an existing enterprise catalog. If you have no catalog, Veracy's own is complete on day one because it is generated, not crawled and annotated.
Where do the business definitions come from?
From open vocabularies — SKOS for concepts, GS1 and FIBO for industry terms, PROV-O for provenance — aligned to your own glossary during contract review.
How does the catalog stay current?
It cannot go stale on its own: every entry is tied to a signed contract version and to the artefacts the engine built from it. When either changes, the catalog reflects it in the same operation.

Stop building your data platform. Just sign what matters.

All capabilities