Skip to content
DevUtils Online

Self-Hosted

jan vs uptime-kuma

uptime-kuma leads by 11.6 · clear

A

jan

86.3

45,760 stars · license n/a

jan 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. jan is written mainly in Rust; uptime-kuma is written mainly in JavaScript. The composite score is 86.3 for jan and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to jan's 45,760, a gap of 48,778 (2.07×). Forks are 3,179 for jan and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 89 versus 100.

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

jan is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for jan and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both jan (45,760 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: jan is unpriced in this catalog, uptime-kuma is open source.

uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against jan at 86.3, a 11.6 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.

jan versus uptime-kuma metrics
Signal jan uptime-kuma
GitHub stars 45,760 94,538
Forks 3,179 8,860
Open issues 580 852
Adoption 94 100
Activity 100 100
Community 89 100
Issue health 84 84
License 30 96
Self-hosting 100 100
Composite 86.3 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 45,760 for jan. The gap is 48,778 stars.

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

Both were last pushed on 17 November 2026.

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

Yes. This catalog marks both jan 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, jan or uptime-kuma?

jan is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 jan vs uptime-kuma score?

uptime-kuma scores 97.9 and jan scores 86.3. This page calls that a clear lead for uptime-kuma.

Related comparisons