A
Suwayomi-Server
80.9
8,075 stars · MPL-2.0
Self-Hosted
uptime-kuma leads by 17.0 · decisive
A
80.9
8,075 stars · MPL-2.0
B · leads
97.9
94,538 stars · MIT
Suwayomi-Server 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. Suwayomi-Server is written mainly in Java; uptime-kuma is written mainly in JavaScript. The composite score is 80.9 for Suwayomi-Server and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to Suwayomi-Server's 8,075, a gap of 86,463 (11.71×). Forks are 499 for Suwayomi-Server and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 78 versus 100, and the fork community is 68 versus 100.
Push history: Suwayomi-Server was last pushed on 12 November 2026 (5 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 216 for Suwayomi-Server (0.027 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; activity scores are 92 and 100.
Suwayomi-Server is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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 78 for Suwayomi-Server and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both Suwayomi-Server (8,075 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: Suwayomi-Server 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 fork community at 32 points (68 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against Suwayomi-Server 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 | Suwayomi-Server | uptime-kuma |
|---|---|---|
| GitHub stars | 8,075 | 94,538 |
| Forks | 499 | 8,860 |
| Open issues | 216 | 852 |
| Adoption | 78 | 100 |
| Activity | 92 | 100 |
| Community | 68 | 100 |
| Issue health | 70 | 84 |
| License | 78 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 80.9 | 97.9 |
A rewrite of Tachiyomi for the Desktop
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 8,075 for Suwayomi-Server. The gap is 86,463 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 12 November 2026 for Suwayomi-Server. That is 5 days apart.
Yes. This catalog marks both Suwayomi-Server and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
Suwayomi-Server is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. 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 Suwayomi-Server scores 80.9. This page calls that a decisive lead for uptime-kuma.