head to head · open source
Uptime Kuma vs parca
Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. parca has 5,007 stars, 271 forks, 206 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 1,761% (93,190 vs 5,007 stars). Uptime Kuma is written in JavaScript under MIT; parca is written in TypeScript under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, parca 5%. Uptime Kuma was the more recently maintained of the two, and both are self-hostable with no licence fee.
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 | parca | |
|---|---|---|
| GitHub stars | ★ 93K | ★ 5.0K |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | TypeScript |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 8.7K | ⑂ 271 |
| 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 parca if
- You want the parca feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches TypeScript
- You evaluated both and parca 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 parca
Continuous profiling for analysis of CPU, memory usage over time, and down to the line number. Saving infrastructure cost, improving performance, and increasing reliability. Features eBPF Profiler : A single profiler, using eBPF, automatically discovering targets from Kubernetes or systemd across the entire infrastructure with very low overhead. Supports C, C++, Rust, Go, and more! Open Standards : Both producing pprof formatted profiles with the eBPF based profiler, and ingesting any pprof formatted profiles allowing for wide language adoption and interoperability with existing tooling. Optimized Storage &…
read the full parca 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 parca more popular?
Uptime Kuma has 93,190 GitHub stars and parca has 5,007. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and parca free?
Both are open source. Uptime Kuma is licensed under MIT and parca under Apache-2.0. Neither carries a licence fee.
What is the difference between Uptime Kuma and parca?
Uptime Kuma is written in JavaScript and parca in TypeScript. 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 parca?
Choose Uptime Kuma if you want the larger community (93,190 stars) or its MIT licence terms. Choose parca if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.