Appwrite vs Nhost
Both are alternatives to Firebase. Here's how they stack up — verified facts, no spin.
Also searched as Nhost vs Appwrite — same comparison, one verdict.
Appwrite
The self-hosted backend that ships as one Docker command.
Appwrite bundles databases, authentication with 30-plus OAuth providers, storage, serverless functions and realtime into a product designed from the start to be self-hosted — one `docker compose up` and you have the whole backend running on your own machine. Where Supabase leads with Postgres, Appwrite leads with operational simplicity, and the SDK coverage across Flutter, web, Apple and Android is unusually complete. BSD-3-Clause, around 56.7k stars. It is the pick when you want to own the whole stack without becoming a database administrator to do it.
Nhost
Postgres plus instant GraphQL, for teams that think in queries.
Nhost pairs Postgres with Hasura to give you a GraphQL API generated straight from your schema, alongside authentication, storage and serverless functions. If your front end is React or Vue and your team already prefers GraphQL to REST, this is the shortest path from a database table to a typed query in the client. MIT, self-hostable, with a hosted tier. It is the smallest project here at around 9.3k stars, which is the caveat — the technology is sound and the ecosystem is thin.
Side by side
| Appwrite | Nhost | |
|---|---|---|
| Sovereignty Score | 92 | 88 |
| Open source | Yes | Yes |
| Self-hostable | Yes | Yes |
| Local-first | Yes | Yes |
| License | BSD-3-Clause | MIT |
| Pricing | Free and open source to self-host. Appwrite Cloud has a free tier and paid plans from about $15/month. | Free tier available; hosted plans from about $25/month. Self-hostable at no licence cost. |
Appwrite edges it on the Sovereignty Score, but the right pick depends on the trade-offs below.
Appwrite
Strengths
- +Self-hosts in a single Docker Compose command — the lowest-friction option here
- +Excellent SDK coverage including Flutter, Apple and Android
- +Permissive BSD-3-Clause with no enterprise directory carve-out
- +Auth, storage, functions and realtime all in one binary set
Trade-offs
- −Its own database abstraction rather than raw Postgres — less portable data
- −Smaller ecosystem and fewer third-party integrations than Supabase
- −Query capability is thinner than SQL when the data model gets complex
- −Scaling beyond a single node needs planning
Nhost
Strengths
- +Instant GraphQL from your Postgres schema via Hasura
- +Real Postgres underneath, so the data stays portable
- +MIT licensed with a genuine self-host path
- +Strong typed-client story for React and Vue front ends
Trade-offs
- −Much smaller community than Supabase or Appwrite
- −GraphQL-first is a commitment, not a neutral default
- −Self-hosting means running Hasura and Postgres, not one binary
- −Fewer SDKs, and mobile support lags the others
Related alternative guides
Facts verified 2026-07-31. Licenses and pricing change — spotted something out of date? That's a correction we want.