gofr
GoFr is an opinionated Go framework for building microservices with built-in support for databases, observability (logs, traces, metrics), and Kubernetes deployment. It provides REST APIs, gRPC, authentication middleware, and health checks out-of-the-box, designed to reduce boilerplate and accelerate microservice development.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | gofr-dev/gofr |
| Owner | gofr-dev |
| Primary language | Go |
| License | Apache-2.0 — OSI-approved |
| Stars | 21.2k |
| Forks | 1.8k |
| Open issues | 104 |
| Latest release | v1.57.0 (2026-06-24) |
| Last updated | 2026-07-07 |
| Source | https://github.com/gofr-dev/gofr |
What gofr is
GoFr is a Go 1.24+ framework offering HTTP/gRPC routing, OpenTelemetry integration for observability, database abstraction with migration support, pub/sub messaging, circuit breaker-enabled HTTP clients, cron job scheduling, and middleware support. It enforces microservice patterns through configuration management and standardized health checks across all datasources.
Get the gofr source
Clone the repository and explore it locally.
git clone https://github.com/gofr-dev/gofr.gitcd gofr# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Go 1.24 or above; upgrade Go version before adoption if not already current.
- Opinionated design means configuration patterns and middleware hooks follow GoFr conventions; team must adopt or work around these patterns.
- Built-in observability requires OpenTelemetry setup and compatible backends (e.g., Jaeger, Prometheus); ensure observability infrastructure is in scope.
- Database abstraction and migration tooling are included; review whether existing migrations or schemas require refactoring.
- gRPC and pub/sub support are optional but present; evaluate whether message broker setup (Kafka, RabbitMQ, etc.) is needed for your use case.
When to avoid it — and what to weigh
- Monolithic or generic web application — GoFr is explicitly opinionated toward microservices; if building a monolith, traditional Go frameworks (Gin, Echo) or a lighter approach may be more suitable.
- Minimal dependencies required — GoFr brings database, observability, and messaging abstractions by default; projects with strict dependency minimalism should evaluate if overhead is acceptable.
- Non-Go tech stack — GoFr is Go-only; polyglot or non-Go teams should consider language-agnostic frameworks or language-specific alternatives.
- Legacy or non-standard deployment environments — GoFr's design assumes modern cloud-native practices; highly constrained or unusual deployment scenarios may conflict with its opinionated architecture.
License & commercial use
GoFr is licensed under Apache License 2.0 (SPDX: Apache-2.0), a permissive OSI-approved license. This license permits commercial use, modification, and distribution with minimal restrictions; includes liability limitations.
Apache 2.0 is a permissive OSI license that explicitly permits commercial use. You may use GoFr in proprietary products and closed-source applications. Standard license obligations apply: include license text and notice of modifications if distributed. No patent indemnification; review patent provisions if intellectual property risk is a concern. Consult legal counsel for high-stakes commercial deployments.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Strong |
| Assessment confidence | High |
Apache 2.0 license does not assert or warrant security. Review GoFr's source code for your risk model. Framework includes auth middleware abstraction and dependency management via Go modules. Standard supply-chain and dependency scanning practices apply. No security posture claims are stated in the data; evaluate based on your threat model and use case sensitivity. Ensure observability backend (if used) is secured appropriately.
Alternatives to consider
Gin
Lightweight, high-performance HTTP framework with minimal opinionation; better for projects not requiring built-in observability or microservice patterns.
Echo
Modular Go web framework with similar REST/HTTP capabilities but lower overhead; suitable if you prefer composing your own observability and database layers.
gRPC with protobuf
Lower-level, language-agnostic RPC framework; appropriate for polyglot teams or projects with strict latency/serialization requirements rather than HTTP microservices.
Build on gofr with DEV.co software developers
GoFr streamlines microservice development with opinionated patterns, observability, and cloud-native design. Review the framework's suitability for your team's Go stack, deployment model, and observability needs.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
gofr FAQ
Does GoFr require Kubernetes?
Can I use GoFr without OpenTelemetry?
What databases does GoFr support?
Is GoFr production-ready?
Software development & web development with DEV.co
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If gofr is part of your open-source observability roadmap, our team can implement, customize, migrate, and maintain it.
Evaluate GoFr for Your Microservice Architecture
GoFr streamlines microservice development with opinionated patterns, observability, and cloud-native design. Review the framework's suitability for your team's Go stack, deployment model, and observability needs.