Skip to content
DevUtils Online

Self-Hosted

atlas vs uptime-kuma

uptime-kuma leads by 10.5 · clear

A

atlas

87.4

9,444 stars · Apache-2.0

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

uptime-kuma has 94,538 GitHub stars to atlas's 9,444, a gap of 85,094 (10.01×). Forks are 377 for atlas and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 65 versus 100.

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

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

In Self-Hosted, both atlas (9,444 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: atlas is open source, uptime-kuma is open source.

The lead is split. atlas is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on fork community (100 to 65). Choose the dimension a rollout cannot compromise on.

uptime-kuma finishes ahead at 97.9 against atlas at 87.4, a 10.5 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.

atlas versus uptime-kuma metrics
Signal atlas uptime-kuma
GitHub stars 9,444 94,538
Forks 377 8,860
Open issues 20 852
Adoption 80 100
Activity 100 100
Community 65 100
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 87.4 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 9,444 for atlas. The gap is 85,094 stars.

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

Both were last pushed on 17 November 2026.

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

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

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

uptime-kuma scores 97.9 and atlas scores 87.4. This page calls that a clear lead for uptime-kuma.

Related comparisons