Skip to content
DevUtils Online

Self-Hosted

cachet vs uptime-kuma

uptime-kuma leads by 14.7 · clear

A

cachet

83.2

15,267 stars · license n/a

cachet 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. cachet is written mainly in PHP; uptime-kuma is written mainly in JavaScript. The composite score is 83.2 for cachet and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to cachet's 15,267, a gap of 79,271 (6.19×). Forks are 1,628 for cachet and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 81 versus 100.

Push history: cachet was last pushed on 16 November 2026 (1 day ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 8 for cachet (0.001 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

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

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

The lead is split. cachet is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

uptime-kuma finishes ahead at 97.9 against cachet at 83.2, a 14.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.

cachet versus uptime-kuma metrics
Signal cachet uptime-kuma
GitHub stars 15,267 94,538
Forks 1,628 8,860
Open issues 8 852
Adoption 84 100
Activity 100 100
Community 81 100
Issue health 96 84
License 30 96
Self-hosting 100 100
Composite 83.2 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 15,267 for cachet. The gap is 79,271 stars.

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

uptime-kuma was pushed more recently: 17 November 2026 versus 16 November 2026 for cachet. That is 1 days apart.

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

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

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

uptime-kuma scores 97.9 and cachet scores 83.2. This page calls that a clear lead for uptime-kuma.

Related comparisons