“The entire backend is built on NestJS!”
Backend FrameworkMaker says so +1 · source ↗
NestJS
TypeScript/Node.js backend framework with a modular, decorator-based architecture inspired by Angular, built on Express or Fastify.
Works with AI agents:llms.txtCLINestJS is a server-side framework for Node.js that gives a backend a fixed architecture. Express and Fastify handle HTTP but leave structure to you; Nest adds a layout of modules, controllers and services, inspired by Angular, so that a growing codebase stays organized the same way across features and developers.
The model rests on dependency injection. You write classes marked with decorators: controllers map routes to methods, providers (services, repositories) hold the logic, and modules declare which providers they own and export. Nest builds the dependency graph at startup and injects instances where they are needed. Guards, pipes, interceptors and exception filters plug into the request pipeline for auth, validation and error handling. Underneath, an HTTP adapter runs either Express (the default) or Fastify, and their APIs stay reachable.
For a small team, the value is in the official integrations: modules for TypeORM, Drizzle, Mongoose and Sequelize (Prisma works through a provider), GraphQL with Apollo or Mercurius, WebSockets, and microservices over transports such as TCP, Redis, NATS, Kafka, RabbitMQ and gRPC. The CLI scaffolds projects and generates code, and new projects come with Vitest-based unit and end-to-end test setups.
Nest is written in TypeScript and expects it; plain JavaScript needs Babel. It requires a recent Node.js (20.19+ or 22.12+). The framework layer adds startup time, which the docs measure as a noticeable cold-start cost on serverless functions compared with bare Express.
Where it fits
How NestJS itself is built
7 tools, from its own code, website and Product Hunt page.
Who uses it
21 makers' products, each linked to the source that shows it, and 62 open-source projects that declare it in their code.
“Nest.js helps us create structured and maintainable backend applications. It’s great for building APIs and handling data efficiently.”
Backend FrameworkMaker says so · source ↗“Loved how structured and scalable it made our backend, especially for handling complex logic cleanly.”
Backend FrameworkMaker says so · source ↗“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.”
Backend FrameworkMaker says so · source ↗“Scalable, modular, and efficient—NestJS is the perfect choice for modern backend development.”
Backend FrameworkMaker says so · source ↗“Nest.js provides a solid architecture to keep the backend maintainable.”
Backend FrameworkMaker says so · source ↗“NestJS makes building efficient, reliable backends a breeze. JustBackend wouldn’t be as robust without it!”
Backend FrameworkMaker says so · source ↗“Great framework for building our backend”
Backend FrameworkMaker says so · source ↗“We picked Nest.js for its modular structure and scalability, ensuring our backend is robust and future-proof. Think of it as the oven where all your pizza appreciation orders get baked to perfection! 🍕🔥”
Backend FrameworkMaker says so · source ↗“ToolJet’s backend is built using NestJS, giving us a scalable, modular architecture for fast and reliable performance.”
Backend FrameworkMaker says so · source ↗“We chose NestJS for the backend because it brings structure and scalability to our codebase. With its built-in support for modules, decorators, and TypeScript, it makes building and maintaining complex features (like live collaboration and the API hub) much easier.”
Backend FrameworkMaker says so · source ↗“NestJS provides the backend architecture behind Cockpit.run. Its modular structure and TypeScript support made it easier to build a scalable infrastructure management system.”
Backend FrameworkMaker says so · source ↗“Makes building and securing APIs straightforward”
Backend FrameworkMaker says so · source ↗“Our backend is fully built with NestJS :)”
Backend FrameworkMaker says so · source ↗“Nest.js has been the ideal solution for our back-end development. Shoutout to the Nest.js team!”
Backend FrameworkMaker says so · source ↗“NestJS powers our high-performance APIs, ensuring scalability and rapid iteration for continuous innovation.”
Backend FrameworkMaker says so · source ↗“Thanks to NestJS to help me to build a backend with the different service needed”
Backend FrameworkMaker says so · source ↗“Node ecosystem provides lot of web-frameworks, we choose NestJS as our preferred choice.”
Backend FrameworkMaker says so · source ↗“Employed Next.js for its efficient loading and scalability, providing a robust foundation for Wellpin’s responsive interface. Its scalability and efficient data handling enhance user experience.”
Backend FrameworkMaker says so · source ↗Open source: a project that declares NestJS as a dependency in its public code — verifiable, but not necessarily a live product.
What makers say
15 makers on why they use NestJS, in their own words on Product Hunt.
We chose NestJS for the backend because it brings structure and scalability to our codebase. With its built-in support for modules, decorators, and TypeScript, it makes building and maintaining complex features (like live collaboration and the API hub) much easier.
UniDeckSep 2026 ↗We picked Nest.js for its modular structure and scalability, ensuring our backend is robust and future-proof. Think of it as the oven where all your pizza appreciation orders get baked to perfection! 🍕🔥
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.
ExstatsSep 2026 ↗NestJS provides the backend architecture behind Cockpit.run. Its modular structure and TypeScript support made it easier to build a scalable infrastructure management system.
Nest.js helps us create structured and maintainable backend applications. It’s great for building APIs and handling data efficiently.
SalesPortSep 2026 ↗Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
- 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
Reliability and open issues
- [Discussion] Who is using Nest in production?👍 334 · opened Aug 2018 · active Jul 2026
- KafkaJs seems not maintained anymore👍 57 · opened Feb 2024 · active Sep 2026
- `UploadFile()` should accept `Readable` instead of `Buffer`👍 24 · opened Feb 2024 · active Jul 2026
Who switches
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general. Open a row to see the pull requests.
Express → NestJS6+ PRs
- 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
Fastify → NestJS4+ PRs
- Proposal: migrate config-write service from Fastify to NestJSrackandhost/getmando · 2026-09-06
- Migrate from fastify to nestjsNexusSerg/shop-training-backend · 2026-05-20
- Migrate from fastify to nestjsNexusSerg/shop-training-backend · 2026-05-20
- refactor: migrate from Fastify to NestJS with Next.js frontendlucaskampi/video-chat-ai-backend · 2026-04-11
FastAPI → NestJS3 PRs
- feat: migrate backend from FastAPI to NestJSAryan-17008/Autonomous-Financial-Control-Tower · 2026-09-04
- refacto: migrate Python FastAPI microservices to NestJS monolithNoFastNoFun/m-dicail-backend · 2026-06-25
- Migrate backend from FastAPI to NestJS + TypeScriptunrealtryhard07/Ask-Circle-main-V2 · 2026-05-12
NestJS → Fastify4+ PRs
- Revert "feat(nestjs): switch the HTTP adapter from Express to Fastify"rolling-scopes/rsschool-app · 2026-08-12
- feat(nestjs): switch the HTTP adapter from Express to Fastifyrolling-scopes/rsschool-app · 2026-08-12
- Migrate NestJS HTTP adapter to Fastify00joaopedro/NextStockOficial · 2026-07-15
- refactor: migrate NestJS from Express to Fastifysamir1498/green-algeria-map · 2026-06-11
Alternatives to NestJS
All alternatives by situation →On Product Hunt, people weigh it against: Convex, SST, Next.js, AdonisJS.
Questions makers ask about NestJS
Can I use Fastify instead of Express with NestJS?
Yes. Express is the default, but Nest ships a FastifyAdapter, and since Nest abstracts the HTTP layer you can switch between the two. The docs suggest Fastify when raw speed matters, and Express for its larger middleware ecosystem. source ↗
Which databases and ORMs does it work with?
Any of them; Nest is database-agnostic. The team maintains integration packages for TypeORM, Drizzle, Mongoose and Sequelize, MikroORM has its own package, and Prisma is used by exposing its generated client through a provider. source ↗
Is NestJS suitable for serverless functions?
It can be, but cold starts are slower: in the docs' benchmark a Nest HTTP app took about 81 ms to start when bundled, against about 7 ms for plain Express. Bundling with webpack and using a standalone application (dependency injection without an HTTP server) cut that time. source ↗
Which Node.js version do I need?
Running a Nest app needs Node.js 20.19 or later (or 22.12+ on the 22 line), and the CLI's generators need an even newer release. The docs recommend the current active LTS. source ↗
Does it support GraphQL?
Yes, through the official @nestjs/graphql module, which can run on Apollo Server or Mercurius; you can also write a custom driver. source ↗
Can I split my backend into microservices later?
Nest has a microservices package with built-in transporters, using TCP by default. Most transporters support both request-response and events, and you can change transport without rewriting handlers. source ↗
How does testing work?
The CLI scaffolds unit and end-to-end tests, new projects use Vitest and Supertest, and Nest's testing module makes dependency injection available in tests so components can be mocked. You can swap in another test runner. source ↗
Is there commercial support?
Yes. The NestJS core team offers official paid support and consulting, including architecture reviews, code reviews and mentoring. source ↗
Is NestJS free?
Yes — it is free, open-source software.
Is NestJS open source or self-hostable?
Open source, and you can self-host it. source ↗
Can AI coding agents work with NestJS?
It serves an llms.txt docs index; it has an official CLI (@nestjs/cli).
Who uses NestJS?
21 makers' products we track, each with a source, and 62 open-source projects declare it in their code. source ↗