head to head · open source
Uptime Kuma vs btrace
Uptime Kuma has 91,477 GitHub stars, 8,426 forks, 805 open issues and last shipped yesterday. btrace has 5,994 stars, 956 forks, 6 open issues and last shipped 4 days ago. Uptime Kuma leads on adoption by 1,426% (91,477 vs 5,994 stars). Uptime Kuma is written in JavaScript under MIT; btrace is written in Java under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, btrace 16%. 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 | btrace | |
|---|---|---|
| GitHub stars | ★ 91K | ★ 6.0K |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | Java |
| Last push | 2026-09-17 | 2026-09-14 |
| Forks | ⑂ 8.4K | ⑂ 956 |
| 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 btrace if
- You want the btrace feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Java
- You evaluated both and btrace 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 btrace
BTrace is an open source dynamic tracing and diagnostics tool for Java applications, distributed under the Apache 2.0 license and maintained in the Java and JVM ecosystem. It works by attaching to a running Java Virtual Machine and dynamically instrumenting bytecode at runtime, injecting tracing code into classes that are already loaded. The project sits in the Infrastructure & Operations / Monitoring & Observability category and carries the topics tracing, observability, diagnostics, profiling, bytecode instrumentation, runtime instrumentation, java agent and dtrace.
read the full btrace 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 btrace more popular?
Uptime Kuma has 91,477 GitHub stars and btrace has 5,994. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and btrace free?
Both are open source. Uptime Kuma is licensed under MIT and btrace under Apache-2.0. Neither carries a licence fee.
What is the difference between Uptime Kuma and btrace?
Uptime Kuma is written in JavaScript and btrace in Java. 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 btrace?
Choose Uptime Kuma if you want the larger community (91,477 stars) or its MIT licence terms. Choose btrace if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.