head to head · open source
Uptime Kuma vs jaeger
Uptime Kuma has 91,477 GitHub stars, 8,426 forks, 805 open issues and last shipped yesterday. jaeger has 23,217 stars, 3,119 forks, 547 open issues and last shipped 2 days ago. Uptime Kuma leads on adoption by 294% (91,477 vs 23,217 stars). Uptime Kuma is written in JavaScript under MIT; jaeger is written in Go under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, jaeger 13%. Uptime Kuma was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| Uptime Kuma | jaeger | |
|---|---|---|
| GitHub stars | ★ 91K | ★ 23K |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | Go |
| Last push | 2026-09-17 | 2026-09-16 |
| Forks | ⑂ 8.4K | ⑂ 3.1K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Uptime Kuma if
- You weight community size — 91K stars and counting
- You want the MIT license terms
- Your stack matches JavaScript
- You value the larger contributor base for long-term maintenance
pick jaeger if
- You want the jaeger feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Go
- You evaluated both and jaeger fits your workflow better
About Uptime Kuma
Uptime Kuma is a free, MIT licensed, self hosted monitoring tool with a reactive web dashboard, built for operators and teams that want to watch their own HTTP, TCP, and DNS endpoints and keep the resulting data on their own infrastructure.
read the full Uptime Kuma overview →
About jaeger
Jaeger is a distributed tracing platform hosted by the Cloud Native Computing Foundation (CNCF), where it graduated as the 7th top level project in October 2019. It was originally created by Uber Technologies and then donated to the CNCF. The project is written in Go and released under the Apache 2.0 license, and it lives in the OpenTelemetry and observability ecosystem: it consumes traces from OpenTelemetry SDKs and reuses components from the OpenTelemetry Collector. Its repository carries topics including cncf, distributed tracing, jaeger, observability, opentelemetry and tracing, and the project is openly gove…
read the full jaeger overview →
More in Infrastructure & Operations
Related comparisons
More Monitoring & Observability projects
Compare either of these against the rest of the Monitoring & Observability field.
Frequently asked questions
Is Uptime Kuma or jaeger more popular?
Uptime Kuma has 91,477 GitHub stars and jaeger has 23,217. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and jaeger free?
Both are open source. Uptime Kuma is licensed under MIT and jaeger under Apache-2.0. Neither carries a licence fee.
What is the difference between Uptime Kuma and jaeger?
Uptime Kuma is written in JavaScript and jaeger in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Uptime Kuma or jaeger?
Choose Uptime Kuma if you want the larger community (91,477 stars) or its MIT licence terms. Choose jaeger if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.