head to head · open source
Uptime Kuma vs pyrra
Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. pyrra has 1,568 stars, 154 forks, 83 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 5,843% (93,190 vs 1,568 stars). Uptime Kuma is written in JavaScript under MIT; pyrra is written in Go under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, pyrra 10%. 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 (docker, 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 | pyrra | |
|---|---|---|
| GitHub stars | ★ 93K | ★ 1.6K |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 8.7K | ⑂ 154 |
| 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 pyrra if
- You want the pyrra 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 pyrra 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 pyrra
Making SLOs with Prometheus manageable, accessible, and easy to use for everyone! Dashboards to visualize SLOs in Grafana: Watch the 5min lightning talk at Prometheus Day 2022: Features Support for Kubernetes, Docker, and reading from the filesystem Alerting: Generates 4 Multi Burn Rate Alerts with different severity Page listing all Service Level Objectives Search through names and labels Sorted by remaining error budget to see the worst ones quickly All columns sortable View and hide individual columns Clicking on labels to filter SLOs that contain the label Tool tips when hovering for extra context Page with…
read the full pyrra 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 pyrra more popular?
Uptime Kuma has 93,190 GitHub stars and pyrra has 1,568. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and pyrra free?
Both are open source. Uptime Kuma is licensed under MIT and pyrra under Apache-2.0. Neither carries a licence fee.
What is the difference between Uptime Kuma and pyrra?
Uptime Kuma is written in JavaScript and pyrra 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 pyrra?
Choose Uptime Kuma if you want the larger community (93,190 stars) or its MIT licence terms. Choose pyrra if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.