head to head · open source
Uptime Kuma vs codeburn
Uptime Kuma has 91,477 GitHub stars, 8,426 forks, 805 open issues and last shipped yesterday. codeburn has 11,063 stars, 839 forks, 39 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 727% (91,477 vs 11,063 stars). Uptime Kuma is written in JavaScript under MIT; codeburn is written in TypeScript under MIT. Uptime Kuma has attracted 9% as many forks as stars, codeburn 8%. 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 | codeburn | |
|---|---|---|
| GitHub stars | ★ 91K | ★ 11K |
| License | MIT | MIT |
| Written in | JavaScript | TypeScript |
| Last push | 2026-09-17 | 2026-09-17 |
| Forks | ⑂ 8.4K | ⑂ 839 |
| 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 codeburn if
- You want the codeburn feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and codeburn 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 codeburn
CodeBurn is a free, open source, local first tool that tracks AI coding token usage and cost across 41 tools and agents, including Claude Code, Cursor, Codex, Gemini, and Grok. It is written in TypeScript, licensed under MIT, and lives in the developer tools and observability ecosystem as a command line utility with optional desktop surfaces. Every surface reads the session files that the supported tools already write to disk, so CodeBurn acts as one source of truth rather than a separate collection layer.
read the full codeburn 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 codeburn more popular?
Uptime Kuma has 91,477 GitHub stars and codeburn has 11,063. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and codeburn free?
Both are open source. Uptime Kuma is licensed under MIT and codeburn under MIT. Neither carries a licence fee.
What is the difference between Uptime Kuma and codeburn?
Uptime Kuma is written in JavaScript and codeburn 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 codeburn?
Choose Uptime Kuma if you want the larger community (91,477 stars) or its MIT licence terms. Choose codeburn if its feature set, stack or MIT licence fits better. Both are self-hostable.