head to head · open source
Uptime Kuma vs MyPerf4J
Uptime Kuma has 91,498 GitHub stars, 8,431 forks, 805 open issues and last shipped today. MyPerf4J has 3,566 stars, 554 forks, 5 open issues and last shipped 2 months ago. Uptime Kuma leads on adoption by 2,466% (91,498 vs 3,566 stars). Uptime Kuma is written in JavaScript under MIT; MyPerf4J is written in Java under BSD-3-Clause. Uptime Kuma has attracted 9% as many forks as stars, MyPerf4J 16%. 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 | MyPerf4J | |
|---|---|---|
| GitHub stars | ★ 91K | ★ 3.6K |
| License | MIT | BSD-3-Clause |
| Written in | JavaScript | Java |
| Last push | 2026-09-18 | 2026-07-31 |
| Forks | ⑂ 8.4K | ⑂ 554 |
| 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 MyPerf4J if
- You want the MyPerf4J feature set and don't need the biggest community
- You prefer the BSD-3-Clause license terms
- Your stack matches Java
- You evaluated both and MyPerf4J 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 MyPerf4J
简体中文 English MyPerf4J 一个针对高并发、低延迟应用设计的高性能 Java 性能监控和统计工具。 价值 快速定位性能瓶颈 快速定位故障原因 优势 高性能: 单线程支持每秒 1600 万次 响应时间的记录，每次记录只花费 63 纳秒 无侵入: 采用 JavaAgent 方式，对应用程序完全无侵入，无需修改应用代码 低内存: 采用 内存复用 的方式，整个生命周期只产生极少的临时对象，不影响应用程序的 GC 高实时: 支持 秒级统计 ，最低统计粒度为 1 秒 ，并且是 全量统计 ，不丢失任何一次记录 文档 English Doc 中文文档 监控指标 MyPerf4J 为每个应用收集数十个监控指标，所有的监控指标都是实时采集和展现的。 下面是 MyPerf4J 目前支持的监控指标列表: Method Metrics RPS，Count，Avg，Min，Max，StdDev，TP50, TP90, TP95, TP99, TP999, TP9999, TP100 JVM Metrics Thread，Memory，ByteBuff，GC，Class，Compilation，FileDescriptor 想知道如何实现上述效果？请先按照快速启动的描述启动应用，再按照这里的描述进行安装配置即可。 快速启动 MyPerf4J 采用 JavaAgent 配置方式， 透明化 接入应用，对应用代码完全 没有侵入 。 下载 下…
read the full MyPerf4J 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 MyPerf4J more popular?
Uptime Kuma has 91,498 GitHub stars and MyPerf4J has 3,566. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and MyPerf4J free?
Both are open source. Uptime Kuma is licensed under MIT and MyPerf4J under BSD-3-Clause. Neither carries a licence fee.
What is the difference between Uptime Kuma and MyPerf4J?
Uptime Kuma is written in JavaScript and MyPerf4J 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 MyPerf4J?
Choose Uptime Kuma if you want the larger community (91,498 stars) or its MIT licence terms. Choose MyPerf4J if its feature set, stack or BSD-3-Clause licence fits better. Both are self-hostable.