A · leads
Appwrite
97.9
58,177 stars · BSD-3-Clause
Self-Hosted
Appwrite leads by 10.5 · clear
A · leads
97.9
58,177 stars · BSD-3-Clause
B
87.4
15,696 stars · AGPL-3.0
Appwrite versus TREK 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 87.4 for TREK.
Appwrite has 58,177 GitHub stars to TREK's 15,696, a gap of 42,481 (3.71×). Forks are 5,897 for Appwrite and 1,342 for TREK. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 83.
Push history: Appwrite was last pushed on 17 November 2026 (0 days ago), and TREK was last pushed on 17 November 2026 (0 days ago). Open issues stand at 744 for Appwrite (0.013 per star) and 19 for TREK (0.001 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. TREK is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for Appwrite and 52 for TREK. This is a procurement signal, not legal advice.
In Self-Hosted, both Appwrite (58,177 stars) and TREK (15,696 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, TREK is open source.
The lead is split. Appwrite is furthest ahead on license flexibility (96 to 52), while TREK is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Appwrite finishes ahead at 97.9 against TREK at 87.4, a 10.5 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 | TREK |
|---|---|---|
| GitHub stars | 58,177 | 15,696 |
| Forks | 5,897 | 1,342 |
| Open issues | 744 | 19 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 84 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 87.4 |
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.
The most complete open-source travel planner: real-time collaboration, bookings, budgets, packing lists, journals, offline PWA, SSO and an AI-ready MCP server, with planet-wide place search and routing built in.
Appwrite has more GitHub stars: 58,177 versus 15,696 for TREK. The gap is 42,481 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Appwrite and TREK 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. TREK is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Appwrite scores 97.9 and TREK scores 87.4. This page calls that a clear lead for Appwrite.