fiber
Fiber is a fast, Express-inspired web framework for Go built on top of the high-performance fasthttp engine. It offers a familiar routing API, middleware, and zero memory allocation in the hot path, targeting developers who want rapid web/API development with low overhead.
Embed badge
[](https://opensources.dev/resource/fiber)MITPermissive — free to use in commercial and proprietary software, with attribution.View license →
Production readiness
4/5- Actively maintainedCommits in the last 6 months
- No known vulnerabilitiesNot yet scanned
- Clear, usable licenseMIT (permissive)
- Proven adoptionWidely used
- Has documentationDocumentation indexed
go get fiberOur analysis
A Go web framework with an Express.js-style API built on fasthttp instead of the standard net/http, emphasizing speed and low memory allocation.
When to use fiber
Good for high-throughput REST APIs and microservices where raw request throughput and low latency matter, and for teams coming from Node/Express who want a familiar developer ergonomics in Go.
When not to
Avoid when you need full compatibility with the standard net/http ecosystem (many middleware, HTTP/2, and libraries assume net/http), or when long-term stability and the broadest community support outweigh peak benchmark numbers — Gin, Echo, or chi may be safer.
Strengths
- Very fast, built on fasthttp with low/zero allocation goals
- Familiar Express-like API lowers the learning curve
- Rich built-in middleware and an active ecosystem
- Good documentation and quick-start friendliness
Trade-offs
- fasthttp is not net/http compatible, so some standard libraries and middleware don't work directly
- Limited HTTP/2 and certain edge-case protocol support compared to net/http
- fasthttp's context-reuse model can lead to subtle bugs if request data is held beyond the handler
- Less idiomatic for purists who prefer the standard library
Maturity
Mature and widely adopted with ~40k stars, frequent releases, an organized GitHub org with companion packages, and active maintenance; production-used but tied to fasthttp's trade-offs.