head to head · open source
Uptime Kuma vs hertzbeat
Uptime Kuma has 91,477 GitHub stars, 8,426 forks, 805 open issues and last shipped yesterday. hertzbeat has 7,397 stars, 1,331 forks, 313 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 1,137% (91,477 vs 7,397 stars). Uptime Kuma is written in JavaScript under MIT; hertzbeat is written in Java under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, hertzbeat 18%. Uptime Kuma was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (monitor, monitoring), so they are genuine substitutes rather than adjacent tools.
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 | hertzbeat | |
|---|---|---|
| GitHub stars | ★ 91K | ★ 7.4K |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | Java |
| Last push | 2026-09-17 | 2026-09-17 |
| Forks | ⑂ 8.4K | ⑂ 1.3K |
| 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 hertzbeat if
- You want the hertzbeat 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 hertzbeat 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 hertzbeat
Apache HertzBeat is an AI powered, next generation open source real time observability system written in Java under the Apache 2.0 licence, built for teams that need unified metrics and logs collection, centralized alerting distribution, and intelligent management and analysis without deploying an agent on every monitored host.
read the full hertzbeat 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 hertzbeat more popular?
Uptime Kuma has 91,477 GitHub stars and hertzbeat has 7,397. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and hertzbeat free?
Both are open source. Uptime Kuma is licensed under MIT and hertzbeat under Apache-2.0. Neither carries a licence fee.
What is the difference between Uptime Kuma and hertzbeat?
Uptime Kuma is written in JavaScript and hertzbeat 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 hertzbeat?
Choose Uptime Kuma if you want the larger community (91,477 stars) or its MIT licence terms. Choose hertzbeat if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.