A
blinko
82.6
11,223 stars · GPL-3.0
Self-Hosted
memos leads by 16.5 · decisive
A
82.6
11,223 stars · GPL-3.0
B · leads
99.1
64,520 stars · MIT
blinko versus memos is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. blinko is written mainly in TypeScript; memos is written mainly in Go. The composite score is 82.6 for blinko and 99.1 for memos.
memos has 64,520 GitHub stars to blinko's 11,223, a gap of 53,297 (5.75×). Forks are 805 for blinko and 4,972 for memos. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 79 versus 100.
Push history: blinko was last pushed on 05 November 2026 (12 days ago), and memos was last pushed on 17 November 2026 (0 days ago). Open issues stand at 438 for blinko (0.039 per star) and 63 for memos (0.001 per star). Issue-health scores are 70 and 96; activity scores are 92 and 100.
blinko 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. 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 64 for blinko and 96 for memos. This is a procurement signal, not legal advice.
In Self-Hosted, both blinko (11,223 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: blinko is open source, memos is open source.
memos is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
memos finishes ahead at 99.1 against blinko at 82.6, a 16.5 point decisive 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 | blinko | memos |
|---|---|---|
| GitHub stars | 11,223 | 64,520 |
| Forks | 805 | 4,972 |
| Open issues | 438 | 63 |
| Adoption | 84 | 100 |
| Activity | 92 | 100 |
| Community | 79 | 100 |
| Issue health | 70 | 96 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.6 | 99.1 |
An open-source, self-hosted personal AI note tool prioritizing privacy, built using TypeScript .
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 11,223 for blinko. The gap is 53,297 stars.
memos was pushed more recently: 17 November 2026 versus 05 November 2026 for blinko. That is 12 days apart.
Yes. This catalog marks both blinko and memos as self-hostable. Confirm each project's deploy docs before you plan a migration.
blinko 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. 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 99.1 and blinko scores 82.6. This page calls that a decisive lead for memos.