Skip to content

Open-source Firebase alternatives

A Firebase replacement is a set of backend decisions. An app using Firestore, Authentication, Storage and Functions needs more than a new database. Inventory those dependencies before choosing a platform; replacing the SDK alone will not migrate your application.

Supabase has the most GitHub stars in this list (115k, Apache-2.0). Supabase, PocketBase, and Appwrite can be self-hosted. Supabase and Appwrite list a hosted option.

Compare the set

Available Firebase alternatives

Which Firebase alternative should you choose?

Evaluate Supabase when you want a Postgres foundation, Appwrite when you want application services behind its APIs, and PocketBase for a compact backend with an embedded database. Choose around your data model, access rules and operating capacity, then prototype one real workflow.

Editorial guide reviewed October 7, 2026. Based on project documentation, not hands-on benchmarks. Catalog metadata last checked November 20, 2026.

Compare Firebase alternatives by use case

Editorial shortlist: use case, tradeoffs, catalog license and hosting
AlternativeConsider it forCheck before choosingLicense / hosting
Supabase

Postgres with application services

Combines a relational database with services including authentication and storage. Its self-hosting guide documents the platform components.

Firestore documents and security rules do not become SQL tables and access policies automatically. Self-hosting also makes your team responsible for the services it runs.

Apache-2.0

Both

Official source for Supabase (opens in a new tab)
Appwrite

Backend services through application APIs

Offers a self-hosting path for applications using its backend APIs, rather than asking you to assemble every service yourself.

Verify each Firebase dependency against the Appwrite service you would use. Client calls, permissions and function deployment need an application migration.

BSD-3-Clause

Both

Official source for Appwrite (opens in a new tab)

Selection is by workflow fit, not sponsorship or star count. Licenses and paid features can differ by edition; check the linked source for the version you plan to use.

Compare Firebase replacements service by service

Documented capabilities and migration checks. Confirm the version and edition you plan to run.

Compare Firebase replacements service by service, with official sources for each tool
What to compareSupabaseAppwrite
Data model

Postgres tables and SQL. Map Firestore documents, nested collections and references into a relational schema.

Official source for Supabase: Data model (opens in a new tab)

Data behind Appwrite APIs. Check the database APIs available in your self-hosted version; hosted documentation can describe newer services.

Official source for Appwrite: Data model (opens in a new tab)
Sign-in

Auth supports passwords, passwordless sign-in and identity providers. Map account identifiers and reconfigure provider callbacks.

Official source for Supabase: Sign-in (opens in a new tab)

Auth supports email/password, OAuth and passwordless flows. Test the methods your application uses on the version you deploy.

Official source for Appwrite: Sign-in (opens in a new tab)
Files

Storage uses buckets with access policies. Copy file bytes as well as metadata, then test private downloads.

Official source for Supabase: Files (opens in a new tab)

Storage provides file APIs and buckets. Rebuild upload/download calls and file permissions.

Official source for Appwrite: Files (opens in a new tab)
Live updates

Realtime includes Broadcast, Presence and Postgres Changes. Replace listeners deliberately; test reconnects and access control.

Official source for Supabase: Live updates (opens in a new tab)

Realtime subscriptions deliver resource events over WebSockets and respect permissions. Rewrite Firebase listener subscriptions.

Official source for Appwrite: Live updates (opens in a new tab)
Access rules

Postgres grants and row-level security control table access. Translate Firebase rules and test both permitted and denied requests.

Official source for Supabase: Access rules (opens in a new tab)

Permissions identify users and teams allowed to access resources. Verify permissions with normal client sessions, not only an administrator.

Official source for Appwrite: Access rules (opens in a new tab)
Operating the backend

Run and maintain the platform services, database, backups and monitoring. Managed-platform features are not all included in self-hosting.

Official source for Supabase: Operating the backend (opens in a new tab)

Operate a self-hosted deployment and its dependencies. Check release compatibility, capacity and backup procedures before cutover.

Official source for Appwrite: Operating the backend (opens in a new tab)

Before switching from Firebase

  1. List every Firebase service in use. Record queries, indexes, listeners, sign-in providers, file permissions and triggered functions, including dependencies hidden in background jobs.
  2. Model one representative dataset in the new backend. Test access control and your hardest queries before building a bulk importer; document relationships and transactions may need redesign.
  3. Plan account migration separately. Confirm supported user exports, password handling and provider identifiers in the destination's current documentation. Do not assume existing sessions will survive.
  4. Pilot a complete workflow: sign in, create a record, upload a file and receive a realtime update. Verify backups and restores, then define a cutover and rollback plan before moving production traffic.

A small Firebase migration rehearsal

Use this proposed acceptance test with synthetic data in an isolated test environment. It is a migration plan, not a benchmark we have run against these products.

  1. Create two test accounts, Alice and Bob, and three documents owned by Alice. Attach one private image to a document and record its checksum. Keep a mapping from the old account and document IDs to the new IDs.
  2. Import the three records and the image. Verify record counts, ownership, timestamps and the image checksum. Run the importer a second time: it should still leave three records, not six.
  3. Using ordinary client sessions, confirm Alice can read and update her records. Confirm Bob and a signed-out visitor cannot read, edit or download Alice's private content. Do not test only with server credentials that bypass access rules.
  4. Subscribe from a second client, change a record, disconnect and reconnect. Check that the client receives the update and recovers its current state; record any difference from your Firebase listener behavior.
  5. Restore a backup into a fresh test instance and repeat the ownership and file checks. Record target versions and actual results before deciding whether to migrate production traffic.

Related categories

Compare alternatives

Related collections

Firebase alternatives: questions

Which open-source Firebase alternative should I start with?
Start with your data model: evaluate Supabase for Postgres, Appwrite for its backend service APIs, or PocketBase for a compact embedded backend. Check the specific services your app uses before choosing.
Can I keep my Firebase client code unchanged?
Do not assume SDK compatibility. Query APIs, authentication, permissions and function triggers can differ. Prototype a representative workflow and budget for application changes.
Is a self-hosted Firebase alternative cheaper?
A license does not cover infrastructure, backups, updates or your team's operating time. Compare those costs with your current usage, and include migration work rather than treating self-hosting as automatically cheaper.
Which Firebase alternatives can be self-hosted?
Supabase, PocketBase, and Appwrite are marked self-hostable in this catalog.
Which Firebase alternatives list a hosted option?
Supabase and Appwrite list a hosted or cloud option.

Repository activity is a signal, not a security or quality guarantee.