Netpress Laravel-inspired backend framework for Node.js
Frameworkv0.1.14 Starterv0.1.12 Docsv1.0.3
Overview Installation Architecture CLI

Node.js Backend Framework

Netpress brings Laravel-style structure to Node.js.

Netpress is a Node.js backend framework for teams that want structure without ceremony.

Express gives you a blank folder. NestJS can feel heavier than the app needs. Netpress gives you the balance: clean architecture, a service container, lazy-loaded systems, and predictable patterns you can follow from day one.

  • Controller -> Service -> Response flow that stays easy to read
  • Service Providers for explicit bootstrapping and lazy loading
  • Built-in auth, validation, CLI tooling, and an optional permissions package
Netpress banner

Why teams choose it

  • Express: flexible, but every app invents its own structure
  • NestJS: powerful, but often too much ceremony for normal backends
  • Netpress: structured, practical, and easy to scale

Starter quick start

npx create-netpress-app my-app
cd my-app
cp .env.example .env
npm run artisan -- key:generate
npm run setup:rendering
npm run migrate
npm run seed
npm run dev
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

TopicExpressNestJSNetpress
StructureMinimal by defaultStrong, framework-drivenClear by default
ComplexityLow at first, grows laterHighModerate and predictable
BoilerplateLow early, custom laterHighLow-to-moderate
FlexibilityMaximumStructuredStructured 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

  1. Get Started and create a new app.
  2. Build your first app to learn the flow quickly.
  3. Read Architecture Overview for the framework shape.
  4. Scan Feature Overview to see what ships in core.