Hono vs NestJS
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 | 3 makers' products · 120 open-source projects | 21 makers' products · 62 open-source projects |
|---|---|---|
| Downloads | 55.9M/wk11.3× vs npm | 14.4M/wk−29% 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 |
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.
NestJS provides the backend architecture behind Cockpit.run. Its modular structure and TypeScript support made it easier to build a scalable infrastructure management system.
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! 🍕🔥
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

