A · level
Appwrite
97.9
58,177 stars · BSD-3-Clause
Self-Hosted
Too close to call · 97.9 to 98.1
A · level
97.9
58,177 stars · BSD-3-Clause
B · level
98.1
45,854 stars · MIT
Appwrite versus reactive-resume 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 98.1 for reactive-resume.
Appwrite has 58,177 GitHub stars to reactive-resume's 45,854, a gap of 12,323 (1.27×). Forks are 5,897 for Appwrite and 4,959 for reactive-resume. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 98.
Push history: Appwrite was last pushed on 17 November 2026 (0 days ago), and reactive-resume was last pushed on 16 November 2026 (1 day ago). Open issues stand at 744 for Appwrite (0.013 per star) and 7 for reactive-resume (0.000 per star). Issue-health scores are 84 and 96; 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. reactive-resume is listed as MIT, 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 reactive-resume. This is a procurement signal, not legal advice.
In Self-Hosted, both Appwrite (58,177 stars) and reactive-resume (45,854 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, reactive-resume is open source.
The lead is split. Appwrite is furthest ahead on adoption (100 to 98), while reactive-resume is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Composite score: Appwrite 97.9, reactive-resume 98.1. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | reactive-resume |
|---|---|---|
| GitHub stars | 58,177 | 45,854 |
| Forks | 5,897 | 4,959 |
| Open issues | 744 | 7 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 98.1 |
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.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
Appwrite has more GitHub stars: 58,177 versus 45,854 for reactive-resume. The gap is 12,323 stars.
Appwrite was pushed more recently: 17 November 2026 versus 16 November 2026 for reactive-resume. That is 1 days apart.
Yes. This catalog marks both Appwrite and reactive-resume 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. reactive-resume is listed as MIT, 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.
Neither tool clears a one-point margin. Appwrite scores 97.9 and reactive-resume scores 98.1.