Skip to content
DevUtils Online

Self-Hosted

onyx vs uptime-kuma

uptime-kuma leads by 13.3 · clear

A

onyx

84.6

33,441 stars · license n/a

onyx 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. onyx is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 84.6 for onyx and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to onyx's 33,441, a gap of 61,097 (2.83×). Forks are 4,754 for onyx and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 93 versus 100.

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

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

In Self-Hosted, both onyx (33,441 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: onyx 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, 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 onyx at 84.6, a 13.3 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.

onyx versus uptime-kuma metrics
Signal onyx uptime-kuma
GitHub stars 33,441 94,538
Forks 4,754 8,860
Open issues 730 852
Adoption 91 100
Activity 100 100
Community 93 100
Issue health 70 84
License 30 96
Self-hosting 100 100
Composite 84.6 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 33,441 for onyx. The gap is 61,097 stars.

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

Both were last pushed on 17 November 2026.

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

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

onyx 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 onyx vs uptime-kuma score?

uptime-kuma scores 97.9 and onyx scores 84.6. This page calls that a clear lead for uptime-kuma.

Related comparisons