A · leads
Appwrite
97.9
58,177 stars · BSD-3-Clause
Self-Hosted
Appwrite leads by 4.9 · narrow
A · leads
97.9
58,177 stars · BSD-3-Clause
B
93.0
22,688 stars · Apache-2.0
Appwrite versus neko is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Appwrite is written mainly in TypeScript; neko is written mainly in Go. The composite score is 97.9 for Appwrite and 93.0 for neko.
Appwrite has 58,177 GitHub stars to neko's 22,688, a gap of 35,489 (2.56×). Forks are 5,897 for Appwrite and 1,662 for neko. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 85.
Push history: Appwrite was last pushed on 17 November 2026 (0 days ago), and neko was last pushed on 16 November 2026 (1 day ago). Open issues stand at 744 for Appwrite (0.013 per star) and 144 for neko (0.006 per star). Issue-health scores are 84 and 84; 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. neko 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 neko. This is a procurement signal, not legal advice.
In Self-Hosted, both Appwrite (58,177 stars) and neko (22,688 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, neko is open source.
Appwrite is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 15 points (100 vs 85), and the tightest is self-hosting at 0 points (100 vs 100).
Appwrite finishes ahead at 97.9 against neko at 93.0, a 4.9 point narrow 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 | neko |
|---|---|---|
| GitHub stars | 58,177 | 22,688 |
| Forks | 5,897 | 1,662 |
| Open issues | 744 | 144 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 93.0 |
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 self hosted virtual browser that runs in docker and uses WebRTC.
Appwrite has more GitHub stars: 58,177 versus 22,688 for neko. The gap is 35,489 stars.
Appwrite was pushed more recently: 17 November 2026 versus 16 November 2026 for neko. That is 1 days apart.
Yes. This catalog marks both Appwrite and neko 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. neko 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 neko scores 93.0. This page calls that a narrow lead for Appwrite.