Hono is a small, fast web framework that runs almost anywhere JavaScript runs — Node.js, Cloudflare Workers, Deno, Bun, and even the edge. You write your API once, and the same code deploys to any of those runtimes without changes. That portability is its whole point.
Hono's API will feel familiar if you have used Express, but it is built on web standards like the Fetch API's Request and Response objects. That is why it can run in so many places: it does not depend on Node.js-specific APIs.
Here is a complete Hono app:
import { Hono } from 'hono';
const app = new Hono();
app.get('/hello/:name', (c) => {
return c.json({ hello: c.req.param('name') });
});
app.get('/health', (c) => c.text('OK'));
export default app;
The c object is the context for each request — it gives you parameters, query strings, headers, and helpers to return JSON, text, or HTML. Middleware works the same way: small functions that run before or after your handler, for logging, CORS, or authentication.
To start, run npm create hono@latest my-app, pick a runtime, and you get a working project. The same starter works for a Node.js server or a Cloudflare Worker — only the deployment target changes.
Hono is a great fit if you are building APIs that need to run on the edge, or if you want one codebase that can move between runtimes. It is also a good choice for small services where Express would be overkill and a raw server would be too bare.
The limits match its size. Hono is deliberately small, so features like validation, file uploads, and database helpers come from middleware or your own code. The ecosystem is growing fast but is still younger than Express or Fastify.
Try it by building one tiny API — a health check plus two or three endpoints — and deploying it to two different runtimes. That exercise shows you exactly what Hono is for.
Top comments (0)