A
signoz
81.7
32,668 stars · license n/a
Self-Hosted
uptime-kuma leads by 16.2 · decisive
A
81.7
32,668 stars · license n/a
B · leads
97.9
94,538 stars · MIT
signoz 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. signoz is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 81.7 for signoz and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to signoz's 32,668, a gap of 61,870 (2.89×). Forks are 2,607 for signoz and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 86 versus 100.
Push history: signoz 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 1,650 for signoz (0.051 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
signoz 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 signoz and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both signoz (32,668 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: signoz 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, 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 signoz at 81.7, a 16.2 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 | signoz | uptime-kuma |
|---|---|---|
| GitHub stars | 32,668 | 94,538 |
| Forks | 2,607 | 8,860 |
| Open issues | 1,650 | 852 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 52 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 81.7 | 97.9 |
SigNoz is an open-source, OpenTelemetry-native observability platform for your team and their AI agents. Get logs, metrics, and traces in one tool with features like APM, distributed tracing, log management, infra monitoring, etc. Combined with SigNoz MCP and a native AI teammate (in SigNoz Cloud) it helps you build more resilient apps.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 32,668 for signoz. The gap is 61,870 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both signoz and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
signoz 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 signoz scores 81.7. This page calls that a decisive lead for uptime-kuma.