A · leads
memos
99.1
64,520 stars · MIT
Self-Hosted
memos leads by 6.2 · narrow
A · leads
99.1
64,520 stars · MIT
B
92.9
22,688 stars · Apache-2.0
memos versus neko 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 Go. The composite score is 99.1 for memos and 92.9 for neko.
memos has 64,520 GitHub stars to neko's 22,688, a gap of 41,832 (2.84×). Forks are 4,972 for memos 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 87.
Push history: memos 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 63 for memos (0.001 per star) and 144 for neko (0.006 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. 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 memos and 96 for neko. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 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: memos is open source, neko is open source.
memos is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 13 points (100 vs 87), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against neko at 92.9, a 6.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 | memos | neko |
|---|---|---|
| GitHub stars | 64,520 | 22,688 |
| Forks | 4,972 | 1,662 |
| Open issues | 63 | 144 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 92.9 |
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.
A self hosted virtual browser that runs in docker and uses WebRTC.
memos has more GitHub stars: 64,520 versus 22,688 for neko. The gap is 41,832 stars.
memos was pushed more recently: 17 November 2026 versus 16 November 2026 for neko. That is 1 days apart.
Yes. This catalog marks both memos and neko as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
memos scores 99.1 and neko scores 92.9. This page calls that a narrow lead for memos.