Netpress Docs
Why Netpress
- Express is easy to start, but many teams end up rebuilding architecture by hand.
- NestJS gives structure, but often with more ceremony than the app actually needs.
- Netpress is the middle ground: clean architecture, a service container, lazy-loaded systems, and predictable patterns that stay readable.
Quick Comparison
| Topic | Express | NestJS | Netpress |
|---|---|---|---|
| Structure | Minimal by default | Strong, framework-driven | Clear by default |
| Complexity | Low at first, grows later | High | Moderate and predictable |
| Boilerplate | Low early, custom later | High | Low-to-moderate |
| Flexibility | Maximum | Structured | Structured without lock-in |
Key Features
- Dependency Injection Container for shared services and infrastructure clients
- Service Providers for explicit bootstrapping and lazy loading
- Controller -> Service pattern for clear backend flow
- Built-in Auth in core and optional NetPress Permissions for roles and abilities
- Validation system through request classes or inline rules
- Queue / Mail / Cache / Storage support that loads only when needed
The Pattern
- Controller handles the HTTP layer.
- Service handles business logic.
- Provider wires infrastructure and bootstrapping.
- Response stays consistent across the app.
Get Started
- Get Started and create a new app.
- Build your first app to learn the flow quickly.
- Read Architecture Overview for the framework shape.
- Scan Feature Overview to see what ships in core.