Self-hosted alternatives to Firebase
Vendor lock-in is total: the data model, the auth, and the functions are all unportable by design.
Below are 2 open-source projects that cover the same ground, each scored 0–100 on how actively it is actually maintained — commit volume, release cadence and recent trend. 2 of the 2 are currently rated healthy or better. Ordering reflects that score, not sponsorship.
| Project | Health | Activity (11 mo) | Stars | Licence | Last release |
|---|---|---|---|---|---|
| Appwrite End to end backend server for web, native, and mobile developers 🚀. | Thriving · 96 | 57k | BSD-3-Clause | 23 Sept 2026 | |
| PocketBase Backend for your next SaaS and Mobile app in one file. | Healthy · 78 | 61k | MIT | 12 Sept 2026 |
How these were picked
Every project listed here is open source and can run entirely on hardware you control. We start from the categories that match Firebase's job — then rank by health score so that a popular-but-abandoned project never appears above a smaller one that is actively shipping. The scoring method is documented in full.
The scores are recomputed from repository data on every rebuild, so this page reflects the state of these projects as of 1 Oct 2026 — not the day it was written.
Appwrite
End to end backend server for web, native, and mobile developers 🚀.
Best fit: Developers looking to consolidate common backend services into a single self-hosted stack rather than piecing together multiple disparate tools.
Worth knowing: Self-hosting a comprehensive backend server introduces significant operational overhead for maintenance, security updates, and scaling.
PocketBase
Backend for your next SaaS and Mobile app in one file.
Best fit: Developers building lightweight SaaS products or mobile applications who want to avoid managing complex multi-service backend architectures.
Worth knowing: The all-in-one approach may lead to scaling limitations or tight coupling as your application logic and data models grow significantly more complex.