Hono vs NestJS
Of the 195 makers' products we know the backend framework of, 21 chose NestJS (11%) and 5 Hono (3%). Among the 44 launched in 2025, Hono is in 5% and NestJS in 20%. They're different kinds of tool, minimal router and structured TypeScript, so the counts don't measure the same choice.
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 need a small TypeScript API, possibly on an edge runtime
Use it whenYou're deploying to an edge runtime or want one API that can move between runtimes.
Trade-offYou choose and wire the database, auth and validation yourself.
- 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 | 5 makers' products · 146 open-source projects | 21 makers' products · 70 open-source projects |
|---|---|---|
| Downloads | 61.5M/wk10× 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 | 3% 2 | 9% 6 | 69 |
| 2025 | 5% 2 | 20% 9 | 44 |
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 built Disco's MCP hub on Hono (leveraging the hono MCP package). DX is good and it's one of the more performant Typescript API framework. Works especially well with Cloudflare worker deployments
Enclosed backend is made with Hono, a good solution for multi-plateform service (Node, Cloudflare, ...)
Very simple and elegant HTTP API framework, we embed into NextJS as our HTTP API and tRPC server
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.
- 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
Hono or NestJS: which do makers choose?
Of the 195 makers' products we know the backend framework of, 21 chose NestJS (11%) and 5 Hono (3%). Among the 44 launched in 2025, Hono is in 5% and NestJS in 20%. They're different kinds of tool, minimal router and structured TypeScript, so the counts don't measure the same choice. Choose Hono if you need a small TypeScript API, possibly on an edge runtime; choose NestJS if your TypeScript API will grow many domains and you want enforced structure.
When should I pick Hono over NestJS?
Pick Hono if: You need a small TypeScript API, possibly on an edge runtime.
When should I pick NestJS over Hono?
Pick NestJS if: Your TypeScript API will grow many domains and you want enforced structure.

