Skip to content
DevUtils Online

Self-Hosted

Termix vs uptime-kuma

uptime-kuma leads by 7.8 · clear

A

Termix

90.1

16,055 stars · Apache-2.0

Termix 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. Termix is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 90.1 for Termix and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to Termix's 16,055, a gap of 78,483 (5.89×). Forks are 776 for Termix and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 73 versus 100.

Push history: Termix 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 35 for Termix (0.002 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

Termix 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 Termix and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both Termix (16,055 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: Termix is open source, uptime-kuma is open source.

The lead is split. Termix is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on fork community (100 to 73). Choose the dimension a rollout cannot compromise on.

uptime-kuma finishes ahead at 97.9 against Termix at 90.1, a 7.8 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Termix versus uptime-kuma metrics
Signal Termix uptime-kuma
GitHub stars 16,055 94,538
Forks 776 8,860
Open issues 35 852
Adoption 84 100
Activity 100 100
Community 73 100
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 90.1 97.9

Questions this page answers

Which has more GitHub stars, Termix or uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 16,055 for Termix. The gap is 78,483 stars.

Which was updated more recently, Termix or uptime-kuma?

Both were last pushed on 17 November 2026.

Can I self-host both Termix and uptime-kuma?

Yes. This catalog marks both Termix and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Termix or uptime-kuma?

Termix 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.

Who wins the Termix vs uptime-kuma score?

uptime-kuma scores 97.9 and Termix scores 90.1. This page calls that a clear lead for uptime-kuma.

Related comparisons