Introduction
Migrate your database, storage, and auth off Supabase to infrastructure you own.
Unbase moves a Supabase project to infrastructure you control: any Postgres (Neon, RDS, plain), Better Auth, and any S3-compatible storage (Cloudflare R2, AWS S3, GCS, MinIO).
It is read-only at the source — Unbase never writes to or mutates your Supabase project — and verified at the target, reconciling row counts after every load.
Why
Supabase is excellent to start on, but couples your database, auth (GoTrue), and storage to one vendor. Unbase decouples them so you can leave on your terms, keeping your data, your users' passwords, and your file URLs intact.
What it migrates
Database
Schema introspection, FK-safe row load into any Postgres, with row-count verification.
Storage
Byte-for-byte object mirroring to R2/S3/GCS/MinIO, plus URL rewriting in your data.
Auth
Users and OAuth identities into Better Auth — bcrypt password hashes preserved, no resets.