head to head · open source
Uptime Kuma vs evlog
Uptime Kuma has 91,498 GitHub stars, 8,431 forks, 805 open issues and last shipped today. evlog has 1,854 stars, 63 forks, 19 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 4,835% (91,498 vs 1,854 stars). Uptime Kuma is written in JavaScript under MIT; evlog is written in TypeScript under MIT. Uptime Kuma has attracted 9% as many forks as stars, evlog 3%. 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 8884 open source comparisons
Side by side
| Uptime Kuma | evlog | |
|---|---|---|
| GitHub stars | ★ 91K | ★ 1.9K |
| License | MIT | MIT |
| Written in | JavaScript | TypeScript |
| Last push | 2026-09-18 | 2026-09-17 |
| Forks | ⑂ 8.4K | ⑂ 63 |
| 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 evlog if
- You want the evlog feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and evlog 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 evlog
evlog Digging through logs is not observability. It's hope. A single request generates 10+ log lines. When production breaks at 3am, you're sifting scattered lines for a needle of signal. Your errors say "Something went wrong", which helps nobody. evlog is different. One wide event per operation. All the context. Errors that explain why and what to do next. Why evlog? The Problem The Solution Output: Built for AI Assisted Development We're in the age of AI agents writing and debugging code. When an agent encounters an error, it needs clear, structured context to understand what happened and how to fix it. Traditi…
read the full evlog 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 evlog more popular?
Uptime Kuma has 91,498 GitHub stars and evlog has 1,854. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and evlog free?
Both are open source. Uptime Kuma is licensed under MIT and evlog under MIT. Neither carries a licence fee.
What is the difference between Uptime Kuma and evlog?
Uptime Kuma is written in JavaScript and evlog 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 evlog?
Choose Uptime Kuma if you want the larger community (91,498 stars) or its MIT licence terms. Choose evlog if its feature set, stack or MIT licence fits better. Both are self-hostable.