A
pentagi
95.4
34,396 stars · MIT
Self-Hosted
uptime-kuma leads by 2.5 · narrow
A
95.4
34,396 stars · MIT
B · leads
97.9
94,538 stars · MIT
pentagi 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. pentagi is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 95.4 for pentagi and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to pentagi's 34,396, a gap of 60,142 (2.75×). Forks are 5,447 for pentagi and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 95 versus 100.
Push history: pentagi was last pushed on 13 November 2026 (3 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 76 for pentagi (0.002 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both pentagi 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 pentagi (34,396 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: pentagi is open source, uptime-kuma is open source.
The lead is split. pentagi is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on adoption (100 to 91). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against pentagi at 95.4, a 2.5 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 | pentagi | uptime-kuma |
|---|---|---|
| GitHub stars | 34,396 | 94,538 |
| Forks | 5,447 | 8,860 |
| Open issues | 76 | 852 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.4 | 97.9 |
Fully autonomous AI Agents system capable of performing complex penetration testing tasks
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 34,396 for pentagi. The gap is 60,142 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 13 November 2026 for pentagi. That is 3 days apart.
Yes. This catalog marks both pentagi and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
pentagi 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 pentagi scores 95.4. This page calls that a narrow lead for uptime-kuma.