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.
Which fits you
- 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.
- 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
| Used by | 3 makers' products · 417 open-source projects | 21 makers' products · 70 open-source projects |
|---|---|---|
| Moved to it on GitHubpull requests since Oct 2024 | fewer than 3 | 6+ from Express |
| Downloads | 129.1M/wk−24% vs npm | 14.5M/wk−26% vs npm |
| Pricing | Free (open source). | Free (open source); paid enterprise support and courses available separately. |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · 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).
| Launched | Products | ||
|---|---|---|---|
| 2024 | 0% 0 | 9% 6 | 69 |
| 2025 | 0% 0 | 20% 9 | 44 |
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.
- Migrate the API from Express to NestJSmahyudi-fitri/moneypilot · 2026-09-28
- Migrate API from Express to NestJS + TypeScriptKathiravan292/blogserver · 2026-09-24
- Rewrite backend from Express to NestJS with Clean ArchitectureBernardoSsilva/Forenser-backend · 2026-09-14
- refactor: migrate cinema-booking-api from Express to NestJSkubrak-j/cinema-booking-api · 2026-09-11
- Migration from express to NestJSCHEESOM11/huddle · 2026-09-09
- refactor: migrate application from Express to NestJSKhdavid332/TeqTag · 2026-09-02
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.
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.
Currently, for our tech stack I’m using mongoDB as a database, nodejs/express as the server and Vue/Nuxt on the front end.
Our Tech Stack Node.js and express MongoDB Nginx Reactjs Nextjs<
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.
Nest.js helps us create structured and maintainable backend applications. It’s great for building APIs and handling data efficiently.
Loved how structured and scalable it made our backend, especially for handling complex logic cleanly.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- 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
- 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
Who uses each
What makers pair each with
Neither quite right?
See the whole backend framework decision →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.

