Updated

Express vs NestJS

Of the 195 makers' products we know the backend framework of, 21 chose NestJS (11%) and 3 Express (2%). Among the 44 launched in 2025, Express is in 0% and NestJS in 20%. They're different kinds of tool, minimal router and structured TypeScript, so the counts don't measure the same choice. On GitHub, 6 public pull requests moved projects from Express to NestJS, and 0 the other way.

Two sides of the backend framework decision: minimal router and structured TypeScript. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Express if
  • You want a Node.js API server with schema validation and good throughput

Use it whenYou're following a tutorial or need a specific Express middleware.

Trade-offOlder design; types, validation and structure are all up to you.

Choose NestJS if
  • Your TypeScript API will grow many domains and you want enforced structure

Use it whenYour API will grow many domains and you want Angular-style structure.

Trade-offMore boilerplate and ceremony than a solo project usually needs.

At a glance

ExpressNestJS
Used by3 makers' products · 417 open-source projects21 makers' products · 70 open-source projects
Moved to it on GitHubpull requests since Oct 2024fewer than 36+ from Express
Downloads129.1M/wk−24% vs npm14.5M/wk−26% vs npm
PricingFree (open source).Free (open source); paid enterprise support and courses available separately.
Free tierYesYes
Open sourceYes · self-hostableYes · self-hostable

New launches vs older products

A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the backend framework decision (by the year they launched on Product Hunt).

LaunchedExpressNestJSProducts
20240% 09% 669
20250% 020% 944

Who moves from one to the other

Public pull requests on GitHub since Oct 2024 whose title says "Express to NestJS" or the reverse — real code changes, by developers in general rather than makers only.

Fewer than 3 pull requests move from NestJS to Express.
Express → NestJS6+ PRs
All matching pull requests on GitHub ↗

What makers say

Makers on using it for backend framework, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.

On Express
Ghostboard started as an ExpressJS monolith in a $5 server on Digitalocean as a prototype for my blog: simple, low-cost, and with a few features.
Ghostboard, the makerNov 2021 ↗
Currently, for our tech stack I’m using mongoDB as a database, nodejs/express as the server and Vue/Nuxt on the front end.
Pallyy, the makerOct 2021 ↗
Our Tech Stack Node.js and express MongoDB Nginx Reactjs Nextjs<
Scrapingdog, the makerMar 2022 ↗
On NestJS
NestJS powers the Exstats backend. Crawlers for Chrome, Edge, and Firefox stores, the GraphQL API behind the dashboard, and the scheduled jobs for alerts and aggregations all run on it.
Exstats, the makerSep 2026 ↗
Nest.js helps us create structured and maintainable backend applications. It’s great for building APIs and handling data efficiently.
SalesPort, the makerSep 2026 ↗
Loved how structured and scalable it made our backend, especially for handling complex logic cleanly.
Overflow AI, the makerSep 2026 ↗
12 more on the NestJS page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Express
Most loved
  • A plain Node and Express server is a simple, low-cost way to get a first product running on a small VPS. Starter StoryStarter Story 2Starter Story 3
  • It is battle-tested with a large middleware ecosystem, so developers keep it over newer runtime built-ins. HNHN 2
  • The minimal core lets you pick your own building blocks and keep dependencies few. HNHN 2
Watch-outs
  • With little convention, each app becomes a homegrown framework that is hard to pick back up months later. HNHN 2
  • End-to-end route typing needs extra libraries, pushing TypeScript teams toward newer frameworks or custom layers. HNHN 2
NestJS
Most loved
  • Modules, decorators and TypeScript give the backend a clear structure that stays maintainable as features grow complex. PHPH 2
  • One NestJS codebase can host the API, crawlers and scheduled jobs together. PHPH 2
  • Its Swagger integration derives the OpenAPI spec from validation rules and decorators, so docs stay in sync with code. HN
Watch-outs
  • Module boilerplate is heavy, and some developers dislike the framework outright. HNHN 2
On Product Hunt: 5.0★, 26 reviews · mentioned most: scalable architecture, maintainable architecture, modular architecture

Who uses each

What makers pair each with

With Express
HonoMinimal routerSmall TypeScript APIs that run on Node, Bun, Deno or edge platforms like Cloudflare Workers.vs Express →vs NestJS →
FastifyMinimal routerNode.js APIs that want low overhead, JSON-schema request validation and a structured plugin system.
FastAPIMinimal routerPython APIs with request validation and interactive docs generated from type hints.vs Express →vs NestJS →
DjangoBatteries includedPython apps that want an ORM, migrations, auth and an admin panel on day one.
Ruby on RailsBatteries includedFull-stack Ruby apps where one developer builds models, views, jobs and emails with strong conventions.
LaravelBatteries includedPHP apps with ORM, queues, auth scaffolding and an optional paid ecosystem for hosting and admin panels.

Questions

Express or NestJS: which do makers choose?

Of the 195 makers' products we know the backend framework of, 21 chose NestJS (11%) and 3 Express (2%). Among the 44 launched in 2025, Express is in 0% and NestJS in 20%. They're different kinds of tool, minimal router and structured TypeScript, so the counts don't measure the same choice. On GitHub, 6 public pull requests moved projects from Express to NestJS, and 0 the other way. Choose Express if you want a Node.js API server with schema validation and good throughput; choose NestJS if your TypeScript API will grow many domains and you want enforced structure.

When should I pick Express over NestJS?

Pick Express if: You want a Node.js API server with schema validation and good throughput.

When should I pick NestJS over Express?

Pick NestJS if: Your TypeScript API will grow many domains and you want enforced structure.

Are people switching from Express to NestJS?

Public GitHub pull requests since 2024-10-02: 6+ from Express to NestJS.