Skip to content
PromptToProd

Best Supabase alternatives (2026)

Supabase is our top-ranked backend, but free projects pause after a week of inactivity, the Free plan allows 2 active projects, and Pro starts at $25/mo with only one small compute instance covered. These alternatives cover serverless Postgres you can pg_dump into (Neon, Prisma Postgres, Xata), all-in-one backends with auth and storage (Convex, Appwrite, Nhost, Firebase) and a free self-hosted single file (PocketBase). Ranked by our evidence-based score, with Supabase shown last for reference.

Editorial picks for this use case. See each tool page for its score breakdown. Last updated 2026-10-25.

#1
N
Neon open source
Serverless Postgres
Verified
86
/ 100
 #2
C
Convex open source
Reactive backend platform
Verified
84
/ 100
 #3
P
Prisma Postgres
Managed Postgres from the Prisma team, billed per operation
Verified
81
/ 100
 #4
A
Appwrite open source
Open-source backend platform
Verified
80
/ 100
 #5
P
PocketBase open source
Open-source backend in one file: SQLite, auth, files and realtime
Verified
77
/ 100
 #6
F
Firebase
Google's app development platform
Verified
77
/ 100
 #7
N
Nhost open source
Open-source Postgres backend with GraphQL, auth, storage and functions
Verified
76
/ 100
 #8
X
Xata open source
Postgres with instant copy-on-write branches for every PR and agent
Verified
71
/ 100
 #9
S
Supabase open source
Open-source Postgres development platform
Verified
93
/ 100

The short version

Neon (86) is the closest swap if you want to keep Postgres: serverless compute that scales to zero, branching, and now Managed Better Auth, object storage and functions alongside the database. Convex (84) is the pick for a reactive, all-TypeScript backend instead of SQL. Prisma Postgres (81) is Postgres billed per query, with a free plan and a $10/mo Starter. Appwrite (80) is the open-source all-in-one with a Supabase migration wizard in its console. PocketBase (77) is a free single-file backend for one cheap server, Firebase (77) is Google’s NoSQL backend, Nhost (76) is the closest feature match (Postgres, auth, storage, functions) with a GraphQL API, and Xata (71) is Postgres built around a branch per pull request or agent. Supabase itself scores 93 and is still our top-ranked database, so switch for a concrete reason, not by default.

Why people look for a Supabase alternative

Four reasons come up most. Pausing: Supabase’s docs say Free projects with low database activity over 7 days are paused (you get a warning email about a week before), and a paused project can be restored for up to a year; paid projects are never paused. The Free plan also allows only 2 active projects. Pricing past the free tier: Pro is from $25/mo and includes $10 of compute credits, enough for one Micro instance (1 GB RAM, shared CPU). Bigger instances cost more (Small $15/mo, Medium $60/mo, Large $110/mo), extra projects start at $10/mo, and usage above the included 8 GB disk, 100,000 MAU and 250 GB egress is billed per unit. The data model: Supabase is Postgres with row-level security; if you would rather write TypeScript functions than SQL, or store documents, Convex or Firebase fit better. Self-hosting: you can run Supabase yourself, but it is a different product from the cloud (see below).

Self-hosting Supabase vs switching

Supabase is open source and its docs recommend Docker Compose for self-hosting. A self-hosted install runs as a single project (Studio does not support multiple organizations or projects), and branching, managed backups and point-in-time recovery, advanced metrics, ETL and the Management API are not available. You are responsible for server security and updates, Postgres maintenance, high availability, backups and monitoring, and support is community-only. If you mainly want to stop paying, PocketBase (one binary) or self-hosted Appwrite are simpler to run; if you mainly want managed Postgres without pausing, a paid Supabase plan or Neon is less work than running the full stack.

Quick picks by need

Keep Postgres, pay by usage: Neon (Launch is usage-based at $0.106 per CU-hour and $0.35 per GB-month). Postgres billed per query, with spend limits on by default: Prisma Postgres. Postgres plus auth, storage and functions like Supabase: Nhost, or Neon’s new backend suite. Realtime TypeScript backend: Convex. Open-source all-in-one, cloud or self-hosted, with a migration wizard: Appwrite. Cheapest possible backend: PocketBase on your own small server. Mobile apps in the Google ecosystem: Firebase. A database branch for every pull request or agent: Xata, which charges no per-branch or per-user fees, or Neon branching.

Cost at small scale: the free plans

