head to head · open source

Uptime Kuma vs gofr

Uptime Kuma has 93,190 GitHub stars, 8,655 forks, 805 open issues and last shipped yesterday. gofr has 20,820 stars, 1,789 forks, 132 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 348% (93,190 vs 20,820 stars). Uptime Kuma is written in JavaScript under MIT; gofr is written in Go under Apache-2.0. Uptime Kuma has attracted 9% as many forks as stars, gofr 9%. gofr 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 gofr ★ 21K category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

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

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

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

Go Fr GoFr: An Opinionated Microservice Development Framework Listed in the CNCF Landscape 🎯 Goal GoFr is designed to simplify microservice development , with a key focus on Kubernetes deployment and out of the box observability . While capable of building generic applications, microservices remain at its core. 💡 Key Features 1. Simple API Syntax 2. REST Standards by Default 3. Configuration Management 4. Observability (Logs, Traces, Metrics) 5. Inbuilt Auth Middleware & Custom Middleware Support 6. gRPC Support 7. HTTP Service with Circuit Breaker Support 8. Pub/Sub 9. Health Check for All Datasources 10…

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

Uptime Kuma has 93,190 GitHub stars and gofr has 20,820. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and gofr free?

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

What is the difference between Uptime Kuma and gofr?

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

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