head to head · open source

gofr vs logchef

gofr has 20,909 GitHub stars, 1,760 forks, 132 open issues and last shipped 2 days ago. logchef has 899 stars, 56 forks, 9 open issues and last shipped 4 days ago. gofr leads on adoption by 2,226% (20,909 vs 899 stars). gofr is written in Go under Apache-2.0; logchef is written in Go under AGPL-3.0. gofr has attracted 8% as many forks as stars, logchef 6%. gofr was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (logging), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

gofr ★ 21K logchef ★ 899 category Infrastructure & Operations

← all 20902 open source comparisons

Side by side

gofr logchef
GitHub stars ★ 21K ★ 899
License Apache-2.0 AGPL-3.0
Written in Go Go
Last push 2026-09-18 2026-09-16
Forks ⑂ 1.8K ⑂ 56
Self-hosting Yes Yes
Data ownership Your server Your server

pick gofr if

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

full gofr profile →

pick logchef if

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

full logchef profile →

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 →

About logchef

Logchef is a lightweight, self hosted log analytics and observability interface for ClickHouse and VictoriaLogs, shipped as a single Go binary under the AGPL 3.0 licence, intended for teams that want a strong query and control plane on top of the log backends they already run.

read the full logchef overview →

More in Infrastructure & Operations

kubernetes ★ 128K Immich ★ 115K frp ★ 110K Uptime Kuma ★ 92K worldmonitor ★ 87K mall ★ 85K

Related comparisons

n8n vs huginn uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana uptime-kuma vs prometheus netdata vs grafana n8n vs kestra langchain vs haystack kubernetes vs rancher ansible vs compose ansible vs conductor ansible vs xxl-job ansible vs gitleaks ansible vs kestra kubernetes vs docker kubernetes vs kong kubernetes vs portainer kubernetes vs trivy kubernetes vs opentofu kubernetes vs jenkins kubernetes vs pulumi kubernetes vs floci

More Monitoring & Observability projects

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

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

Frequently asked questions

Is gofr or logchef more popular?

gofr has 20,909 GitHub stars and logchef has 899. gofr has the larger community by that measure.

Are gofr and logchef free?

Both are open source. gofr is licensed under Apache-2.0 and logchef under AGPL-3.0. Neither carries a licence fee.

What is the difference between gofr and logchef?

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

Choose gofr if you want the larger community (20,909 stars) or its Apache-2.0 licence terms. Choose logchef if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.