A
hive
87.7
11,167 stars · Apache-2.0
Self-Hosted
uptime-kuma leads by 10.2 · clear
A
87.7
11,167 stars · Apache-2.0
B · leads
97.9
94,538 stars · MIT
hive 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. hive is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 87.7 for hive and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to hive's 11,167, a gap of 83,371 (8.47×). Forks are 5,629 for hive and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 95 versus 100.
Push history: hive 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,108 for hive (0.099 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
hive 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 hive and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both hive (11,167 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: hive 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 issue health at 32 points (52 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against hive at 87.7, a 10.2 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 | hive | uptime-kuma |
|---|---|---|
| GitHub stars | 11,167 | 94,538 |
| Forks | 5,629 | 8,860 |
| Open issues | 1,108 | 852 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.7 | 97.9 |
Multi-Agent Harness for Production AI
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 11,167 for hive. The gap is 83,371 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both hive and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
hive 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 hive scores 87.7. This page calls that a clear lead for uptime-kuma.