Wiring every service by hand at boot.
Modules & DI
- Modules own their providers
- Request-scoped container
- Explicit imports and exports
//docs v1.4
Build Rust backends without wiring everything by hand.
NestForge brings Nest-style structure to Axum: modules, dependency injection, guards, and interceptors built in. These docs cover building on it, and building it.
cargo install nestforge-cli- 01RouterAxum router, request context
- 02MiddlewareLogging, header preparation
- 03GuardsAccess rules, early exits
- 04InterceptorsWrap handler execution
- 05HandlerYour code, finally
- 06ResponseFilters run, 200 leaves
// What NestForge Solves
Built-in solutions for the hard problems
Auth checks scattered across every handler.
Guards & Interceptors
- Typed guards with early rejection
- Composable interceptor pipelines
- Middleware bindings, declaratively
API docs that rot behind the code.
OpenAPI
- Schemas derived from handlers
- Auth documented end-to-end
- Always in sync with the router
A new database, a new mess of glue.
Data Layer
- SQL and Mongo workflows
- Redis caching built in
- Transactions without ceremony
REST today, gRPC tomorrow, rewrite everything.
Transports
- Same handlers, many transports
- GraphQL, gRPC, WebSockets
- Microservices out of the box
Untested glue holding it all together.
Testing & CLI
- Test harness per feature module
- Scaffold a feature in seconds
- One command, a running API
// The Mental Model
Every module declares its wiring
The #[module] attribute tells the injector everything it needs. Nothing is wired by hand, nothing is hidden.
- No more manual constructor plumbing
- Dependencies are explicit, nothing is hidden
- The compiler catches what you miss
#[module](
imports = [DatabaseModule],
controllers = [UsersController],
providers = [UsersService],
exports = [UsersService]
)
pub struct UsersModule;
imports = [DatabaseModule],
controllers = [UsersController],
providers = [UsersService],
exports = [UsersService]
)
pub struct UsersModule;
imports
Pull in providers exported by other modules.
controllers
Route handlers instantiated with the module.
providers
Services built by the injector, shared in scope.
exports
The subset other modules may use.
// Documentation
Everything the docs cover
// FAQ
Questions we get asked a lot
Can't find what you're looking for? Open an issue. The framework is developed in the open.
Ask on GitHubWhy a Nest-style framework in Rust?
Structure scales. Nest proved that opinionated architecture, with modules, dependency injection, and guards, removes a whole class of decisions. NestForge brings that structure to Axum without the runtime cost of a JavaScript framework.
Is NestForge just macros over Axum?
Macros are the surface. Underneath there is a real dependency injector, a request-scoped container, and a guard and interceptor pipeline that Axum alone does not give you.
Can I drop down to plain Axum?
Yes. Every handler is an Axum handler. You can mount raw routes beside NestForge modules and migrate one feature at a time.
What does the CLI scaffold?
A complete feature module: DTOs, service, controller, tests, and OpenAPI registration, wired into your workspace and ready to run.
How does it handle multiple databases?
Data layer modules wrap SQL, Mongo, and Redis behind the same provider interface, so swapping a store does not ripple through your services.