SchemaDrift Guardian
Free while in early access

Catch breaking schema changes before they merge.

Someone opens a pull request that drops a column or narrows a type. Nothing in the description says so. It merges, and days later a dashboard breaks, a nightly job fails, or an API consumer starts throwing 500s.

SchemaDrift is a CI check that catches it at the pull request and turns the build red before it lands — with a comment naming each breaking change and what it does to callers. Monitoring tells you after the pipeline broke. This refuses the merge.

Sign in with GitHubRead the FAQ

No credit card. No billing to set up. Sign in with GitHub and connect a repository.

What counts as breaking

Anything that can break a reader without touching the reader’s code. Additive changes are reported as informational and never fail a build.

Column droppedusers.login_count (integer) was dropped.
Type narrowedusers.email narrowed from varchar(255) to varchar(64).
Enum variant removedorder_status lost the value “refunded”.

How it works, from pull request to verdict

Your production database is never contacted, and no row data ever leaves your CI.

01

A pull request changes the schema

Someone drops a column, narrows a type, or removes an enum variant. Nothing in the PR description says so.

02

CI builds the schema the PR would produce

The Action stands up a throwaway database, applies the PR’s migrations, and introspects the result. Your production database is never touched.

03

The check goes red before merge

The diff runs against the baseline from your default branch. Breaking changes fail the build with a comment naming each one.

Setting it up takes six steps

  1. 1Install the GitHub App, so verdicts can post to your pull requests.
  2. 2Sign in with GitHub. A workspace is created on first sign-in.
  3. 3Connect a schema: a name, the owner/repo to gate, and which schemas to read.
  4. 4Copy the workflow it generates, pre-filled with your source name.
  5. 5Save the API key as the repository secret SCHEMADRIFT_API_KEY.
  6. 6Commit the workflow to .github/workflows/schema-drift.yml.

The first pull request after setup becomes your baseline — there is nothing to compare against yet, so it passes. The one after that gets a real verdict. Start in observe-only mode and switch on blocking once the verdicts have earned trust.

What it does not do yet

It tells you the schema broke, not who it broke. Tracing a change through to the specific dashboards and services that depend on it is not built yet. It is the next thing being built, and this page will say so when it ships.

Free while in early access

There is no paid plan, no trial timer, and no billing to configure. Early access is about finding out whether the verdicts are right on real schemas. If pricing ever arrives it will not arrive as a surprise on an account already using it.

Sign in with GitHub