NextRush
Explicit architecture. Zero hidden behavior.
NextRush is the backend framework for developers who want to reason about every request, not guess what a framework did for them. Start with a small functional core; add segment-trie routing, middleware, and the class runtime only when your application needs them. Benchmarks publish the methodology so you can reproduce results on your own hardware.
Node.js
Bun
Deno
Edge
TypeScriptimport { createApp, createRouter, listen } from 'nextrush';
const app = createApp();
const router = createRouter();
const PORT = Number(process.env.PORT) || 8080;
router.get('/', (ctx) => {
ctx.json({ message: 'Hello NextRush!' });
});
await listen(app, PORT);An explicit stack, not a magic box
Keep the request path understandable and add capabilities only where they solve a real application need.
Segment-trie routing
Route matching scales with URL segments rather than route count, while keeping application code explicit.
Typed request flow
Context, routes, middleware, and errors share TypeScript contracts without loosening to `any`.
Small core, optional modules
Start with the functional core, then add middleware, streaming, or class-based composition when needed.
Web-standard adapters
Write against Request, Response, streams, and AbortSignal; adapters carry runtime-specific details.
Class runtime when it helps
Controllers, modules, request scopes, guards, and lifecycle hooks remain an opt-in path.
Security as composition
Add CORS, headers, CSRF protection, rate limits, and validation as intentional middleware choices.
Install your first app
Choose a package manager, install the core, then follow the introduction.
$ pnpm add nextrushChoose your next step
Learn the model first, then move into architecture or task-focused documentation.
Start with the mental model
See how applications, routers, middleware, and adapters fit together before writing code.
Read introductionExplore the architecture
Trace the request lifecycle, package boundaries, runtime support, and performance methodology.
View framework mapBuild from the docs
Move from concepts to guides, recipes, and API reference when you know what you need.
Browse documentationPackages for each layer
Start with the core, then add only the tools your application needs.