Skip to content
DevUtils Online

Self-Hosted

uptime-kuma vs wallabag

uptime-kuma leads by 12.6 · clear

uptime-kuma versus wallabag is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. uptime-kuma is written mainly in JavaScript; wallabag is written mainly in PHP. The composite score is 97.9 for uptime-kuma and 85.3 for wallabag.

uptime-kuma has 94,538 GitHub stars to wallabag's 13,066, a gap of 81,472 (7.24×). Forks are 8,860 for uptime-kuma and 916 for wallabag. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 75.

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

Both uptime-kuma and wallabag 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 uptime-kuma (94,538 stars) and wallabag (13,066 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: uptime-kuma is open source, wallabag is open source.

uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 32 points (84 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against wallabag 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.

uptime-kuma versus wallabag metrics
Signal uptime-kuma wallabag
GitHub stars 94,538 13,066
Forks 8,860 916
Open issues 852 742
Adoption 100 83
Activity 100 100
Community 100 75
Issue health 84 52
License 96 96
Self-hosting 100 100
Composite 97.9 85.3

wallabag

wallabag is a self hostable application for saving web pages: Save and classify articles. Read them later. Freely.

Project site · GitHub · Full profile

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 13,066 for wallabag. The gap is 81,472 stars.

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

Both were last pushed on 17 November 2026.

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

Yes. This catalog marks both uptime-kuma and wallabag as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, uptime-kuma or wallabag?

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

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

Related comparisons