How it works
Hono (Japanese for 'flame') uses the standard Request and Response objects that browsers, Deno, Bun and edge platforms share, instead of Node's own types. That lets one app deploy to Cloudflare Workers, Deno, Bun, AWS Lambda, Vercel or Node.js with a small adapter at most. The core has no dependencies, and its smallest preset is under 14 KB.
It ships middleware for common jobs (CORS, JWT checks, logging, caching, secure headers) and a validator that works with Zod. In RPC mode a typed client (hc) reads the server's route types, giving tRPC-style end-to-end type safety over plain HTTP. Its API feels familiar to anyone who has used Express.
Hono pros and cons
Pros
- Runs on almost every JavaScript runtime and edge platform
- Tiny and quick to start, which suits serverless cold starts
- Written in TypeScript, with an optional typed RPC client
- Useful middleware included out of the box
Cons
- Younger ecosystem than Express or Fastify
- Node-only libraries may not work on the edge runtimes it targets
When to use Hono
Pick it when
- APIs on Cloudflare Workers, Deno Deploy, Bun or other edge platforms
- One codebase that can move between hosts
- Small typed APIs beside a TypeScript frontend
Skip it when
- The app depends on a large set of Express-specific middleware
Hono pricing
Hono vs the alternatives
Related terms
More in Backend and APIs
Frameworks