Skip to content
DevUtils Online

Self-Hosted

homer vs uptime-kuma

uptime-kuma leads by 9.6 · clear

A

homer

88.3

11,725 stars · Apache-2.0

homer 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. homer is written mainly in Vue; uptime-kuma is written mainly in JavaScript. The composite score is 88.3 for homer and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to homer's 11,725, a gap of 82,813 (8.06×). Forks are 928 for homer and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 75 versus 100.

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

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

In Self-Hosted, both homer (11,725 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: homer 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, license flexibility, self-hosting. The widest gap is fork community at 25 points (75 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against homer at 88.3, a 9.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.

homer versus uptime-kuma metrics
Signal homer uptime-kuma
GitHub stars 11,725 94,538
Forks 928 8,860
Open issues 157 852
Adoption 82 100
Activity 100 100
Community 75 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 88.3 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 11,725 for homer. The gap is 82,813 stars.

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

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

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

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

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

uptime-kuma scores 97.9 and homer scores 88.3. This page calls that a clear lead for uptime-kuma.

Related comparisons