SupaForge
COMPARISON

SupaForge vs. Flyway / Liquibase

Traditional migration runners vs Supabase-native drift detection.

Note: The SupaForge CLI is currently being prepared for public release. to be notified when it's available.

How Flyway and Liquibase Work

Flyway and Liquibase are proven migration management tools. They track which SQL or XML changesets have been applied to a database and run pending migrations in order. They solve the problem of applying known changes reliably.

What they don't solve is detecting unknown changes — differences that crept in through the Supabase dashboard, direct SQL sessions, or configuration changes made outside the migration pipeline.

Different Problems, Different Tools

Flyway and Liquibase are migration runners. SupaForge is a drift detector. They complement each other rather than compete:

  • Flyway / Liquibase: "Apply these specific changes to the database."
  • SupaForge: "What is actually different between these two live environments?"
FeatureFlyway / LiquibaseSupaForge
PurposeApply known migrationsDetect unknown drift
Schema support✅ SQL / XML changesets✅ Full DDL diff
RLS policies✅ Dedicated check
Auth settings✅ 20+ settings
Storage buckets✅ Metadata + policies
Cron jobs✅ pg_cron diff
Edge Functions✅ Version mismatch
DirectionForward-only (UP)Bi-directional (UP + DOWN)
Dashboard changesInvisibleDetected automatically
Supabase-nativeNo — generic SQL toolYes — built for Supabase
Drift score✅ 0–100 with severity

Using Them Together

A robust workflow combines both approaches: use Flyway or Liquibase to manage your intentional migrations, and use SupaForge to detect any drift that happened outside the migration pipeline.

Install SupaForge
npm i -g @akalforge/supaforge
supaforge.config.json
{
  "environments": {
    "staging": {
      "dbUrl": "postgresql://user:pass@db.STAGING_REF.supabase.co:5432/postgres",
      "projectRef": "STAGING_REF",
      "apiKey": "your-staging-service-role-key"
    },
    "production": {
      "dbUrl": "postgresql://user:pass@db.PROD_REF.supabase.co:5432/postgres",
      "projectRef": "PROD_REF",
      "apiKey": "your-production-service-role-key"
    }
  },
  "source": "staging",
  "target": "production"
}
Detect drift after migration deploy
supaforge scan
Preview what SupaForge would fix
supaforge promote

When Flyway / Liquibase Is Enough

If your team never uses the Supabase dashboard, never runs ad-hoc SQL, and manages everything through version-controlled migration files — Flyway or Liquibase alone may suffice for schema management. Even then, they won't cover auth, storage, cron, or Edge Functions.

Summary

Flyway and Liquibase are excellent migration runners for applying known changes. SupaForge detects unknown drift across every Supabase check — making them natural complements in a production-grade workflow.

Ready to try SupaForge?

Detect drift across all your Supabase environments in seconds.

View on GitHub