Caught at the source
Breaking changes flagged at the PR level. Not after deployment. Not after your stakeholders notice.
Schema Guardian analyzes GitHub PRs with AI before they merge. It maps downstream impact across your entire stack and posts a bot comment inside the PR so your team knows exactly what will break and why.
How it works
No waiting for deployment. No stakeholder complaints. Schema Guardian runs the moment a PR is opened.
Your analytics engineer opens a PR to rename a column or change a type in a dbt model. Looks clean. Tests pass.
Claude AI reads the PR diff, identifies breaking changes, and maps downstream impact across your connected warehouse, dbt models, and BI layer.
A structured comment appears directly in GitHub. Breaking changes flagged. Impacted assets listed. Mitigation recommendations included. No context switching.
Merge Protection sets a required status check via the GitHub Checks API. A breaking change triggers conclusion:failure and blocks the merge until resolved or overridden by an admin.
Breaking changes flagged at the PR level. Not after deployment. Not after your stakeholders notice.
Impact traced from the dbt model change to specific Tableau workbooks and Power BI reports.
No new tool to open. The bot comment appears where your team already reviews code.
How Schema Guardian compares
| Capability | Datawise | Recce | Datafold |
|---|---|---|---|
| Pre-merge PR analysis | Datawise for Pre-merge PR analysis: included | Recce for Pre-merge PR analysis: included | Datafold for Pre-merge PR analysis: included |
| AI-generated impact explanation | Datawise for AI-generated impact explanation: included | Recce for AI-generated impact explanation: not included | Datafold for AI-generated impact explanation: not included |
| BI layer impact (Tableau, Power BI) | Datawise for BI layer impact (Tableau, Power BI): included | Recce for BI layer impact (Tableau, Power BI): not included | Datafold for BI layer impact (Tableau, Power BI): not included |
| Merge blocking via GitHub Checks API | Datawise for Merge blocking via GitHub Checks API: included | Recce for Merge blocking via GitHub Checks API: not included | Datafold for Merge blocking via GitHub Checks API: not included |
| Post-deployment detection | Datawise for Post-deployment detection: included | Recce for Post-deployment detection: not included | Datafold for Post-deployment detection: included |
Frequently Asked Questions