Skip to content
DevUtils Online

Self-Hosted

CasaOS vs uptime-kuma

uptime-kuma leads by 6.2 · narrow

A

CasaOS

91.7

37,656 stars · Apache-2.0

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

uptime-kuma has 94,538 GitHub stars to CasaOS's 37,656, a gap of 56,882 (2.51×). Forks are 2,222 for CasaOS and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 85 versus 100.

Push history: CasaOS 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 844 for CasaOS (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.

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

In Self-Hosted, both CasaOS (37,656 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: CasaOS is open source, uptime-kuma is open source.

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

uptime-kuma finishes ahead at 97.9 against CasaOS at 91.7, a 6.2 point narrow 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.

CasaOS versus uptime-kuma metrics
Signal CasaOS uptime-kuma
GitHub stars 37,656 94,538
Forks 2,222 8,860
Open issues 844 852
Adoption 92 100
Activity 100 100
Community 85 100
Issue health 70 84
License 96 96
Self-hosting 100 100
Composite 91.7 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 37,656 for CasaOS. The gap is 56,882 stars.

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

Both were last pushed on 17 November 2026.

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

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

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

uptime-kuma scores 97.9 and CasaOS scores 91.7. This page calls that a narrow lead for uptime-kuma.

Related comparisons