A · leads
Appwrite
97.9
58,177 stars · BSD-3-Clause
Self-Hosted
Appwrite leads by 14.2 · clear
A · leads
97.9
58,177 stars · BSD-3-Clause
B
83.7
10,433 stars · GPL-3.0
Appwrite versus feishin 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 83.7 for feishin.
Appwrite has 58,177 GitHub stars to feishin's 10,433, a gap of 47,744 (5.58×). Forks are 5,897 for Appwrite and 609 for feishin. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 74.
Push history: Appwrite was last pushed on 17 November 2026 (0 days ago), and feishin was last pushed on 16 November 2026 (1 day ago). Open issues stand at 744 for Appwrite (0.013 per star) and 329 for feishin (0.032 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. feishin is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for Appwrite and 64 for feishin. This is a procurement signal, not legal advice.
In Self-Hosted, both Appwrite (58,177 stars) and feishin (10,433 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, feishin is open source.
Appwrite is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 32 points (96 vs 64), and the tightest is self-hosting at 0 points (100 vs 100).
Appwrite finishes ahead at 97.9 against feishin at 83.7, a 14.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 | feishin |
|---|---|---|
| GitHub stars | 58,177 | 10,433 |
| Forks | 5,897 | 609 |
| Open issues | 744 | 329 |
| Adoption | 100 | 84 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 84 | 70 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 83.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.
A modern self-hosted music player.
Appwrite has more GitHub stars: 58,177 versus 10,433 for feishin. The gap is 47,744 stars.
Appwrite was pushed more recently: 17 November 2026 versus 16 November 2026 for feishin. That is 1 days apart.
Yes. This catalog marks both Appwrite and feishin 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. feishin is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Appwrite scores 97.9 and feishin scores 83.7. This page calls that a clear lead for Appwrite.