head to head · open source
Uptime Kuma vs codeburn
Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. codeburn has 11,664 stars, 903 forks, 45 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 699% (93,190 vs 11,664 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%. codeburn 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 | codeburn | |
|---|---|---|
| GitHub stars | ★ 93K | ★ 12K |
| License | MIT | MIT |
| Written in | JavaScript | TypeScript |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 8.7K | ⑂ 903 |
| 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 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 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 codeburn
See where your AI spend goes. If CodeBurn shows you something your bill never did, star the repo so other developers find it, and consider sponsoring to keep 41 integrations honest. npx codeburn To keep it: npm install g codeburn or brew install codeburn . Needs Node.js 22.13+. Desktop app 0.9.25. The macOS builds are signed with a Developer ID and notarized by Apple. The problem Your bill gives you a month total. It does not break that down by project, by model or by task, and it does not show which part of it was wasted. Claude Code, Codex, Cursor and the rest each write a session file every time you use them…
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 93,190 GitHub stars and codeburn has 11,664. 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 (93,190 stars) or its MIT licence terms. Choose codeburn if its feature set, stack or MIT licence fits better. Both are self-hostable.