supabase-schema-diff
Visual diff for Supabase schema drift between staging and production
Catch breaking migrations before they hit customers. Compare tables, columns, indexes, and RLS policies in minutes instead of shipping blind and hoping rollbacks save you.
The Problem
Supabase teams often run migrations in staging and assume production matches. Drift builds silently, and the first signal is broken APIs after deploy.
What Breaks
Dropped columns, tightened nullability, changed RLS policies, and index mutations can fail reads, writes, and permissions instantly.
The Fix
Run a visual diff before promoting migrations. Ship with confidence because you know exactly what changed and why it is risky or safe.
What you get inside the dashboard
The tool compares Supabase environments and labels each change with impact and recommended migration order.
Pricing
Simple pricing for teams that want safer migrations without enterprise overhead.
Starter
$12/month
Unlimited schema diff runs, staging-vs-prod checks, and webhook-backed paywall access.
Unlock purchased access
Complete Stripe checkout first, then unlock with the purchase email to set your secure access cookie.
FAQ
What schema changes are marked as breaking?
Dropped tables, removed columns, NOT NULL tightenings, unsafe type mutations, removed/changed RLS policies, and critical index removals are flagged as breaking so they are obvious before rollout.
How do you connect to Supabase projects?
You provide each project URL and service role key in the dashboard, then the app reads metadata from Supabase pg-meta APIs for public/auth/storage schemas.
How does access unlocking work after payment?
Stripe webhook events record your purchase email. Enter the same email in Unlock Access and we issue an HTTP-only cookie that opens the dashboard.
Can I run this in CI before migrations ship?
Yes. The API returns a structured diff payload and unified diff text so you can fail deployments when breaking changes appear.