head to head · open source

Uptime Kuma vs GoModel

Uptime Kuma has 91,498 GitHub stars, 8,431 forks, 805 open issues and last shipped yesterday. GoModel has 1,167 stars, 101 forks, 80 open issues and last shipped yesterday. Uptime Kuma leads on adoption by 7,740% (91,498 vs 1,167 stars). Uptime Kuma is written in JavaScript under MIT; GoModel is written in Go under MIT. Uptime Kuma has attracted 9% as many forks as stars, GoModel 9%. GoModel 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 GoModel ★ 1.2K category Infrastructure & Operations

← all 13541 open source comparisons

Side by side

Uptime Kuma GoModel
GitHub stars ★ 91K ★ 1.2K
License MIT MIT
Written in JavaScript Go
Last push 2026-09-18 2026-09-18
Forks ⑂ 8.4K ⑂ 101
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 GoModel if

  • You want the GoModel feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Go
  • You evaluated both and GoModel fits your workflow better

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

GoModel is an MIT licensed AI gateway, control plane and proxy written in Go that exposes one OpenAI compatible endpoint at /v1 and one Anthropic compatible endpoint at /v1/messages in front of OpenAI, Anthropic, Gemini, Groq, xAI, Ollama, vLLM and many other providers, for teams that run their own LLM traffic and want routing, caching, spend control and observability in a single self hosted service.

read the full GoModel 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 prometheus uptime-kuma vs openvpn uptime-kuma vs wr-do uptime-kuma vs plakar uptime-kuma vs pluton n8n vs huginn worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana n8n vs kestra langchain vs haystack llama-index vs haystack compose vs conductor compose vs xxl-job langgraph vs haystack compose vs gitleaks trivy vs gitleaks supabase vs nocodb mall vs prometheus mall vs nocodb supabase vs postgrest

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 GoModel more popular?

Uptime Kuma has 91,498 GitHub stars and GoModel has 1,167. Uptime Kuma has the larger community by that measure.

Are Uptime Kuma and GoModel free?

Both are open source. Uptime Kuma is licensed under MIT and GoModel under MIT. Neither carries a licence fee.

What is the difference between Uptime Kuma and GoModel?

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

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