A
kaneo
87.8
9,819 stars · MIT
Self-Hosted
uptime-kuma leads by 10.1 · clear
A
87.8
9,819 stars · MIT
B · leads
97.9
94,538 stars · MIT
kaneo 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. kaneo is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 87.8 for kaneo and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to kaneo's 9,819, a gap of 84,719 (9.63×). Forks are 963 for kaneo and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 76 versus 100.
Push history: kaneo 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 83 for kaneo (0.008 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both kaneo 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 kaneo (9,819 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: kaneo 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 24 points (76 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against kaneo at 87.8, a 10.1 point clear 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 | kaneo | uptime-kuma |
|---|---|---|
| GitHub stars | 9,819 | 94,538 |
| Forks | 963 | 8,860 |
| Open issues | 83 | 852 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 76 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.8 | 97.9 |
⚡ Project management that doesn't become the project. Boards, Gantt charts, and GitHub integration. Self-host it or use Kaneo Cloud.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 9,819 for kaneo. The gap is 84,719 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both kaneo and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
kaneo 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.
uptime-kuma scores 97.9 and kaneo scores 87.8. This page calls that a clear lead for uptime-kuma.