head to head · open source

Uptime Kuma vs m3

Uptime Kuma has 91,498 GitHub stars, 8,431 forks, 805 open issues and last shipped today. m3 has 4,896 stars, 463 forks, 222 open issues and last shipped today. Uptime Kuma leads on adoption by 1,769% (91,498 vs 4,896 stars). Uptime Kuma is written in JavaScript under MIT; m3 is written in Go under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, m3 9%. m3 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 ★ 91K m3 ★ 4.9K category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

Uptime Kuma m3
GitHub stars ★ 91K ★ 4.9K
License MIT Apache-2.0
Written in JavaScript Go
Last push 2026-09-18 2026-09-18
Forks ⑂ 8.4K ⑂ 463
Self-hosting Yes Yes
Data ownership Your server Your server

pick Uptime Kuma if

  • You weight community size — 91K 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 m3 if

  • You want the m3 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 m3 fits your workflow better

full m3 profile →

About Uptime Kuma

Uptime Kuma is a free, MIT licensed, self hosted monitoring tool with a reactive web dashboard, built for operators and teams that want to watch their own HTTP, TCP, and DNS endpoints and keep the resulting data on their own infrastructure.

read the full Uptime Kuma overview →

About m3

M3 is an Apache 2.0 licensed, Go based monorepo that provides a distributed time series database, query engine, metrics aggregator, and Prometheus sidecar for teams that need to store and query large volumes of metrics on their own infrastructure.

read the full m3 overview →

More in Infrastructure & Operations

Immich ★ 114K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K Grafana ★ 77K

Related comparisons

uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana uptime-kuma vs huginn uptime-kuma vs openvpn uptime-kuma vs wr-do uptime-kuma vs plakar uptime-kuma vs pluton worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana worldmonitor vs huginn immich vs paperless-ngx immich vs ceph immich vs filestash immich vs garage immich vs storj immich vs alarik immich vs spinifex paperless-ngx vs ceph mall vs prometheus mall vs nocodb mall vs etcd mall vs dbeaver

More Monitoring & Observability projects

Compare either of these against the rest of the Monitoring & Observability field.

Uptime Kuma vs worldmonitor Uptime Kuma vs NetData Uptime Kuma vs Grafana Uptime Kuma vs huginn Uptime Kuma vs Sentry Uptime Kuma vs SigNoz Uptime Kuma vs Grafana Loki Uptime Kuma vs beszel Uptime Kuma vs cilium Uptime Kuma vs Apache SkyWalking Uptime Kuma vs jaeger Uptime Kuma vs Vector

Frequently asked questions

Is Uptime Kuma or m3 more popular?

Uptime Kuma has 91,498 GitHub stars and m3 has 4,896. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and m3 free?

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

What is the difference between Uptime Kuma and m3?

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

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