A
Appwrite
97.6
58,177 stars · BSD-3-Clause
Self-Hosted
memos leads by 1.2 · narrow
A
97.6
58,177 stars · BSD-3-Clause
B · leads
98.8
64,520 stars · MIT
Appwrite versus memos 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; memos is written mainly in Go. The composite score is 97.6 for Appwrite and 98.8 for memos.
memos has 64,520 GitHub stars to Appwrite's 58,177, a gap of 6,343 (1.11×). Forks are 5,897 for Appwrite and 4,972 for memos. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 98.
Push history: Appwrite was last pushed on 17 November 2026 (0 days ago), and memos was last pushed on 17 November 2026 (0 days ago). Open issues stand at 744 for Appwrite (0.013 per star) and 63 for memos (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. memos 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 memos. This is a procurement signal, not legal advice.
In Self-Hosted, both Appwrite (58,177 stars) and memos (64,520 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, memos is open source.
The lead is split. Appwrite is furthest ahead on fork community (100 to 98), while memos is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
memos finishes ahead at 98.8 against Appwrite at 97.6, a 1.2 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 | memos |
|---|---|---|
| GitHub stars | 58,177 | 64,520 |
| Forks | 5,897 | 4,972 |
| Open issues | 744 | 63 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.6 | 98.8 |
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.
Memos is an open-source, self-hosted note-taking app that brings your everyday thoughts together in a personal timeline. Your data stays yours, and you choose what to keep private or share.
memos has more GitHub stars: 64,520 versus 58,177 for Appwrite. The gap is 6,343 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Appwrite and memos 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. memos 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.
memos scores 98.8 and Appwrite scores 97.6. This page calls that a narrow lead for memos.