Supabase Free: 2 active projects, 500 MB database, 50,000 MAU, 5 GB egress, 1 GB file storage, paused after a week idle. Neon Free: no credit card or time limit, 100 projects with 1 GB storage and 100 CU-hours a month each, compute scales to zero after 5 minutes idle, and Managed Better Auth up to 60,000 MAU. Prisma Postgres Free: 200,000 operations a month, 2 GB storage and 50 databases, free forever with no card. Convex Free & Starter: $0 with 1M function calls, 0.5 GB database storage and 1 GB file storage included, for 1 to 6 developers. Nhost Starter: 1 active project, 1 GB database, 1 GB storage, 5 GB egress, paused after a week idle. Appwrite Free: 2 projects, 75,000 MAU, 2 GB storage, 5 GB bandwidth and 750K function executions, paused after a week idle; a project that hits a limit freezes until you upgrade, trim usage or the next billing cycle. Firebase Spark: no payment method, Firestore 1 GiB stored with 50K reads and 20K writes a day, Auth free up to 50K MAU, but no Cloud Functions. PocketBase: free; you pay only for the server. Xata: the open-source edition is free to self-host; Xata Cloud is pay as you go from $0.012/hr.

Cost at medium scale: the first real bill

Take an always-on production app with about 8 GB of data. Supabase Pro: $25/mo covers the Micro instance, 8 GB disk, 100,000 MAU, 250 GB egress and 7 days of daily backups; moving up to the Small instance (2 GB RAM) makes it about $30/mo ($25 plan + $15 compute − $10 credit). Neon Launch: a 0.25 CU compute running 24/7 is about 182 CU-hours, roughly $19 a month, plus about $2.80 for 8 GB of storage (computed from Neon’s list rates; scale-to-zero lowers it, and Neon quotes a typical spend of $15/mo for intermittent load). Prisma Postgres: Starter is $10/mo with 1M operations (then $8 per million) and 10 GB; Pro is $49/mo with 10M operations and 50 GB. Convex Professional: $25 per developer a month with 25M function calls and 50 GB of database storage. Nhost Pro: from $25/mo with $15 of compute credits, a 10 GB database, 50 GB storage and 50 GB egress. Xata Cloud: a small instance (2 GB RAM) is $18/mo plus $0.28 per GB-month, about $20 for 8 GB. Appwrite Pro: from $25/mo per project (+$15 per extra project) with $10/mo of database compute credits, 200,000 MAU (twice Supabase Pro’s 100,000), 150 GB storage and 2 TB bandwidth; dedicated database compute starts at $10/mo (1 core, 1 GB). At 300,000 MAU it is about $325/mo versus about $675/mo on Supabase Pro (see Supabase vs Appwrite). PocketBase: its FAQ says it can serve 10,000+ realtime connections on a $4 Hetzner VPS.

Moving your data off Supabase

To another Postgres (Neon, Prisma Postgres, Nhost, Xata): it is a standard dump and restore. Neon’s Supabase guide uses pg_dump -Fc on the public schema and pg_restore into a project on the same Postgres version, over an unpooled connection; add more --schema flags if you need auth or storage tables, and Neon also documents logical replication from Supabase for near-zero downtime. Supabase’s own CLI can dump roles, schema and data separately with supabase db dump. Row-level security policies that rely on Supabase’s auth schema need rewriting for the new auth provider. To Appwrite: its console wizard connects with your Supabase connection details and service_role key, and usage during the migration doesn’t count toward Appwrite Cloud charges. Appwrite’s docs warn that advanced indexes, Postgres functions and scheduling are not migrated, functions must be rewritten, and OAuth users have to sign in again. To Convex or Firebase: tables become documents, so plan to remodel data and rewrite queries.

Moving your users

Supabase Auth keeps users in the auth.users table and stores passwords as bcrypt hashes in its encrypted_password column, so you can export them with SQL or a dump of the auth schema. Any target that imports bcrypt hashes can keep existing passwords working; Firebase’s auth:import command, for example, accepts BCRYPT. Users who sign in with Google, GitHub or another OAuth provider just reconnect the same provider on the new backend. Test with a few accounts before you switch the app over.

When to stay on Supabase

Stay if pausing is the only problem: any paid plan stops automatic pausing, and $25/mo still includes compute, backups and 100,000 MAU. Stay if your app came from Lovable, Bolt or v0 and leans on their Supabase integration. Move when you need many small databases (Neon, Prisma Postgres), a reactive TypeScript model (Convex), a backend you host for the price of a small server (PocketBase, Appwrite), or a database branch per agent (Xata, Neon).

Side-by-side comparison

