A
QuantDinger
91.6
13,825 stars · Apache-2.0
Self-Hosted
uptime-kuma leads by 6.3 · narrow
A
91.6
13,825 stars · Apache-2.0
B · leads
97.9
94,538 stars · MIT
QuantDinger 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. QuantDinger is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 91.6 for QuantDinger and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to QuantDinger's 13,825, a gap of 80,713 (6.84×). Forks are 2,819 for QuantDinger and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 87 versus 100.
Push history: QuantDinger was last pushed on 16 November 2026 (1 day ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 43 for QuantDinger (0.003 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
QuantDinger is listed as Apache-2.0, 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. License scores in this pair are 96 for QuantDinger and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both QuantDinger (13,825 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: QuantDinger is open source, uptime-kuma is open source.
The lead is split. QuantDinger is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on adoption (100 to 83). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against QuantDinger at 91.6, a 6.3 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 | QuantDinger | uptime-kuma |
|---|---|---|
| GitHub stars | 13,825 | 94,538 |
| Forks | 2,819 | 8,860 |
| Open issues | 43 | 852 |
| Adoption | 83 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.6 | 97.9 |
The most complete open-source, self-hosted Agentic Trading OS—AI research, Python strategies, factor discovery, backtesting, optimization, paper/live multi-asset execution, risk controls, monitoring, MCP, and multi-tenant SaaS in one auditable stack.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 13,825 for QuantDinger. The gap is 80,713 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 16 November 2026 for QuantDinger. That is 1 days apart.
Yes. This catalog marks both QuantDinger and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
QuantDinger is listed as Apache-2.0, 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 QuantDinger scores 91.6. This page calls that a narrow lead for uptime-kuma.