head to head · open source

Uptime Kuma vs go-grpc-middleware

Uptime Kuma has 91,477 GitHub stars, 8,426 forks, 805 open issues and last shipped yesterday. go-grpc-middleware has 6,761 stars, 747 forks, 83 open issues and last shipped 21 days ago. Uptime Kuma leads on adoption by 1,253% (91,477 vs 6,761 stars). Uptime Kuma is written in JavaScript under MIT; go-grpc-middleware is written in Go under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, go-grpc-middleware 11%. 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 ★ 91K go-grpc-middleware ★ 6.8K category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

Uptime Kuma go-grpc-middleware
GitHub stars ★ 91K ★ 6.8K
License MIT Apache-2.0
Written in JavaScript Go
Last push 2026-09-17 2026-08-28
Forks ⑂ 8.4K ⑂ 747
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 go-grpc-middleware if

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

full go-grpc-middleware 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 go-grpc-middleware

go grpc middleware is an Apache 2.0 Go library published by the grpc ecosystem that provides ready to use gRPC interceptors — reusable middleware for authentication, logging, retries, metrics and panic recovery — for developers building Go microservices on gRPC.

read the full go-grpc-middleware 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 go-grpc-middleware more popular?

Uptime Kuma has 91,477 GitHub stars and go-grpc-middleware has 6,761. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and go-grpc-middleware free?

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

What is the difference between Uptime Kuma and go-grpc-middleware?

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

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