A
Kavita
84.1
12,145 stars · GPL-3.0
Self-Hosted
uptime-kuma leads by 13.8 · clear
A
84.1
12,145 stars · GPL-3.0
B · leads
97.9
94,538 stars · MIT
Kavita 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. Kavita is written mainly in C#; uptime-kuma is written mainly in JavaScript. The composite score is 84.1 for Kavita and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to Kavita's 12,145, a gap of 82,393 (7.78×). Forks are 704 for Kavita and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 72 versus 100.
Push history: Kavita was last pushed on 15 November 2026 (1 day ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 165 for Kavita (0.014 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Kavita 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 Kavita and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both Kavita (12,145 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: Kavita 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, 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 Kavita at 84.1, a 13.8 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 | Kavita | uptime-kuma |
|---|---|---|
| GitHub stars | 12,145 | 94,538 |
| Forks | 704 | 8,860 |
| Open issues | 165 | 852 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 72 | 100 |
| Issue health | 84 | 84 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.1 | 97.9 |
Kavita is a fast, feature rich, cross platform reading server. Built with the goal of being a full solution for all your reading needs. Setup your own server and share your reading collection with your friends and family.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 12,145 for Kavita. The gap is 82,393 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 15 November 2026 for Kavita. That is 1 days apart.
Yes. This catalog marks both Kavita and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
Kavita 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 Kavita scores 84.1. This page calls that a clear lead for uptime-kuma.