A · leads
Appwrite
97.9
58,177 stars · BSD-3-Clause
Self-Hosted
Appwrite leads by 9.2 · clear
A · leads
97.9
58,177 stars · BSD-3-Clause
B
88.7
8,995 stars · Apache-2.0
Appwrite versus rakazo is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 97.9 for Appwrite and 88.7 for rakazo.
Appwrite has 58,177 GitHub stars to rakazo's 8,995, a gap of 49,182 (6.47×). Forks are 5,897 for Appwrite and 1,614 for rakazo. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 85.
Push history: Appwrite was last pushed on 17 November 2026 (0 days ago), and rakazo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 744 for Appwrite (0.013 per star) and 236 for rakazo (0.026 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
Appwrite is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. rakazo is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for Appwrite and 96 for rakazo. This is a procurement signal, not legal advice.
In Self-Hosted, both Appwrite (58,177 stars) and rakazo (8,995 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Appwrite is freemium, rakazo is open source.
Appwrite is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is adoption at 17 points (100 vs 83), and the tightest is self-hosting at 0 points (100 vs 100).
Appwrite finishes ahead at 97.9 against rakazo at 88.7, a 9.2 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Appwrite | rakazo |
|---|---|---|
| GitHub stars | 58,177 | 8,995 |
| Forks | 5,897 | 1,614 |
| Open issues | 744 | 236 |
| Adoption | 100 | 83 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 88.7 |
Appwrite is a backend server for auth, databases, storage, and functions. It is built for product teams that want a self-hosted alternative to a proprietary backend-as-a-service.
Open-source Grok Bot alternative. Choose your own model and sandbox.
Appwrite has more GitHub stars: 58,177 versus 8,995 for rakazo. The gap is 49,182 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Appwrite and rakazo as self-hostable. Confirm each project's deploy docs before you plan a migration.
Appwrite is listed as BSD-3-Clause, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. rakazo is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Appwrite scores 97.9 and rakazo scores 88.7. This page calls that a clear lead for Appwrite.