MoroJS vs the field

Compared honestly.
Sources you can check.

Everyone evaluating MoroJS asks the same thing: why not just use Express, Fastify, NestJS, or Hono? Fair question. So here's the same endpoint written in each one, a feature-by-feature checklist, and benchmarks we didn't run: two independent projects that measure every framework on their own hardware.

The status quo

Every Node framework makes you choose

Speed or features. Simplicity or power. Type-safety or flexibility. You wire middleware in the right order and pray nothing breaks at 3am.

Express
Designed in 2010, with no types, no validation and no async-aware error handling. Every project ends up rebuilding the same handful of pieces.
Fastify
Fast, but you assemble the framework yourself: schemas, plugins, decorators, lifecycle hooks.
NestJS
Powerful, but heavy. Decorators, modules, providers, DI container. Java in TypeScript clothing.
Hono / Elysia
Small and fast, and that is the whole offer. Auth, validation, websockets and gRPC are yours to source, wire up and keep working.

MoroJS ships with all of it. You use only what you need.

Same endpoint, every framework

Less code. More guarantees.

The same validated POST endpoint in four frameworks. Identical behavior, wildly different effort.

moro · POST /users13 lines
import { createApp, z } from '@morojs/moro' const app = await createApp() app.post('/users')  .body(z.object({    name: z.string().min(1),    email: z.string().email(),    age: z.number().int().min(18),  }))  .handler((req) => {    return { id: crypto.randomUUID(), ...req.body }  }) app.listen(3000)
Result
All of it.
In one chainable call.
  • Schema, validation, types in one chain
  • req.body fully typed, already validated
  • Errors handled by intelligent defaults
  • No plugins. No boilerplate.
Feature parity, side by side

Everything in the box. Nothing to install.

Auth, validation, websockets, GraphQL, gRPC, HTTP/2, every one first-class and ready to use. No plugins to vet, no glue code to write.

FeatureExpressFastifyNestJSHonoMoroJS
Core
TypeScript nativeNot supportedVia plugin / communityBuilt-inBuilt-inBuilt-in
Zero-configVia plugin / communityNot supportedNot supportedVia plugin / communityBuilt-in
Intelligent middleware orderingNot supportedNot supportedNot supportedNot supportedBuilt-in
Multi-runtime (Node/Edge/Lambda/Workers)Not supportedNot supportedNot supportedBuilt-inBuilt-in
Validation
Zod / Joi / Yup supportVia plugin / communityVia plugin / communityVia plugin / communityVia plugin / communityBuilt-in
Type inference from schemaNot supportedVia plugin / communityVia plugin / communityVia plugin / communityBuilt-in
Auth
Built-in OAuth providersNot supportedNot supportedVia plugin / communityNot supportedBuilt-in
RBAC + sessions, zero depsNot supportedNot supportedVia plugin / communityNot supportedBuilt-in
Real-time
WebSocketsVia plugin / communityVia plugin / communityBuilt-inVia plugin / communityBuilt-in
Server-Sent EventsVia plugin / communityVia plugin / communityBuilt-inBuilt-inBuilt-in
GraphQLVia plugin / communityVia plugin / communityBuilt-inVia plugin / communityBuilt-in
gRPCVia plugin / communityVia plugin / communityBuilt-inNot supportedBuilt-in
HTTP/2 nativeNot supportedBuilt-inBuilt-inVia plugin / communityBuilt-in
Background work
Built-in job schedulerNot supportedNot supportedVia plugin / communityNot supportedBuilt-in
Worker threads facadeNot supportedNot supportedVia plugin / communityNot supportedBuilt-in
Mail (SES, SendGrid, Resend)Not supportedNot supportedVia plugin / communityNot supportedBuilt-in
Performance
Own native engine (default)Not supportedNot supportedNot supportedNot supportedBuilt-in
Built-in clusteringNot supportedNot supportedNot supportedNot supportedBuilt-in
req/sec on Node (The Benchmarker, independent)53k73k58k68k274k
Built-inVia plugin / communityNot supported
Independent results

Measured by people who aren't us

HttpArena and The Benchmarker run every framework on their own hardware and publish the results. On HttpArena's 64-core machine MoroJS serves 2.4M requests per second, and 37M pipelined.

Requests per second, higher is better64-core machine · 4,096 connections · best of three runs
MoroJS
Elysia (Bun)
Hono (Bun)
h3 (Node)
Fastify
Koa
Express
Hono (Node)
Raw servers, no framework on top
Bun.serve
Deno.serve
node:http
3.3×
vs Fastify, baseline · 2,406,514 vs 737,611 req/s
6.9×
vs Fastify, short-lived connections · 2,005,333 vs 291,264 req/s
8.9×
vs Fastify, JSON with compression · 436,734 vs 49,030 req/s
22×
vs Fastify, pipelined · 37,119,811 vs 1,671,518 req/s
Requests per second, higher is better64 connections · keep-alive · closed loop
MoroJS
Elysia (Bun)
Hono (Deno)
Fastify
Hono (Node)
NestJS (Fastify)
Express
Koa
NestJS (Express)
Raw servers, no framework on top
@morojs/engine
uWebSockets.js
3.8×
vs Fastify · 273,991 vs 72,918 req/s
4.0×
vs Hono on Node · 273,991 vs 67,979 req/s
4.8×
vs NestJS on Fastify · 273,991 vs 57,576 req/s
5.2×
vs Express · 273,991 vs 52,690 req/s

Measured by HttpArena ↗ (2026-11-11) and The Benchmarker ↗ (2026-11-05)

Start

Build it in the next 60 seconds.

One command. A typed, validated, production-ready API. No framework decisions left to make.

$npx @morojs/cli init my-apiRead the docsStar on GitHub

MIT licensed · No telemetry · Open governance