Trace every column from source to dashboard to API
Understand exactly where your data comes from, how it changes, and where it ends up — across warehouses, pipelines, dashboards, and APIs. Goava builds end-to-end, column-level lineage so your Data Management Office can answer "where did this number come from?" with evidence, not guesswork.
End-to-End & Column-Level
Follow every column from source system to final report
Most teams can name the dashboard; few can prove the path behind it. Goava maps lineage across your entire stack — tables, pipelines, topics, dashboards, and APIs — at both table and column granularity. When a regulator, auditor, or business owner asks how a figure was produced, the answer is one click away. And before you change anything upstream, impact analysis shows exactly which downstream assets — and which consumers — will feel it.
- End-to-end lineage across tables, pipelines, dashboards, topics, and APIs
- Column-level detail: trace a single field through every transformation
- Impact analysis: see every downstream asset before you change a schema
- Lineage evidence that supports documentation aligned with the NDMO framework
Visual Editor & ML Suggestions
Curate lineage visually — and let ML fill the gaps
Automated harvesting covers most of your estate, but real environments always have connections no scanner sees — legacy jobs, manual processes, custom scripts. Goava's visual lineage editor lets data stewards draw, correct, and document those connections directly on the graph. ML-based suggestions propose likely lineage links — including API-to-table relationships — for stewards to review and confirm, so the graph keeps getting more complete without becoming less trustworthy.
- Visual lineage editor: add, correct, and annotate lineage on the graph
- ML-based suggestions propose likely lineage links for steward review
- API-to-table suggestions connect endpoints to the data that powers them
- Ownership and stewardship keep every manual edit accountable
Lineage capabilities
Everything your Data Management Office needs to prove where data comes from — and where it goes.
Column-Level Lineage
Trace individual columns through every join, transformation, and aggregation — from source system to dashboard.
Impact Analysis
Before changing a table or pipeline, see every downstream asset, report, and API endpoint that depends on it.
Visual Lineage Editor
Draw, correct, and document lineage directly on the graph — including manual processes no scanner can detect.
ML-Based Suggestions
Machine learning proposes likely lineage links for stewards to confirm, keeping the graph complete and trustworthy.
Pipeline-Aware via Airflow & dbt
Lineage understands your orchestration layer: Airflow DAGs and dbt models become part of the end-to-end picture.
API-to-Data Lineage
See which tables power which API endpoints — across Kong, AWS API Gateway, Azure API Management, Google Cloud API Gateway, and Nginx.
Frequently asked questions
How does Goava build lineage?
Lineage is harvested automatically through Goava's native connectors to your databases, warehouses, BI tools, and pipeline tools such as Airflow and dbt — and through automatic endpoint detection from OpenAPI specs on your API gateways. ML-based suggestions then propose additional links, and data stewards complete the picture with the visual lineage editor.
Can we edit lineage manually?
Yes. The visual lineage editor lets data stewards add, correct, and annotate lineage directly on the graph — useful for legacy jobs, manual processes, and custom scripts that automated harvesting cannot see. Combined with ownership and stewardship, every edit stays accountable.
Does lineage really go down to the column level?
Yes. Goava traces lineage at both table and column granularity, so you can follow a single field through every transformation from source to dashboard. Impact analysis works at the same granularity, showing exactly which downstream columns and assets a change will affect.
Are APIs part of the lineage graph?
Yes — this is a Goava distinctive. Goava discovers APIs from gateways such as Kong, AWS API Gateway, Azure API Management, Google Cloud API Gateway, and Nginx, detects endpoints automatically from OpenAPI specs, and maps API-to-data lineage so you can see which tables power which endpoints. Classifications and PII tags are inherited between data and the APIs that expose it.
See your data's full story — end to end
Book a demo and watch Goava trace a column from its source system to the dashboards and APIs it feeds — deployed on-premises or in cloud inside Saudi Arabia.