head to head · open source

Uptime Kuma vs witr

Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. witr has 22,906 stars, 808 forks, 17 open issues and last shipped 11 days ago. Uptime Kuma leads on adoption by 307% (93,190 vs 22,906 stars). Uptime Kuma is written in JavaScript under MIT; witr is written in Go under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, witr 4%. 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 (docker, 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 witr ★ 23K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

Uptime Kuma witr
GitHub stars ★ 93K ★ 23K
License MIT Apache-2.0
Written in JavaScript Go
Last push 2026-11-02 2026-10-23
Forks ⑂ 8.7K ⑂ 808
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 witr if

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

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

witr Why is this running? Trace any process, port, container, or file back to the exact chain that started it — one command, machine readable JSON, or an interactive TUI. 🎮 Try witr in your browser → Investigate a simulated Linux box — a guided tutorial and free play sandbox, no install required. Purpose • Installation • TUI • Flags • Core Concept • Examples Output Behavior • Platforms • Success Criteria • Sponsors 1. Purpose witr exists to answer a single question: Why is this running? When something is running on a system, whether it is a process, a service, or something bound to a port, there is always a…

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

Uptime Kuma has 93,190 GitHub stars and witr has 22,906. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and witr free?

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

What is the difference between Uptime Kuma and witr?

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

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