A
blinko
80.9
11,223 stars · GPL-3.0
Self-Hosted
uptime-kuma leads by 17.0 · decisive
A
80.9
11,223 stars · GPL-3.0
B · leads
97.9
94,538 stars · MIT
blinko 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. blinko is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 80.9 for blinko and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to blinko's 11,223, a gap of 83,315 (8.42×). Forks are 805 for blinko and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 74 versus 100.
Push history: blinko was last pushed on 05 November 2026 (12 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 438 for blinko (0.039 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; 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. 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. License scores in this pair are 64 for blinko and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both blinko (11,223 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: blinko is open source, uptime-kuma is open source.
uptime-kuma 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).
uptime-kuma finishes ahead at 97.9 against blinko at 80.9, a 17.0 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 | uptime-kuma |
|---|---|---|
| GitHub stars | 11,223 | 94,538 |
| Forks | 805 | 8,860 |
| Open issues | 438 | 852 |
| Adoption | 81 | 100 |
| Activity | 92 | 100 |
| Community | 74 | 100 |
| Issue health | 70 | 84 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 80.9 | 97.9 |
An open-source, self-hosted personal AI note tool prioritizing privacy, built using TypeScript .
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 11,223 for blinko. The gap is 83,315 stars.
uptime-kuma 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 uptime-kuma 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. 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.
uptime-kuma scores 97.9 and blinko scores 80.9. This page calls that a decisive lead for uptime-kuma.