A
rakazo
86.9
8,995 stars · Apache-2.0
Self-Hosted
uptime-kuma leads by 11.0 · clear
A
86.9
8,995 stars · Apache-2.0
B · leads
97.9
94,538 stars · MIT
rakazo 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. rakazo is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 86.9 for rakazo and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to rakazo's 8,995, a gap of 85,543 (10.51×). Forks are 1,614 for rakazo and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 81 versus 100.
Push history: rakazo 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 236 for rakazo (0.026 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
rakazo 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 rakazo and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both rakazo (8,995 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: rakazo is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is adoption at 20 points (80 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against rakazo at 86.9, a 11.0 point clear 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 | rakazo | uptime-kuma |
|---|---|---|
| GitHub stars | 8,995 | 94,538 |
| Forks | 1,614 | 8,860 |
| Open issues | 236 | 852 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 81 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.9 | 97.9 |
Open-source Grok Bot alternative. Choose your own model and sandbox.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 8,995 for rakazo. The gap is 85,543 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both rakazo and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
rakazo 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 rakazo scores 86.9. This page calls that a clear lead for uptime-kuma.