Veracy

It serves · Data Governance

Data governance that is enforced, not just documented

Declare once, enforced everywhere

Governance programmes produce policies; engines produce access. The gap between the two is where most data breaches and audit findings live. Veracy closes it by making the policy part of the contract and the contract the thing the engine runs.

Today

Policies live in documents and tickets. Each tool implements its own version of them, differently, and the newest consumer — an AI agent — often gets a service account with everything. Proving who could see what, and when, is a forensic exercise.

What Veracy does

  1. 01

    Access is declared once, in the contract: who may see which rows and columns, under which purpose, with what masking.

  2. 02

    The engine enforces it natively — inside the query path, row by row — for every consumer. There is no way around it through a different tool, because every tool goes through the engine.

  3. 03

    Every access is recorded. Unknown principals get nothing by default (fail-closed), and the audit trail is a query, not an investigation.

What you get

  • One policy, every consumer

    dashboards, notebooks, exports and AI agents all obey the same declaration.

  • Fail-closed

    nothing is visible until it is explicitly allowed, which is what GDPR, HIPAA and most auditors expect.

  • Proof on demand

    who accessed what, under which policy version, is on record and verifiable.

Questions

Where are access rules defined?
In the data contract, next to the schema and the quality rules, so they are versioned and signed with the rest. The engine reads that declaration directly; there is no separate policy engine to keep in sync.
Does this apply to AI agents too?
Yes, and that is the point. An agent asking a question goes through the same governed path as a person, with the same row-level enforcement, and its answers carry the same receipt.
What does "fail-closed" mean in practice?
If a principal, a purpose or a column is not explicitly covered by a policy, access is denied and the denial is logged. Nothing is exposed by default while someone gets round to writing a rule.

Stop building your data platform. Just sign what matters.

All capabilities