No noise
Safe changes don't page you. Only breaking changes surface as actionable alerts.
Know what broke in productionbefore your stakeholders do.
Schema Radar detects column-level changes post-deployment across Snowflake and BigQuery. It shows you what changed, what's impacted, and who owns it. Before the Monday 9am Slack message from your VP.
How it works
Automated detection. Full blast radius. No guesswork.
Schema Radar runs continuously. When something changes, you know immediately. Not when a dashboard goes dark.
- 1
Schema change lands in production
A column is renamed, removed, or its type changes in Snowflake or BigQuery. It made it through. Schema Radar picks it up on the next ingestion run.
- 2
Breaking vs safe classification
Not every change is a breakage. Schema Radar distinguishes column adds (safe) from renames, removals, and type changes (breaking). No alert fatigue from false positives.
- 3
Blast radius surfaced immediately
Impacted downstream assets shown. Tableau workbooks, Power BI reports, dbt models. Ownership surfaced. You know who to contact before anyone reports an issue.
- 4
Mitigation tracked across ingestion runs
Schema Radar compares ingestion runs to track whether the breakage has been resolved. History is immutable. You have a clean audit trail of what happened and when.
Immutable history
Every schema change is logged permanently. You can trace what broke, when, and what the state was before.
Ownership built in
Impacted assets surface with ownership so the right person gets the right alert immediately.
What Schema Radar detects
| Change type | Classification | Example |
|---|---|---|
| Column added | Safe | New column appended to existing table |
| Column renamed | Breaking | revenue → total_revenue breaks downstream models |
| Column removed | Breaking | Referenced column dropped from source table |
| Type change | Breaking | INT to STRING causes dbt model cast failure |
Frequently Asked Questions