head to head · open source
Uptime Kuma vs telemetry
Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. telemetry has 923 stars, 76 forks, 6 open issues and last shipped 1 months ago. Uptime Kuma leads on adoption by 9,996% (93,190 vs 923 stars). Uptime Kuma is written in JavaScript under MIT; telemetry is written in Erlang under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, telemetry 8%. 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 | telemetry | |
|---|---|---|
| GitHub stars | ★ 93K | ★ 923 |
| License | MIT | Apache-2.0 |
| Written in | JavaScript | Erlang |
| Last push | 2026-11-02 | 2026-09-30 |
| Forks | ⑂ 8.7K | ⑂ 76 |
| 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 telemetry if
- You want the telemetry feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Erlang
- You evaluated both and telemetry 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 telemetry
Telemetry Documentation Telemetry is a lightweight library for dynamic dispatching of events, with a focus on metrics and instrumentation. Any Erlang or Elixir library can use telemetry to emit events. Application code and other libraries can then hook into those events and run custom handlers. Note: this library is agnostic to tooling and therefore is not directly related to OpenTelemetry. For OpenTelemetry in the Erlang VM, see opentelemetry erlang, and check opentelemetry telemetry to connect both libraries. Usage In a nutshell, you register a custom module and function to be invoked for certain events, which…
read the full telemetry 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 telemetry more popular?
Uptime Kuma has 93,190 GitHub stars and telemetry has 923. Uptime Kuma has the larger community by that measure.
Are Uptime Kuma and telemetry free?
Both are open source. Uptime Kuma is licensed under MIT and telemetry under Apache-2.0. Neither carries a licence fee.
What is the difference between Uptime Kuma and telemetry?
Uptime Kuma is written in JavaScript and telemetry in Erlang. 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 telemetry?
Choose Uptime Kuma if you want the larger community (93,190 stars) or its MIT licence terms. Choose telemetry if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.