head to head · open source

Uptime Kuma vs slog

Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. slog has 1,706 stars, 98 forks, 57 open issues and last shipped 5 months ago. Uptime Kuma leads on adoption by 5,362% (93,190 vs 1,706 stars). Uptime Kuma is written in JavaScript under MIT; slog is written in Rust under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, slog 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.

Uptime Kuma ★ 93K slog ★ 1.7K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

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

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

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

Getting started Introduction FAQ Crate list slog rs The Logging for [Rust][rust] You might consider using tracing instead It's been a while since slog was created and it served Rust community well all this time. It remains a stable, featureful and battle tested library, used in many important projects. In last few years, another ecosystem for Rust was created with similar features and a very good support for debugging async code and already larger dev team and community. Please check tracing and see if it is more suitable for your use case. It seems that it is already a go to logging/tracing solution for Rust…

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

Uptime Kuma has 93,190 GitHub stars and slog has 1,706. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and slog free?

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

What is the difference between Uptime Kuma and slog?

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

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