Moving off Supabase: 7 options and what each move costs

The best Supabase alternative depends on which part of Supabase you want to replace. Supabase is Postgres plus auth, file storage, realtime, edge functions and a generated API in one project. Some alternatives replace all of that with a different stack (Firebase, Appwrite, Nhost, PocketBase, Convex). Others replace only the database and leave auth and storage to you (Neon, Turso). Free tier figures below come from each pricing page, checked on 22 October 2026. For the quick list with open source and self hosted picks, see Supabase alternatives; this guide goes deeper into what each move involves.

The short list

Why people look for a Supabase alternative

The reasons we see most often, roughly in order:

1. The free plan pause. Free projects pause after one week without activity, which catches demo apps and side projects.
2. Two free projects. The free plan allows two active projects. If you build many small things, that runs out fast.
3. Wanting less. Some apps only need Postgres, and the auth, storage and API layers are things to learn and secure without a benefit.
4. Wanting a different model. Document data, offline-first mobile sync or reactive queries fit other tools better than SQL tables.

If one of these is your reason, it points straight at one of the options below.

Firebase: the closest all in one rival

Firebase is Google's backend platform: Firestore (a document database), Auth, Hosting, Cloud Functions and more. It is the default for many mobile apps because its client SDKs handle offline data and sync well.

The free Spark plan includes 1 GiB of Firestore storage, 50,000 reads, 20,000 writes and 20,000 deletes a day, and Auth for up to 50,000 monthly active users. The Blaze plan is pay as you go and keeps the free quotas. The big difference from Supabase is the data model: Firestore is NoSQL, so you design around documents and queries, not joins. Firebase's pricing page now also lists SQL Connect with Cloud SQL for PostgreSQL if you want SQL on Google's side.

Pick Firebase if you build mobile first, want offline sync, or already run on Google Cloud. Firebase is not open source and you cannot self-host it.

Appwrite: open source, many services

Appwrite covers the same ground as Supabase and more: auth, databases, storage, functions, messaging, realtime and hosting, and you can run it on Appwrite Cloud or self-host it from the open source code. Its pricing page lists a free organisation tier that freezes a project when it hits its limits rather than billing you, and dedicated database tiers from $10 a month. Check the pricing page for the current free limits, because we could not read them on the day we checked.

Pick Appwrite if you want an all in one backend you can also run yourself, and you do not need Postgres specifically.

PocketBase: a backend in one file

PocketBase is an open source backend that ships as one file: an embedded SQLite database with realtime subscriptions, auth, file storage and an admin dashboard. You extend it in Go or JavaScript. It costs nothing but the server you run it on.

It is still before 1.0 (a 0.x release on 12 November 2026), so read the changelog before upgrading. Pick PocketBase for small and medium apps, internal tools and prototypes where one process on a cheap VPS is a feature, not a limit.

Nhost: Postgres with GraphQL

Nhost is the closest in spirit to Supabase: Postgres, with Hasura GraphQL on top, plus auth, storage and functions, as a cloud service or self-hosted. The free Starter plan allows one active project with a 1 GB database and 1 GB of storage, and like Supabase it pauses after a week without activity. Pro starts at $25 a month with $15 of compute credits included.

Pick Nhost if you want a GraphQL API over Postgres instead of Supabase's REST style API.

Convex: a reactive backend

Convex is a different kind of backend. You write queries and mutations as TypeScript functions, and every query the UI subscribes to updates live when data changes, with no cache or socket code on your side. It suits collaborative and realtime apps very well. On 12 November 2026 its Free and Starter plan was $0 and pay as you go for 1 to 6 developers, with 1M function calls, 0.5 GB of database storage and 1 GB of file storage included, and Professional was $25 per developer a month.

We compare Convex with Supabase, Neon and Turso in our guide to picking a database for a new app, and two at a time in Supabase vs Convex.

Neon: only the Postgres

If what you want from Supabase is the database, Neon is the cleanest swap. It is serverless Postgres from Databricks with branching per pull request and compute that scales to zero after 5 minutes idle. The free plan allows 100 projects, each with 1 GB of storage and 100 compute-hours a month, and it does not pause your data. It now also lists built in auth for up to 60,000 monthly active users.

The two are close enough that we wrote a full head to head: Neon vs Supabase.

Turso: SQLite at the edge

Turso hosts SQLite (libSQL) databases, and it is built for having many of them: the free plan includes 100 databases, 5 GB of storage, 500 million rows read and 10 million rows written a month. The Developer plan is $4.99 a month. One thing to know: Turso's pricing page now says "Turso is joining Supabase", so it may end up part of Supabase rather than an alternative to it.

How to choose

• You want the same thing without the free plan pause: Neon for the database alone, or PocketBase if you can host it.
• You want everything in one place, but not Supabase: Firebase for mobile, Appwrite for open source.
• You want GraphQL over Postgres: Nhost.
• You want live data in the UI without writing sync code: Convex.
• You want many tiny databases: Turso or Neon.

Whichever you choose, keep your data portable. With Postgres based options a pg_dump moves the data; with Firebase and Convex, plan an export before you need it. For the ORM on top, read Drizzle vs Prisma, and browse the databases category for newer options.