FastAPI vs NestJS
Of the 195 makers' products we know the backend framework of, 30 chose FastAPI (15%) and 21 NestJS (11%). Among the 44 launched in 2025, FastAPI is in 16% 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, 3 public pull requests moved projects from FastAPI 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
- Your backend needs Python for AI or data work
Use it whenYour backend needs Python for AI or data work.
Trade-offNo built-in ORM, admin or auth; you assemble those from separate libraries.
- 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 | 30 makers' products · 397 open-source projects | 21 makers' products · 70 open-source projects |
|---|---|---|
| Moved to it on GitHubpull requests since Oct 2024 | fewer than 3 | 3 from FastAPI |
| Downloads | 85.8M/wk | 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 | 26% 18 | 9% 6 | 69 |
| 2025 | 16% 7 | 20% 9 | 44 |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "FastAPI to NestJS" or the reverse — real code changes, by developers in general rather than makers only.
- 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
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.
We use FastAPI for our API written in Python. The tool is very easy to use and we believe this is part of the best combination for SaaS development.
As a Python-based product, FastAPI gave us the best capabilities to create an API-based low-code product.
Making API's has never been so simple, FastAPI has definitely saved us plenty of hours of development!
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.
- OpenAPI docs are generated automatically, so interactive documentation and typed client SDKs come almost for free. PHPH 2
- Type hints with Pydantic validation catch bad input and bugs during development rather than in production. PHHN
- It removes most API boilerplate, making it the fastest way to deliver a Python API or microservice. PHPH 2HN
- Its single-maintainer governance makes some teams weigh community-run alternatives like Litestar. HN
- 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
FastAPI or NestJS: which do makers choose?
Of the 195 makers' products we know the backend framework of, 30 chose FastAPI (15%) and 21 NestJS (11%). Among the 44 launched in 2025, FastAPI is in 16% 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, 3 public pull requests moved projects from FastAPI to NestJS, and 0 the other way. Choose FastAPI if your backend needs Python for AI or data work; choose NestJS if your TypeScript API will grow many domains and you want enforced structure.
When should I pick FastAPI over NestJS?
Pick FastAPI if: Your backend needs Python for AI or data work.
When should I pick NestJS over FastAPI?
Pick NestJS if: Your TypeScript API will grow many domains and you want enforced structure.
Are people switching from FastAPI to NestJS?
Public GitHub pull requests since 2024-10-02: 3 from FastAPI to NestJS.

