Skip to content
DevUtils Online

Self-Hosted

openship vs uptime-kuma

uptime-kuma leads by 8.2 · clear

A

openship

89.7

15,349 stars · Apache-2.0

openship 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. openship is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 89.7 for openship and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to openship's 15,349, a gap of 79,189 (6.16×). Forks are 1,415 for openship and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 80 versus 100.

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

openship is listed as Apache-2.0, 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. License scores in this pair are 96 for openship and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both openship (15,349 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: openship 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 20 points (80 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against openship at 89.7, a 8.2 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.

openship versus uptime-kuma metrics
Signal openship uptime-kuma
GitHub stars 15,349 94,538
Forks 1,415 8,860
Open issues 177 852
Adoption 84 100
Activity 100 100
Community 80 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 89.7 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 15,349 for openship. The gap is 79,189 stars.

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

Both were last pushed on 17 November 2026.

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

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

openship is listed as Apache-2.0, 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 openship vs uptime-kuma score?

uptime-kuma scores 97.9 and openship scores 89.7. This page calls that a clear lead for uptime-kuma.

Related comparisons