Skip to content
DevUtils Online

Self-Hosted

SafeLine vs uptime-kuma

uptime-kuma leads by 11.2 · clear

A

SafeLine

86.7

23,303 stars · GPL-3.0

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

uptime-kuma has 94,538 GitHub stars to SafeLine's 23,303, a gap of 71,235 (4.06×). Forks are 1,610 for SafeLine and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 81 versus 100.

Push history: SafeLine was last pushed on 11 November 2026 (6 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 48 for SafeLine (0.002 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.

SafeLine is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 64 for SafeLine and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both SafeLine (23,303 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: SafeLine is open source, uptime-kuma is open source.

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

uptime-kuma finishes ahead at 97.9 against SafeLine at 86.7, a 11.2 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.

SafeLine versus uptime-kuma metrics
Signal SafeLine uptime-kuma
GitHub stars 23,303 94,538
Forks 1,610 8,860
Open issues 48 852
Adoption 88 100
Activity 92 100
Community 81 100
Issue health 96 84
License 64 96
Self-hosting 100 100
Composite 86.7 97.9

SafeLine

SafeLine is a self-hosted WAF(Web Application Firewall) / reverse proxy to protect your web apps from attacks and exploits.

Project site · GitHub · Full profile

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 23,303 for SafeLine. The gap is 71,235 stars.

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

uptime-kuma was pushed more recently: 17 November 2026 versus 11 November 2026 for SafeLine. That is 6 days apart.

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

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

SafeLine is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 SafeLine vs uptime-kuma score?

uptime-kuma scores 97.9 and SafeLine scores 86.7. This page calls that a clear lead for uptime-kuma.

Related comparisons