Skip to content
DevUtils Online

Self-Hosted

core vs uptime-kuma

uptime-kuma leads by 14.5 · clear

A

core

83.4

8,853 stars · AGPL-3.0

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

uptime-kuma has 94,538 GitHub stars to core's 8,853, a gap of 85,685 (10.68×). Forks are 2,061 for core and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 84 versus 100.

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

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

In Self-Hosted, both core (8,853 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: core is open source, 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 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against core at 83.4, a 14.5 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.

core versus uptime-kuma metrics
Signal core uptime-kuma
GitHub stars 8,853 94,538
Forks 2,061 8,860
Open issues 146 852
Adoption 79 100
Activity 100 100
Community 84 100
Issue health 84 84
License 52 96
Self-hosting 100 100
Composite 83.4 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 8,853 for core. The gap is 85,685 stars.

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

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

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

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

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

uptime-kuma scores 97.9 and core scores 83.4. This page calls that a clear lead for uptime-kuma.

Related comparisons