head to head · open source

Uptime Kuma vs hertzbeat

Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. hertzbeat has 7,451 stars, 1,370 forks, 313 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 1,151% (93,190 vs 7,451 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.

Uptime Kuma ★ 93K hertzbeat ★ 7.5K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

Uptime Kuma hertzbeat
GitHub stars ★ 93K ★ 7.5K
License MIT Apache-2.0
Written in JavaScript Java
Last push 2026-11-02 2026-11-02
Forks ⑂ 8.7K ⑂ 1.4K
Self-hosting Yes Yes
Data ownership Your server Your server

pick Uptime Kuma if

  • You weight community size — 93K stars and counting
  • You want the MIT license terms
  • Your stack matches JavaScript
  • You value the larger contributor base for long-term maintenance

full Uptime Kuma profile →

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

full hertzbeat profile →

About Uptime Kuma

Uptime Kuma Uptime Kuma is an easy to use self hosted monitoring tool. 🥔 Live Demo Try it! Demo Server (Location: Frankfurt Germany): It is a temporary live demo, all data will be deleted after 10 minutes. Sponsored by Uptime Kuma Sponsors. ⭐ Features Monitoring uptime for HTTP(s) / TCP / HTTP(s) Keyword / HTTP(s) Json Query / Websocket / Ping / DNS Record / Push / Steam Game Server / Docker Containers Fancy, Reactive, Fast UI/UX Notifications via Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP), and 90+ notification services, click here for the full list 20 second intervals Multi Languages Multiple…

read the full Uptime Kuma overview →

About hertzbeat

Readme : English 中文 日本語 Home: hertzbeat.apache.org Email: Mail to dev subscribe@hertzbeat.apache.org to subscribe mailing lists 🎡 Introduction Apache HertzBeat™ is an AI powered next generation open source real time observability system. Unified metrics and logs collection, centralized alerting distribution, intelligent management and analysis. No Agent required, high performance cluster, provides powerful custom monitoring and status page building capabilities. Features Integrates collection + analysis + alerting + notification into one platform, with new AI powered interactions and features under HertzBeat…

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 93,190 GitHub stars and hertzbeat has 7,451. 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 (93,190 stars) or its MIT licence terms. Choose hertzbeat if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.