Skip to content
DevUtils Online

Self-Hosted

listmonk vs uptime-kuma

uptime-kuma leads by 9.8 · clear

A

listmonk

88.1

24,352 stars · AGPL-3.0

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

uptime-kuma has 94,538 GitHub stars to listmonk's 24,352, a gap of 70,186 (3.88×). Forks are 2,807 for listmonk and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 87 versus 100.

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

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

In Self-Hosted, both listmonk (24,352 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: listmonk is open source, uptime-kuma is open source.

The lead is split. listmonk 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 listmonk at 88.1, a 9.8 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.

listmonk versus uptime-kuma metrics
Signal listmonk uptime-kuma
GitHub stars 24,352 94,538
Forks 2,807 8,860
Open issues 69 852
Adoption 88 100
Activity 100 100
Community 87 100
Issue health 96 84
License 52 96
Self-hosting 100 100
Composite 88.1 97.9

listmonk

High performance, self-hosted, newsletter and mailing list manager with a modern dashboard. Single binary app.

Project site · GitHub · Full profile

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 24,352 for listmonk. The gap is 70,186 stars.

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

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

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

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

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

uptime-kuma scores 97.9 and listmonk scores 88.1. This page calls that a clear lead for uptime-kuma.

Related comparisons