Business glossary & metrics
Find shared definitions for terms such as active customer and net revenue. See the accountable owner, calculation and source behind each metric before using it in a report or business review.
The context plane
The organizational Context Lake.
Catalog your data, services and infrastructure alongside their owners, business terms and policies. Follow the relationships from a customer-facing API to its deployment, source data and business impact.
01
checkout-api service02
├─ owned_by commerce-platform03
├─ built_from repository/checkout04
├─ runs_on k8s/production/checkout05
├─ reads_from table/orders06
└─ governed_by policy/customer-data07
08
business term completed_order → KPI revenueSTATUSREADYREGIONME-CENTRAL
VegaGraph / role in the platform
A service catalog tells you who owns checkout. A data catalog tells you what is in the orders table. VegaGraph connects both to deployments, infrastructure, business definitions and policies, so teams and agents can investigate the whole dependency chain.
Capabilities
What you can build with VegaGraph
Business impact & lineage
Explore how customers, processes and KPIs depend on data and services. Trace a proposed change to affected dashboards, business metrics and teams before setting priorities.
Business policies & governance
Record business rules, data classifications and approval requirements. Link policies to the data, services and processes they apply to, with review history and supporting records.
Ownership & accountability
Record technical owners, business owners and responsible teams across datasets, services and KPIs. Find who to involve when a change crosses team boundaries.
Data catalog
Find datasets, columns and dashboards with their owners, definitions and lineage. Check where data comes from before using it.
Data quality monitoring
Track quality check results and data contracts alongside each dataset. Trace failed checks to affected pipelines and the teams responsible.
Service & API catalog
Give developers a directory of services, APIs and repositories with owners, lifecycle status and dependencies. Trace a service to its builds and deployments.
Infrastructure inventory
Map clusters, Kubernetes workloads, queues and environments to the services they run. Inspect runtime dependencies and differences between staging and production.
Operational context
Connect incidents, SLOs, runbooks and observability records to affected services. Find the responsible team and review recent deployments during an investigation.
Ontology modeling
Define business concepts, entity types and relationships for your domain. Connect terms such as customer, order and revenue to the data and services that implement them.
Context for workflows & agents
Retrieve owners, dependencies, policies and environment-specific context during execution. Give an agent the related records it needs to investigate or plan a change.
History & provenance
Inspect where a graph record came from, when it changed and which run or review supports it. Attach new outcomes to the same entities for future investigations.
How it works
Follow the data and execution.
01
Connect
Bring business terms, metrics, customers and owners together with their data and systems.
02
Understand
Explore shared definitions, sources and relationships to see what sits behind a business result.
03
Decide
Review business impact, accountable owners and relevant policies with the teams involved.
04
Act
Use VegaFlow to coordinate approved follow-up work and link outcomes back to the same context.
VegaGraph / start with one outcome