A · level
memos
97.1
64,520 stars · MIT
Self-Hosted
Too close to call · 97.1 to 97.9
A · level
97.1
64,520 stars · MIT
B · level
97.9
94,538 stars · MIT
memos versus uptime-kuma is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. memos is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 97.1 for memos and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to memos's 64,520, a gap of 30,018 (1.47×). Forks are 4,972 for memos and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 94 versus 100.
Push history: memos was last pushed on 17 November 2026 (0 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 63 for memos (0.001 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both memos and uptime-kuma are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both memos (64,520 stars) and uptime-kuma (94,538 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, uptime-kuma is open source.
The lead is split. memos is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on fork community (100 to 94). Choose the dimension a rollout cannot compromise on.
Composite score: memos 97.1, uptime-kuma 97.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | uptime-kuma |
|---|---|---|
| GitHub stars | 64,520 | 94,538 |
| Forks | 4,972 | 8,860 |
| Open issues | 63 | 852 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.1 | 97.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 fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 64,520 for memos. The gap is 30,018 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both memos and uptime-kuma 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. uptime-kuma 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.
Neither tool clears a one-point margin. memos scores 97.1 and uptime-kuma scores 97.9.