Skip to content
DevUtils Online

Self-Hosted

nginx-ui vs uptime-kuma

uptime-kuma leads by 13.7 · clear

A

nginx-ui

84.2

11,792 stars · AGPL-3.0

nginx-ui 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. nginx-ui is written mainly in Go; uptime-kuma is written mainly in JavaScript. The composite score is 84.2 for nginx-ui and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to nginx-ui's 11,792, a gap of 82,746 (8.02×). Forks are 921 for nginx-ui and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 75 versus 100.

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

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

In Self-Hosted, both nginx-ui (11,792 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: nginx-ui is open source, uptime-kuma is open source.

The lead is split. nginx-ui 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 nginx-ui at 84.2, a 13.7 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.

nginx-ui versus uptime-kuma metrics
Signal nginx-ui uptime-kuma
GitHub stars 11,792 94,538
Forks 921 8,860
Open issues 41 852
Adoption 82 100
Activity 100 100
Community 75 100
Issue health 96 84
License 52 96
Self-hosting 100 100
Composite 84.2 97.9

Questions this page answers

Which has more GitHub stars, nginx-ui or uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 11,792 for nginx-ui. The gap is 82,746 stars.

Which was updated more recently, nginx-ui or uptime-kuma?

Both were last pushed on 17 November 2026.

Can I self-host both nginx-ui and uptime-kuma?

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

nginx-ui 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.

Who wins the nginx-ui vs uptime-kuma score?

uptime-kuma scores 97.9 and nginx-ui scores 84.2. This page calls that a clear lead for uptime-kuma.

Related comparisons