Veracy

It authors · Data Contracts

Data contracts, written for you and signed by you

Authored by the machine, signed by you

A data contract is the agreement between the people who produce data and the people who depend on it: what the data looks like, what quality it promises, how fast it arrives and who owns it. Most teams know they need them. Almost none have the time to write them by hand, table by table.

Today

Contracts are usually a template in a wiki that nobody keeps current. The schema changes, the promise does not, and the first sign of trouble is a broken dashboard on a Monday morning. Where contracts do exist they live apart from the pipelines they describe, so nothing enforces them.

What Veracy does

  1. 01

    Connect a source (a read replica is enough). Veracy profiles every table and column: types, keys, nulls, ranges, relationships.

  2. 02

    It drafts the contract in the open ODCS standard — schema, quality expectations, freshness and ownership — and puts a filled page in front of your team.

  3. 03

    You refine and sign. From that signature the warehouse, the quality rules, the catalog entry and the metric definitions are generated and kept in step.

What you get

  • One signed source of truth

    the contract is the input everything else is built from, not documentation written after the fact.

  • Breach monitoring

    when a producer breaks the promise (a column disappears, freshness slips), it is caught at the contract, not in a report.

  • Versioning without fear

    a contract can evolve; history is kept and downstream consumers see exactly what changed and when.

Questions

What is a data contract?
A formal, machine-readable agreement about a dataset: its schema, quality rules, service levels and ownership. Veracy uses the Open Data Contract Standard (ODCS) so contracts are portable and not tied to any vendor.
Do I still have to write the contract?
No. Veracy drafts it from the source itself. Your job is to review what it found, adjust the business intent (names, rules, thresholds) and sign. Signing is the only human step that is required.
What happens when the source schema changes?
The change is detected against the signed contract. Compatible changes heal themselves and are versioned; a change of meaning is refused and escalated to a person, so nothing downstream silently drifts.

Stop building your data platform. Just sign what matters.

All capabilities