- Status:
- Active
- Momentum:
- Star growth:
- +0.012%/day
- Open issues:
- +6 since 2026-10-01
- Contributor growth:
- +4 since 2026-10-01
- License:
- BSD-3-Clause
- Category:
- backend, database, self-hosted
Direct alternative to:SupabasePocketBaseFirebaseAWS Amplify
- Stargazers
- 57,537+7 / 1d
- Forks
- 5,757
- Contributors
- 536
- Open issues
- 684
57,537 stars · +7 stars / 1 day · tracking since
Self-hostable backend-as-a-service: auth, databases, storage, functions, and messaging behind one API.
What it does
Appwrite packages the pieces a typical app backend needs — authentication, a document database, file storage, serverless functions, and messaging — into one platform you either self-host via Docker or run on Appwrite's managed cloud, all behind a single set of client SDKs.
Why people use it
- One consistent API surface across auth, database, storage, and functions
- Runs the same self-hosted or on Appwrite's managed cloud, so teams can start managed and migrate later without a rewrite
- Broad SDK coverage across web, mobile, and server-side languages
Pros
- Wide feature surface for a single platform (auth, DB, storage, functions, messaging)
- Active development and a large contributor base
- Self-hosting via Docker is well documented
Cons
- More moving parts to operate self-hosted than a single-binary alternative like PocketBase
- Its own document-style database, not raw SQL, unlike Supabase's Postgres
Alternatives
| Project | Status | Stars | Category |
|---|---|---|---|
| Supabase | Active | 110,999 | backend |
| PocketBase | Active | 61,240 | backend |
Commercial alternatives
How it compares
Side-by-side facts against the alternatives we've profiled.
| Parameter | Appwrite | Supabase | PocketBase |
|---|---|---|---|
| Stars | 57,537 | 110,999 | 61,240 |
| Contributors | 536 | 2,060 | 45 |
| Forks | 5,757 | 15,476 | 3,717 |
| Status | Active | Active | Active |
| License | BSD-3-Clause | Apache-2.0 | MIT |