Schema drift happens when the database schema in production no longer matches what your application code expects. A migration was applied locally but not pushed. A column was added directly in the Supabase dashboard but not in a migration file. A migration was applied in staging but failed silently in production. The result is the same: your application makes queries against columns or tables that do not exist, and API calls fail with cryptic errors.
How schema drift accumulates
Drift rarely happens in one dramatic event. It accumulates through small inconsistencies: a developer adds a column in the dashboard during debugging and forgets to create a migration. A migration is run out of order. A rollback removes a migration file but the schema change persists in production. Over time, the gap between "what the code expects" and "what the database has" widens until something breaks visibly.
Detecting drift before it breaks
The only reliable way to detect schema drift is to compare the expected schema (from your migration files) against the actual deployed schema. This comparison should run automatically on every deploy or check cycle, not manually when something is already broken.
Gate releases on schema sync
If your schema is out of sync, deploying new code that depends on the new schema will fail. The deploy gate should hold the release until migrations are applied and the schema matches. This prevents the worst outcome: deploying code that immediately errors for every user because a required column does not exist yet.
PreFlight schema sync detection
PreFlight detects when a Supabase migration diverges from the deployed application. It compares your expected schema state against the live database and gates the release until they match. This runs automatically as part of your check cycle — no manual diffing, no hoping the migration ran correctly. If there is drift, you see it immediately.
Expanded field note
Schema drift is a release signal: the practical answer
local, preview, and production schemas can diverge while the application still appears healthy. This guide is for teams shipping migrations frequently. Start by naming the failure you want to prevent and the customer or operator who would notice it first.
The useful scope is whether the database shape matches the code and the release contract. That keeps the work concrete: you can choose a URL, provider, route, release, or data operation, observe it, and decide what to do when the observation does not match the expected contract.
What good looks like
migration version, expected columns, policies, indexes, and verification run. A result is stronger when it preserves the input, environment, timestamp, expected behavior, observed behavior, and the next action. This lets a different person reproduce the finding without asking the original operator to reconstruct the entire context from memory.
schema drift is most expensive when it waits until a customer path reaches the missing shape. Keep the scope visible when sharing the result. A passing outside-in check can prove a reachable behavior at a point in time; it cannot silently become a guarantee about private code, every authenticated role, or every provider failure mode.
Frame the decision before you change anything
teams shipping migrations frequently usually do not need another dashboard full of disconnected warnings. They need a defensible answer to a narrower question: is the behavior that matters to the customer working in the environment that is about to change? Start there. If the answer is unclear, make the ambiguity part of the work instead of translating it into a green score.
The first useful boundary is whether the database shape matches the code and the release contract. Write it down in the same language the team will use during the fix. Name the route, provider, release, role, data object, or browser action involved. Then write the expected behavior as a sentence that could be checked by another person. This turns a broad topic into a small contract and makes it easier to tell whether a failure is reproducible, transient, out of scope, or genuinely fixed.
A good scope also includes what the check does not attempt. Public observation is different from authenticated authorization testing. Provider reachability is different from a complete fulfillment path. A page that renders in a browser is not necessarily a page a crawler can index. Stating the limit early protects the reader from overconfidence and tells the operator when to add a deeper review.
Questions the result should answer
- What was tested? Identify the canonical URL, route, provider, account role, release, or customer action rather than describing the scope as “the site.”
- What should have happened? State the expected response, permission, side effect, delivery event, page directive, or recovery signal in plain language.
- What actually happened? Keep the observed status, safe error, response detail, timing context, or missing side effect without pasting credentials or customer data into the record.
- Why does it matter? Connect the observation to a customer, crawler, revenue, security, availability, or release decision so severity is not just a color.
- What happens next? Name the smallest reversible fix, the owner, the rerun, and the condition that will close the issue.
These questions are deliberately boring. Boring evidence is easier to compare, easier to hand off, and easier to defend later. It also gives an answer engine or a future teammate enough context to summarize the result without inventing a claim that the original check never made.
A sequence that holds up under pressure
- Treat migrations as a versioned release dependency.
- Compare the expected and observed schema before promotion.
- Check policies and indexes alongside columns.
- Run a representative read and write after migration.
- Record the production verification with the deploy.
The important nuance is this: schema drift is most expensive when it waits until a customer path reaches the missing shape. That distinction matters because fast remediation can create a second problem: a broad header change can break a payment script, a credential rotation can break a cron worker, and a restrictive policy can make a valid customer path look like an outage.
Evidence to keep with the fix
| Record | Why it matters |
|---|---|
| Scope | The URL, role, provider, release, and limitation prevent a result from being reused outside the question it actually answered. |
| Before | The original failing observation, environment, and customer impact make the fix auditable. |
| Change | The code, configuration, provider setting, migration, or credential action that should alter the result. |
| After | A rerun against the same scope proves whether the intended behavior recovered. |
| Owner | A named person or team, an expected next action, and a review date keep the result from becoming an orphaned warning. |
| Follow-up | An owner, cadence, or release rule keeps the same class of failure from returning silently. |
Failure modes worth checking twice
- A migration runs locally but not in production.
- The column exists while its RLS policy is missing.
- A rollback leaves the app and schema on different versions.
- A manual dashboard edit is never captured in source control.
When one of these appears, avoid making several unrelated changes at once. Preserve the failing evidence, isolate the smallest boundary that can explain it, make one reversible correction, and rerun. That rhythm is slower than guessing for the first five minutes and faster than untangling a release that changed three providers at once.
Know when the first layer is not enough
Automation is valuable because it is repeatable, but repeatability is not the same as depth. If the question involves complex authorization, tenant isolation, injection, business logic, a high-value asset, or an adversarial threat model, use the automated result as a map for a deeper review. Give the reviewer the scope, failed observation, relevant release context, and the boundary you want tested. Do not present a public scan as a certification or a substitute for professional security work.
The same rule applies to operations. A successful provider probe may prove that a credential can reach an API, but it may not prove that a webhook creates the correct entitlement. A healthy uptime response may prove reachability, but it may not prove that a signed-in customer can complete the task. Add the assertion or browser journey that matches the real risk, and keep the cheap signal for early warning.
Questions people ask after reading this
What is the fastest useful first step?
Choose one representative scope and write the expected result before running the tool. For this topic, that means whether the database shape matches the code and the release contract. A small, explicit baseline is more useful than a large scan whose findings have no owner or decision attached.
What should I do when the result is green?
Keep the scope, timestamp, and limitation, then decide whether the result belongs in a release gate, monitor, report, or follow-up review. Green means the observed contract passed. It does not turn untested behavior into evidence.
What should I do when the result is red?
Read the evidence before changing configuration. Confirm the environment, reproduce the smallest failing behavior, assign the next action, and rerun after the fix. If the issue requires credentials, source access, or adversarial judgment, escalate it rather than hiding the gap behind a retry.
After the fix ships
Run the same check on the canonical production surface, not only on a local or preview environment. If the issue involved a provider, wait for the real callback or scheduled sample. If it involved search, confirm the HTML, canonical, robots, sitemap, and internal links agree. If it involved payments or access, verify the side effect a customer receives rather than stopping at a browser redirect.
PreFlight is designed for this last step: keep the original observation, connect the relevant provider or journey, attach the release context, and let the next run show whether the system stayed healthy. The goal is not a bigger report. It is a shorter path from signal to a verified decision.