A
neko
91.1
22,688 stars · Apache-2.0
Self-Hosted
uptime-kuma leads by 6.8 · narrow
A
91.1
22,688 stars · Apache-2.0
B · leads
97.9
94,538 stars · MIT
neko 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. neko is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 91.1 for neko and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to neko's 22,688, a gap of 71,850 (4.17×). Forks are 1,662 for neko and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 82 versus 100.
Push history: neko was last pushed on 16 November 2026 (1 day ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 144 for neko (0.006 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. 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 96 for neko and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both neko (22,688 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: neko is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 18 points (82 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against neko at 91.1, a 6.8 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 | neko | uptime-kuma |
|---|---|---|
| GitHub stars | 22,688 | 94,538 |
| Forks | 1,662 | 8,860 |
| Open issues | 144 | 852 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.1 | 97.9 |
A self hosted virtual browser that runs in docker and uses WebRTC.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 22,688 for neko. The gap is 71,850 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 16 November 2026 for neko. That is 1 days apart.
Yes. This catalog marks both neko and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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 neko scores 91.1. This page calls that a narrow lead for uptime-kuma.