A
bore
74.5
11,615 stars · MIT
Self-Hosted
uptime-kuma leads by 23.4 · decisive
A
74.5
11,615 stars · MIT
B · leads
97.9
94,538 stars · MIT
bore 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. bore is written mainly in Rust; uptime-kuma is written mainly in JavaScript. The composite score is 74.5 for bore and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to bore's 11,615, a gap of 82,923 (8.14×). Forks are 531 for bore and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 69 versus 100.
Push history: bore was last pushed on 04 February 2026 (286 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 19 for bore (0.002 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 36 and 100.
Both bore 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 bore (11,615 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: bore is open source, uptime-kuma is open source.
The lead is split. bore is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against bore at 74.5, a 23.4 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 | bore | uptime-kuma |
|---|---|---|
| GitHub stars | 11,615 | 94,538 |
| Forks | 531 | 8,860 |
| Open issues | 19 | 852 |
| Adoption | 82 | 100 |
| Activity | 36 | 100 |
| Community | 69 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 74.5 | 97.9 |
🕳 bore is a simple CLI tool for making tunnels to localhost
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 11,615 for bore. The gap is 82,923 stars.
uptime-kuma was pushed more recently: 17 November 2026 versus 04 February 2026 for bore. That is 286 days apart.
Yes. This catalog marks both bore and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
bore 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 bore scores 74.5. This page calls that a decisive lead for uptime-kuma.