Current as of v1.8.24 · November 2026

Roadmap

MoroJS is production-ready and shipping every few weeks. Here's everything that's already in your hands, plus a draft of where it could go next. The proposed items are just that, so open a discussion and help set the order.

Status

ShippedProposedExploring

Core & Developer Experience

Shipped

The foundation: intelligent routing, end-to-end types, and an API that stays out of your way.

Intelligent routing with automatic 10-phase middleware ordering
End-to-end TypeScript inference, schema to response
Zero-config defaults
Route groups and file-based auto-loading
Express-compatible API and standalone router
CLI: scaffold projects, generate modules, deploy

Validation, Auth & Security

Shipped

Validation, authentication, and the security defaults that ship turned on.

Universal validation: Zod, Joi, Yup, Class Validator
Better Auth: OAuth providers, RBAC, JWT, sessions
Security defaults: helmet, CORS, rate limiting, body-size
Hardening: JWT algorithm pinning, path-traversal fixes
TLS rotation on the running listener: app.reloadTLS() and server.ssl.watch
Bundled BoringSSL on the native engine, OpenSSL selectable: server.ssl.library
Auto-generated OpenAPI / Swagger from Zod schemas
Structured error handling and validation errors

Real-time & Protocols

Shipped

More than HTTP. Sockets, streams, and RPC from the same app instance.

WebSockets on the native engine, Socket.IO and ws adapters, raw frames for plain peers
Server-Sent Events
GraphQL with subscriptions and DataLoader
gRPC with streaming and interceptors
HTTP/2 served by the native engine: multiplexing, header compression, HTTP/1.1 on the same port

Data & Background Jobs

Shipped

Talk to your data and run background work without bolting on extra services.

Database adapters: Postgres, MySQL, MongoDB, SQLite, Redis, Drizzle
Job scheduler: cron, intervals, leader election, health checks
Mail adapters: SES, SendGrid, Resend, Nodemailer
Worker-thread facade for CPU-bound work
Versioned module system, auto-mounted at /api/v{version}

Performance & Runtimes

Shipped

Fast by default, and the same code runs wherever you deploy it.

Native engine (@morojs/engine), the default transport
Engine-answered routes: literal bodies and param() echoes never enter JS
Built-in clustering, worker count aware of container CPU and memory limits
One codebase on Node, Vercel Edge, AWS Lambda, Cloudflare Workers
Lifecycle hooks and decorators (app.decorate, onClose)
OpenTelemetry traces and metrics: middleware.openTelemetry()
Static file serving with an in-memory cache, and a built-in template engine

Next Up

Proposed

Proposed directions, not commitments. Tell us which of these you would want first.

First-party testing utilities
More database and mail adapters
Edge and serverless cold-start tuning

Exploring

Exploring

Early ideas, nothing scheduled. Open a discussion to push one forward.

Module registry and marketplace
VS Code extension
Visual route and module explorer
Distributed caching and pub/sub
Community

Shape What's Next

The shipped list is real and growing. The proposed items are open for debate. If there is something you need, ask for it, or send a pull request and build it.

Feature Requests

Suggest new features or improvements

Contributions

Help build the features you want to see

Community

Connect with other developers