It serves · Semantic Layer
A semantic layer with one definition of every metric
One definition of every metric
When three dashboards show three revenues, the problem is not the dashboards; it is that "revenue" was defined three times. A semantic layer defines it once. Veracy generates that layer from the contract and the warehouse it built, so the definition and the data cannot disagree.
Today
Metric logic is copied into every BI tool, spreadsheet and notebook, and each copy drifts. Meetings turn into reconciliation sessions. The AI agent added last quarter has yet another copy.
What Veracy does
- 01
Metrics, dimensions and hierarchies are derived from the signed contract and the serving layer, using the vocabulary the catalog aligned.
- 02
Each definition is portable and governed: it is versioned, owned and served through one path, whatever tool is asking.
- 03
KPIs and scorecards are built from those definitions, so a figure on a scorecard traces to the same metric an agent would compute.
What you get
The same number in every tool
because there is only one definition and one path to compute it.
Definitions people own
each metric has an owner and a version, like the contract it came from.
Agent-ready
AI agents consume the same governed definitions, so their answers are consistent with the dashboards.
Questions
- Which tools can consume the semantic layer?
- Any consumer that can ask the engine: BI tools, spreadsheets, notebooks, applications and AI agents. They all receive the same definition and the same number, with a receipt attached.
- Is the metric logic locked into Veracy?
- No. Definitions are declarative and portable; they are yours, in open form, and can be exported. The exit door is part of the product.
- Who defines a metric?
- Veracy proposes metrics from the contract and the model; the business owner names, refines and signs them. From then on the definition is governed like the contract that produced it.
In the same job · it serves
Stop building your data platform. Just sign what matters.