head to head · open source
Uptime Kuma vs perses
Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. perses has 2,514 stars, 266 forks, 277 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 3,607% (93,190 vs 2,514 stars). Uptime Kuma is written in JavaScript under MIT; perses is written in Go under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, perses 11%. perses was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (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 20902 open source comparisons
Side by side
| Uptime Kuma | perses | |
|---|---|---|
| GitHub stars | ★ 93K | ★ 2.5K |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 8.7K | ⑂ 266 |
| 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
pick perses if
- You want the perses 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 perses fits your workflow better
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 perses
Perses Overview Perses is first and foremost a dashboard tool that you can use to display a variety of observability data. It currently supports Prometheus metrics, Tempo traces, Loki for logs, Pyroscope for profiling, bringing together all four observability pillars in one place. As the project continues to evolve, it will expand support for additional tools to give users even more flexibility and insight. Perses is a Cloud Native Computing Foundation sandbox project. Beyond its core usage, Perses aims to achieve several broader goals: Open specification for dashboards . Perses is also an initiative to define a…
read the full perses 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 perses more popular?
Uptime Kuma has 93,190 GitHub stars and perses has 2,514. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and perses free?
Both are open source. Uptime Kuma is licensed under MIT and perses under Apache-2.0. Neither carries a licence fee.
What is the difference between Uptime Kuma and perses?
Uptime Kuma is written in JavaScript and perses 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 perses?
Choose Uptime Kuma if you want the larger community (93,190 stars) or its MIT licence terms. Choose perses if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.