Skip to content
DevUtils Online

Self-Hosted

Stirling-PDF vs uptime-kuma

uptime-kuma leads by 6.6 · narrow

Stirling-PDF 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. Stirling-PDF is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 91.2 for Stirling-PDF and 97.8 for uptime-kuma.

Stirling-PDF has 96,832 GitHub stars to uptime-kuma's 94,538, a gap of 2,294 (1.02×). Forks are 9,373 for Stirling-PDF and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 99.

Push history: Stirling-PDF 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 448 for Stirling-PDF (0.005 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for Stirling-PDF and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both Stirling-PDF (96,832 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: Stirling-PDF is unpriced in this catalog, uptime-kuma is open source.

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

uptime-kuma finishes ahead at 97.8 against Stirling-PDF at 91.2, a 6.6 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.

Stirling-PDF versus uptime-kuma metrics
Signal Stirling-PDF uptime-kuma
GitHub stars 96,832 94,538
Forks 9,373 8,860
Open issues 448 852
Adoption 100 100
Activity 100 100
Community 100 99
Issue health 96 84
License 30 96
Self-hosting 100 100
Composite 91.2 97.8

Questions this page answers

Which has more GitHub stars, Stirling-PDF or uptime-kuma?

Stirling-PDF has more GitHub stars: 96,832 versus 94,538 for uptime-kuma. The gap is 2,294 stars.

Which was updated more recently, Stirling-PDF or uptime-kuma?

Both were last pushed on 17 November 2026.

Can I self-host both Stirling-PDF and uptime-kuma?

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

Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 Stirling-PDF vs uptime-kuma score?

uptime-kuma scores 97.8 and Stirling-PDF scores 91.2. This page calls that a narrow lead for uptime-kuma.

Related comparisons