Data lineage and observability that shows what breaks before it breaks
Connect your warehouse and Datatrail maps every table and column, traces any number to its source, and alerts you the moment something goes stale or changes, before it reaches a dashboard.
Read-only connection. Datatrail never moves or mutates your data.
Pick a scenario, watch the trail draw itself
Connects to
Why data teams switch
Lineage first, and the answer to what breaks before you ship it
Most catalogs draw you a graph after something broke. Datatrail leads with the question an engineer actually asks: if I change this column, what dies? It answers it before the merge.
Know what feeds every number
01Trace any column from the dashboard back through every model to its source table. When the CEO asks where a number comes from, you have the whole path in seconds, not a Slack archaeology dig.
Catch breaks before people do
02Freshness and schema-change alerts fire the moment a table goes stale or a column changes upstream, so you hear it from Datatrail, not from the people reading a blank dashboard.
Know what you will break before you ship
03Select a column you want to change and Datatrail lights the blast radius: every model and dashboard downstream. You answer "if I drop this, what dies?" before the merge, not after.
A map your whole team can read
04Lineage builds itself from your query history and stays current, even when someone writes ad-hoc SQL. The catalog is a side effect of the map, not a quarter of manual data entry.
What it does
Map lineage, watch freshness, catch schema changes, see the impact
Lineage diagram
Datatrail draws the diagram for you. It reads query history and your dbt graph, then renders a living lineage visualization from raw ingestion tables to the dashboards your team trusts, so the map matches production instead of the whiteboard photo in a wiki.
Learn more LINEAGE - COLUMN LEVELColumn-level lineage
Datatrail traces a single column through every join, CASE statement, and aggregation between its source and the report that uses it. When someone asks where orders.revenue comes from, you have the exact answer in one click.
Learn more LINEAGE - BLAST RADIUSImpact analysis
Before you rename a column or drop a model, Datatrail shows every downstream asset that depends on it. You see the blast radius first, so a small change to stg_orders never silently breaks a board-level dashboard.
Learn more OBSERVABILITY - FRESHNESSFreshness monitoring
Datatrail watches when each table was last loaded and compares it to a freshness SLA you set or that it learns. When stg_stripe_charges stops updating, you hear about it before the revenue dashboard shows yesterday figures.
Learn more OBSERVABILITY - SCHEMA DRIFTSchema change alerts
Datatrail watches the structure of every source and model, so when an upstream column is dropped or retyped you get an alert with the exact downstream assets at risk. Schema drift stops being a surprise you debug after the fact.
Learn more OBSERVABILITY - ANOMALIESAnomaly detection
Datatrail learns the normal shape of each table, then flags when row volume, load timing, or a column distribution drifts out of range. A 40 percent drop in fct_orders row count surfaces as an alert, not a quarter-end surprise.
Learn moreHow it works
Connect read-only, map the lineage, trace any number, catch every break
Connect your warehouse, read-only
Grant read-only access to your query history and metadata on Snowflake, BigQuery, Redshift, Postgres, or dbt. We request the minimum read scopes and never get write access.
Datatrail maps the lineage
It parses real query logs to map how data flows table to table and column to column, then watches every table for freshness and schema changes. No manual diagramming.
Trace any number to its source
Pick a column or a dashboard and see the whole path light up, source to model to exposure, with the count of everything downstream that depends on it.
Get alerted and see the impact
When a table goes stale or a schema changes upstream, an alert routes to Slack or email, and impact analysis shows what will break before a change reaches a dashboard.
Who it is for
Built for data engineers and analytics teams
Drive it yourself
Trace a column, catch a stale table, see a blast radius
Pick a scenario and watch the lineage trail draw itself, source to model to dashboard, with the count of everything downstream that depends on it. This is the real console, not a screenshot.
Read-only connection. Datatrail never moves or mutates your data.
// What it maps
Column-level lineage across Snowflake, BigQuery, Redshift, Postgres, and dbt, traced past the dbt boundary and forward to every dashboard, in one read-only view.
Transparent pricing
Pricing you can read on the page
Every plan is paid and self-serve. It often pays for itself the first time it catches a broken pipeline before an executive does.
Starter
Small data teams, one warehouse
Team
Growing analytics and data-eng teams
Scale
Data platform teams at scale
Enterprise
Large orgs and regulated data
FAQ
Questions data teams ask first
Yes. Datatrail connects read-only. It reads your query history and metadata to build lineage, and it never moves, copies, or mutates your data. It does not need write access and it does not ingest row-level data to map how tables and columns flow. You can revoke access at any time. Read-only by design is the whole point.
Lineage maps automatically in minutes from your query history. There is no manual diagramming, no months-long rollout, and no need to annotate every model by hand. The first pass surfaces your table and column flow, freshness state, and recent schema changes right away.
Yes. Datatrail traces a single column through every transformation, from its source table to the dashboards that use it. You can answer exactly what feeds a number and what would break if that column changed, not just which tables touch which tables.
Snowflake, BigQuery, Redshift, Postgres, and dbt, with read-only connections to query history and metadata. Datatrail parses real query logs, so it maps lineage past the dbt boundary and stays current even when someone writes ad-hoc SQL.
Datatrail is lineage-first and impact-before-you-ship, self-serve and transparent-priced. Enterprise governance suites and observability incumbents are powerful but sales-gated, six-figure, and built for a procurement cycle. Many catalogs show you a graph after something broke. Datatrail leads with the question an engineer actually asks, if I change this column what dies, and answers it pre-merge.
Datatrail surfaces stale tables and upstream schema changes and shows the blast radius of a change before it merges, so breaks get caught before they reach a person. It does not promise zero incidents or perfect coverage. It gives you the map and the early warning so a silent upstream change stops poisoning a dashboard quietly.
Stop finding out about broken data from the people who use it
Connect your warehouse read-only and get a lineage map in minutes, freshness and schema alerts before a dashboard breaks, and the blast radius of any change before you ship it. Datatrail never moves or mutates your data.
Read-only · Never moves your data · Live in minutes