Skip to content
DevUtils Online

Self-Hosted

metube vs uptime-kuma

uptime-kuma leads by 12.6 · clear

A

metube

85.3

15,290 stars · AGPL-3.0

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

uptime-kuma has 94,538 GitHub stars to metube's 15,290, a gap of 79,248 (6.18×). Forks are 1,140 for metube and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 77 versus 100.

Push history: metube was last pushed on 14 November 2026 (2 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 5 for metube (0.000 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

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

In Self-Hosted, both metube (15,290 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: metube is open source, uptime-kuma is open source.

The lead is split. metube 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 metube at 85.3, a 12.6 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.

metube versus uptime-kuma metrics
Signal metube uptime-kuma
GitHub stars 15,290 94,538
Forks 1,140 8,860
Open issues 5 852
Adoption 84 100
Activity 100 100
Community 77 100
Issue health 96 84
License 52 96
Self-hosting 100 100
Composite 85.3 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 15,290 for metube. The gap is 79,248 stars.

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

uptime-kuma was pushed more recently: 17 November 2026 versus 14 November 2026 for metube. That is 2 days apart.

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

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

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

uptime-kuma scores 97.9 and metube scores 85.3. This page calls that a clear lead for uptime-kuma.

Related comparisons