A
pangolin
82.3
23,827 stars · license n/a
Self-Hosted
uptime-kuma leads by 15.6 · decisive
A
82.3
23,827 stars · license n/a
B · leads
97.9
94,538 stars · MIT
pangolin 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. pangolin is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 82.3 for pangolin and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to pangolin's 23,827, a gap of 70,711 (3.97×). Forks are 840 for pangolin and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 74 versus 100.
Push history: pangolin 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 135 for pangolin (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.
pangolin is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for pangolin and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both pangolin (23,827 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: pangolin is unpriced in this catalog, 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 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against pangolin at 82.3, a 15.6 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 | pangolin | uptime-kuma |
|---|---|---|
| GitHub stars | 23,827 | 94,538 |
| Forks | 840 | 8,860 |
| Open issues | 135 | 852 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.3 | 97.9 |
Modern networking and security platform providing secure access and connectivity to apps, infrastructure, and AI workloads. Connect and protect your users.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 23,827 for pangolin. The gap is 70,711 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both pangolin and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
pangolin is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 pangolin scores 82.3. This page calls that a decisive lead for uptime-kuma.