Skip to content
DevUtils Online

Self-Hosted

FreshRSS vs uptime-kuma

uptime-kuma leads by 14.7 · clear

A

FreshRSS

83.2

16,611 stars · AGPL-3.0

FreshRSS 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. FreshRSS is written mainly in PHP; uptime-kuma is written mainly in JavaScript. The composite score is 83.2 for FreshRSS and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to FreshRSS's 16,611, a gap of 77,927 (5.69×). Forks are 1,349 for FreshRSS and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 79 versus 100.

Push history: FreshRSS 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 680 for FreshRSS (0.041 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.

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

In Self-Hosted, both FreshRSS (16,611 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: FreshRSS is open source, uptime-kuma is open source.

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

uptime-kuma finishes ahead at 97.9 against FreshRSS at 83.2, a 14.7 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.

FreshRSS versus uptime-kuma metrics
Signal FreshRSS uptime-kuma
GitHub stars 16,611 94,538
Forks 1,349 8,860
Open issues 680 852
Adoption 85 100
Activity 100 100
Community 79 100
Issue health 70 84
License 52 96
Self-hosting 100 100
Composite 83.2 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 16,611 for FreshRSS. The gap is 77,927 stars.

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

Both were last pushed on 17 November 2026.

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

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

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

uptime-kuma scores 97.9 and FreshRSS scores 83.2. This page calls that a clear lead for uptime-kuma.

Related comparisons