Types should do real work
A request struct should guide the compiler, validate incoming data, and describe the public API—not be copied into several parallel formats.
Why EchoNext
Keep the speed. Strengthen the boundary.
Echo is an excellent HTTP foundation. EchoNext focuses on the repetitive contract work around it: binding, validation, response shapes, and OpenAPI documentation.
Adoption should be gradual
Typed routes and standard Echo handlers can coexist. Teams choose the abstraction where it improves clarity.
Documentation should agree
Generated OpenAPI is valuable because it is derived from the same route declarations and types that run the service.
Project principles
Echo remains visible
EchoNext embeds the Echo application. Its middleware ecosystem, context, groups, error handling, server options, and escape hatches remain part of the development model.
Core first, contrib by choice
The central package handles typed HTTP contracts. Database, configuration, middleware, observability, and testing helpers remain optional contrib packages.
Open development
Source, issues, discussions, examples, documentation, and the roadmap are public under the MIT license.
Explore the repository