head to head · open source

Uptime Kuma vs client_js

Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. client_js has 3,498 stars, 431 forks, 50 open issues and last shipped 2 days ago. Uptime Kuma leads on adoption by 2,564% (93,190 vs 3,498 stars). Uptime Kuma is written in JavaScript under MIT; client_js is written in JavaScript under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, client_js 12%. Uptime Kuma was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (monitoring), 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 client_js ★ 3.5K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

Uptime Kuma client_js
GitHub stars ★ 93K ★ 3.5K
License MIT Apache-2.0
Written in JavaScript JavaScript
Last push 2026-11-02 2026-11-01
Forks ⑂ 8.7K ⑂ 431
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 client_js if

  • You want the client_js feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches JavaScript
  • You evaluated both and client_js fits your workflow better

full client_js 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 client_js

Prometheus client for Node.js A prometheus client for Node.js that supports histogram, summaries, gauges and counters. Installation This package was previously published as prom client . See the CHANGELOG for the breaking changes involved in upgrading. API See example folder for a sample usage. The library does not bundle any web framework. To expose the metrics, respond to Prometheus's scrape requests with the result of await registry.metrics() . Default metrics There are some default metrics recommended by Prometheus itself. To collect these, call collectDefaultMetrics . In addition, some Node.js specific…

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

Uptime Kuma has 93,190 GitHub stars and client_js has 3,498. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and client_js free?

Both are open source. Uptime Kuma is licensed under MIT and client_js under Apache-2.0. Neither carries a licence fee.

What is the difference between Uptime Kuma and client_js?

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

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