Skip to content
DevUtils Online

Self-Hosted

gogs vs uptime-kuma

uptime-kuma leads by 2.8 · narrow

A

gogs

95.1

47,942 stars · MIT

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

uptime-kuma has 94,538 GitHub stars to gogs's 47,942, a gap of 46,596 (1.97×). Forks are 5,081 for gogs and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 94 versus 100.

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

Both gogs and uptime-kuma are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Self-Hosted, both gogs (47,942 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: gogs 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 6 points (94 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against gogs at 95.1, a 2.8 point narrow 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.

gogs versus uptime-kuma metrics
Signal gogs uptime-kuma
GitHub stars 47,942 94,538
Forks 5,081 8,860
Open issues 837 852
Adoption 94 100
Activity 100 100
Community 94 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 95.1 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 47,942 for gogs. The gap is 46,596 stars.

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

Both were last pushed on 17 November 2026.

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

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

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

uptime-kuma scores 97.9 and gogs scores 95.1. This page calls that a narrow lead for uptime-kuma.

Related comparisons