A
AIHOT
90.8
10,903 stars · MIT
Self-Hosted
uptime-kuma leads by 7.1 · clear
A
90.8
10,903 stars · MIT
B · leads
97.9
94,538 stars · MIT
AIHOT 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. AIHOT is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 90.8 for AIHOT and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to AIHOT's 10,903, a gap of 83,635 (8.67×). Forks are 2,532 for AIHOT and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 86 versus 100.
Push history: AIHOT 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 for AIHOT (0.000 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both AIHOT and uptime-kuma are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both AIHOT (10,903 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: AIHOT is open source, uptime-kuma is open source.
The lead is split. AIHOT is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on adoption (100 to 81). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against AIHOT at 90.8, a 7.1 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 | AIHOT | uptime-kuma |
|---|---|---|
| GitHub stars | 10,903 | 94,538 |
| Forks | 2,532 | 8,860 |
| Open issues | 1 | 852 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.8 | 97.9 |
一个自己找热点、自己写日报的网站框架。把信源和精选标准换成你的,它就是你的行业热点站。
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 10,903 for AIHOT. The gap is 83,635 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both AIHOT and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
AIHOT 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. 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 AIHOT scores 90.8. This page calls that a clear lead for uptime-kuma.