For teams leaving Supabase
Switch from Supabase with a plan you approve.
Fieldwick reads your Supabase project, maps every service, env var, and Postgres add-on, and shows you the full plan before anything changes. No Auth or Storage parity needed - just one platform for the Postgres and the services that already talk to it.
$0 to try. Bring your project over when you are ready.
How it works
Three promises that make the migration feel safe.
Postgres mapped before you commit
Point Fieldwick at your existing Supabase project and it identifies your Postgres add-on, maps it to a Fieldwick managed Postgres add-on, and shows you the full plan. You review exactly what will move before you confirm anything.
Keep your services running
Already running your app on Vercel, Railway, Fly, or Render with Supabase as the database? Fieldwick detects those services and maps their env var references to the new add-on. The ${{Postgres.DATABASE_URL}} reference contract is preserved in the plan, so DATABASE_URL stays the only thing that needs to change.
No surprise bills
Supabase compute-hour, egress, and storage tiers can stack up unexpectedly in a busy week. Fieldwick rolls everything into one hard monthly cap for your whole account. You set the ceiling; we enforce it - no per-service or per-project billing to track.
Ready when you are
Bring your project to Fieldwick.
The migration wizard is in your dashboard. We will not deploy until you approve the diff; we will not delete your Supabase project on the way out.
Open the migration wizard