ToolScoreFree tierPricingBest for
Neon86Yes: 100 projects, 1 GB storage per project, 100 CU-hours/project/moLaunch: usage-based, no monthly minimum ($0.106/CU-hour, $0.35/GB-month)Serverless Postgres with instant branches for previews and agents
Convex84Yes: Free plan with hard resource capsProfessional $25/developer/mo; Starter $0 base plus pay-as-you-goTypeScript apps that need realtime data with minimal backend code
Prisma Postgres81Yes: 200K operations/mo, 2 GB storage, 50 databases, no cardStarter $10/mo (1M operations, then $8 per million; 10 GB, then $2/GB; spend limits); Pro $49/mo (10M ops, 50 GB); Business $129/mo (50M ops, 100 GB, HIPAA/SOC 2)TypeScript apps and coding agents that want a Postgres database in one command with predictable per-query pricing
Appwrite80Yes: 75K MAU, 2 GB storage, 5 GB bandwidth, 750K executions; 2 projects, paused after 1 week idlePro from $25/mo per project (+$15/extra project); 200K MAU included, then $3 per 1,000An open-source, self-hostable Firebase alternative
PocketBase77Yes: free to self-host (no hosted plan)Free and open source (MIT); you pay only for your own server. No official hosting.Small and mid-size apps that want a free, portable backend on one cheap VPS
Firebase77Yes: Spark plan with no-cost quotas (e.g. Firestore 1 GiB, 50K reads/day)Blaze: pay as you go above free quotasMobile and realtime apps that want a Google-managed backend
Nhost76Yes: Starter is free with 1 project, 1 GB database, 1 GB storage and 5 GB egress (the project pauses after 1 week of inactivity)Starter free (1 project). Pro from $25/mo with $15 compute credits included: 10 GB database (then $0.20/GB), 50 GB storage, 50 GB egress, daily backups. Team from $599/mo. Enterprise customBuilders who want a Supabase-style all-in-one Postgres backend but prefer a GraphQL API
Xata71No: 14-day free trial on Xata Cloud (no card); open source self-hosting is freeXata Cloud pay as you go from $0.012/hr (micro, ~$9/mo) + $0.28/GB-month storage; no per-branch or per-seat fees; BYOC quotedTeams running many coding agents or previews that each need an isolated copy of a production Postgres database
Supabase93Yes: 2 projects, 500 MB DB, 50K MAU, 1 GB storage (pauses after 1 week idle)Pro from $25/mo per org (includes $10 compute credit)Default backend for vibe-coded apps (Lovable, Bolt, v0 integrations)

FAQ

What is the best Supabase alternatives in 2026?
Our top pick is Neon (score 86/100): Serverless Postgres. Runners-up: Convex, Prisma Postgres, Appwrite, PocketBase, Firebase, Nhost, Xata, Supabase.
Is Neon free?
Neon free tier: Yes: 100 projects, 1 GB storage per project, 100 CU-hours/project/mo. Paid pricing: Launch: usage-based, no monthly minimum ($0.106/CU-hour, $0.35/GB-month).
Is Convex free?
Convex free tier: Yes: Free plan with hard resource caps. Paid pricing: Professional $25/developer/mo; Starter $0 base plus pay-as-you-go.
Is Prisma Postgres free?
Prisma Postgres free tier: Yes: 200K operations/mo, 2 GB storage, 50 databases, no card. Paid pricing: Starter $10/mo (1M operations, then $8 per million; 10 GB, then $2/GB; spend limits); Pro $49/mo (10M ops, 50 GB); Business $129/mo (50M ops, 100 GB, HIPAA/SOC 2).
How are these tools ranked?
Each tool is scored out of 100 on fit, vibe-coder friendliness, output quality, pricing, ecosystem, momentum and code ownership, using desk research of official docs and pricing pages. Affiliate status never affects scores.
What is the best alternative to Supabase?
Neon, at 86 in our ranking, if you want to keep Postgres: its Free plan has no time limit, 100 projects and scale-to-zero compute, and it now adds Managed Better Auth, object storage and functions. Convex (84) is the pick for a reactive TypeScript backend, and Appwrite (80) for an open-source all-in-one with a Supabase migration wizard.
Is there a free Supabase alternative that doesn’t pause after a week?
Supabase and Nhost both pause free projects after a week of inactivity. Neon’s Free plan has no time limit and scales compute to zero after 5 minutes idle, and Prisma Postgres Free is free forever with no card and also scales to zero when idle. PocketBase is free to self-host on your own server.
Can I self-host Supabase for free?
Yes. Supabase is open source and its docs recommend Docker Compose. A self-hosted install runs as a single project and lacks branching, managed backups and point-in-time recovery, and the Management API, and you handle security updates, backups and uptime yourself.
How do I migrate from Supabase to Neon?
Neon’s guide uses pg_dump in custom format (-Fc) on your Supabase database, then pg_restore into a Neon project on the same Postgres version. Use an unpooled connection string, and add --schema flags if you also need auth or storage tables. For near-zero downtime, Neon documents logical replication from Supabase.
Can I move Supabase Auth users without resetting passwords?
Usually, yes. Supabase stores password hashes with bcrypt in the encrypted_password column of auth.users, so a target that imports bcrypt hashes (Firebase’s auth:import accepts BCRYPT, for example) can keep passwords working. In Appwrite’s Supabase migration, OAuth users are not migrated and sign in again.

Sources (checked Oct 17, 2026)

Related guides

Official sites

Related guides

See the full category ranking · How we score