Skip to content
DevUtils Online

Self-Hosted

traccar vs uptime-kuma

uptime-kuma leads by 10.1 · clear

A

traccar

87.8

8,142 stars · Apache-2.0

traccar 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. traccar is written mainly in Java; uptime-kuma is written mainly in JavaScript. The composite score is 87.8 for traccar and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to traccar's 8,142, a gap of 86,396 (11.61×). Forks are 3,494 for traccar and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 90 versus 100.

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

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

In Self-Hosted, both traccar (8,142 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: traccar is open source, uptime-kuma is open source.

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

uptime-kuma finishes ahead at 97.9 against traccar at 87.8, a 10.1 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.

traccar versus uptime-kuma metrics
Signal traccar uptime-kuma
GitHub stars 8,142 94,538
Forks 3,494 8,860
Open issues 406 852
Adoption 79 100
Activity 100 100
Community 90 100
Issue health 70 84
License 96 96
Self-hosting 100 100
Composite 87.8 97.9

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 8,142 for traccar. The gap is 86,396 stars.

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

Both were last pushed on 17 November 2026.

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

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

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

uptime-kuma scores 97.9 and traccar scores 87.8. This page calls that a clear lead for uptime-kuma.

Related comparisons