A
TREK
85.6
15,696 stars · AGPL-3.0
Self-Hosted
uptime-kuma leads by 12.3 · clear
A
85.6
15,696 stars · AGPL-3.0
B · leads
97.9
94,538 stars · MIT
TREK 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. TREK is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 85.6 for TREK and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to TREK's 15,696, a gap of 78,842 (6.02×). Forks are 1,342 for TREK and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 79 versus 100.
Push history: TREK 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 19 for TREK (0.001 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
TREK is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for TREK and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both TREK (15,696 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: TREK is open source, uptime-kuma is open source.
The lead is split. TREK is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.9 against TREK at 85.6, a 12.3 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 | TREK | uptime-kuma |
|---|---|---|
| GitHub stars | 15,696 | 94,538 |
| Forks | 1,342 | 8,860 |
| Open issues | 19 | 852 |
| Adoption | 84 | 100 |
| Activity | 100 | 100 |
| Community | 79 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 85.6 | 97.9 |
The most complete open-source travel planner: real-time collaboration, bookings, budgets, packing lists, journals, offline PWA, SSO and an AI-ready MCP server, with planet-wide place search and routing built in.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 15,696 for TREK. The gap is 78,842 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both TREK and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
TREK is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 TREK scores 85.6. This page calls that a clear lead for uptime-kuma.