head to head · open source

beszel vs gofr

beszel has 25,459 GitHub stars, 1,019 forks, 313 open issues and last shipped yesterday. gofr has 20,916 stars, 1,759 forks, 132 open issues and last shipped yesterday. beszel leads on adoption by 22% (25,459 vs 20,916 stars). beszel is written in Go under MIT; gofr is written in Go under Apache-2.0. beszel has attracted 4% as many forks as stars, gofr 8%. beszel 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.

beszel ★ 25K gofr ★ 21K category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

beszel gofr
GitHub stars ★ 25K ★ 21K
License MIT Apache-2.0
Written in Go Go
Last push 2026-09-17 2026-09-17
Forks ⑂ 1.0K ⑂ 1.8K
Self-hosting Yes Yes
Data ownership Your server Your server

pick beszel if

  • You weight community size — 25K stars and counting
  • You want the MIT license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

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

Beszel is a lightweight server monitoring platform written in Go and released under the MIT License. It consists of two components: a hub, which is a web application built on PocketBase and provides the dashboard for viewing and managing connected systems, and an agent, which runs on each system being monitored and communicates system metrics back to the hub. The project lives in the self hosted, homelab oriented monitoring ecosystem, alongside the broader category of Infrastructure and Operations tooling, and it is distributed primarily through Docker images published as henrygd/beszel for the hub and henrygd/be…

read the full beszel overview →

About gofr

GoFr is an opinionated Go framework for building microservices, aimed at Go developers and platform teams who want HTTP, gRPC, data access and observability built in rather than assembled from separate libraries.

read the full gofr overview →

More in Infrastructure & Operations

Immich ★ 114K Uptime Kuma ★ 91K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K

Related comparisons

uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana uptime-kuma vs huginn 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 mall vs orm prometheus vs nocodb mall vs milvus mall vs tidb

More Monitoring & Observability projects

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

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

Frequently asked questions

Is beszel or gofr more popular?

beszel has 25,459 GitHub stars and gofr has 20,916. beszel has the larger community by that measure.

Are beszel and gofr free?

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

What is the difference between beszel and gofr?

beszel is written in Go 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, beszel or gofr?

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