A
server
81.3
16,219 stars · license n/a
Self-Hosted
uptime-kuma leads by 16.6 · decisive
A
81.3
16,219 stars · license n/a
B · leads
97.9
94,538 stars · MIT
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. server is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 81.3 for server and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to server's 16,219, a gap of 78,319 (5.83×). Forks are 900 for server and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 75 versus 100.
Push history: server was last pushed on 14 November 2026 (3 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 90 for server (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.
server 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 server and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both server (16,219 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: server 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 server at 81.3, a 16.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 | server | uptime-kuma |
|---|---|---|
| GitHub stars | 16,219 | 94,538 |
| Forks | 900 | 8,860 |
| Open issues | 90 | 852 |
| Adoption | 85 | 100 |
| Activity | 100 | 100 |
| Community | 75 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 81.3 | 97.9 |
A simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui)
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 16,219 for server. The gap is 78,319 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 14 November 2026 for server. That is 3 days apart.
Yes. This catalog marks both server and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
server 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 server scores 81.3. This page calls that a decisive lead for uptime-kuma.