head to head · open source
Uptime Kuma vs cost-xray
Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. cost-xray has 5,825 stars, 375 forks, 13 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 1,500% (93,190 vs 5,825 stars). Uptime Kuma is written in JavaScript under MIT; cost-xray is written in Python under MIT. Uptime Kuma has attracted 9% as many forks as stars, cost-xray 6%. 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 | cost-xray | |
|---|---|---|
| GitHub stars | ★ 93K | ★ 5.8K |
| License | MIT | MIT |
| Written in | JavaScript | Python |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 8.7K | ⑂ 375 |
| 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 cost-xray if
- You want the cost-xray feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and cost-xray 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 cost-xray
cost xray See what your AI coding agent actually sends to the API — and what each part costs. Most usage tools read local logs. That shows the total cost of a call or session, but it misses the request time context assembled before the model is invoked: system prompts, tool schemas, MCP blocks, tool results, cache reads/writes, and previous thinking blocks. cost xray captures the actual local API traffic for Claude Code and Codex, then attributes tokens and dollars back to the sources inside the request. It shows not just how much a turn cost, but why it cost that much. Home — every session by agent · project ·…
read the full cost-xray 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 cost-xray more popular?
Uptime Kuma has 93,190 GitHub stars and cost-xray has 5,825. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and cost-xray free?
Both are open source. Uptime Kuma is licensed under MIT and cost-xray under MIT. Neither carries a licence fee.
What is the difference between Uptime Kuma and cost-xray?
Uptime Kuma is written in JavaScript and cost-xray in Python. 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 cost-xray?
Choose Uptime Kuma if you want the larger community (93,190 stars) or its MIT licence terms. Choose cost-xray if its feature set, stack or MIT licence fits better. Both are self-hostable.