head to head · open source

Uptime Kuma vs xray-checker

Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. xray-checker has 933 stars, 92 forks, 20 open issues and last shipped 2 months ago. Uptime Kuma leads on adoption by 9,888% (93,190 vs 933 stars). Uptime Kuma is written in JavaScript under MIT; xray-checker is written in Go under AGPL-3.0. Uptime Kuma has attracted 9% as many forks as stars, xray-checker 10%. Uptime Kuma was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (monitoring, uptime), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Uptime Kuma ★ 93K xray-checker ★ 933 category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

Uptime Kuma xray-checker
GitHub stars ★ 93K ★ 933
License MIT AGPL-3.0
Written in JavaScript Go
Last push 2026-11-02 2026-09-10
Forks ⑂ 8.7K ⑂ 92
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

full Uptime Kuma profile →

pick xray-checker if

  • You want the xray-checker feature set and don't need the biggest community
  • You prefer the AGPL-3.0 license terms
  • Your stack matches Go
  • You evaluated both and xray-checker fits your workflow better

full xray-checker profile →

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 xray-checker

Xray Checker Xray Checker is a tool for monitoring proxy server availability with support for VLESS, VMess, Trojan, and Shadowsocks protocols. It automatically tests connections through Xray Core and provides metrics for Prometheus, as well as API endpoints for integration with monitoring systems. [!TIP] Try the Live Demo: See Xray Checker in action at demo xray checker.kutovoy.dev 🚀 Key Features 🔍 Monitoring of Xray proxy servers (VLESS, VMess, Trojan, Shadowsocks) 🔄 Automatic configuration updates from subscription (multiple subscriptions supported) 📊 Prometheus metrics export with Pushgateway support 🌐…

read the full xray-checker 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 xray-checker more popular?

Uptime Kuma has 93,190 GitHub stars and xray-checker has 933. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and xray-checker free?

Both are open source. Uptime Kuma is licensed under MIT and xray-checker under AGPL-3.0. Neither carries a licence fee.

What is the difference between Uptime Kuma and xray-checker?

Uptime Kuma is written in JavaScript and xray-checker in Go. 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 xray-checker?

Choose Uptime Kuma if you want the larger community (93,190 stars) or its MIT licence terms. Choose xray-checker if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.