The next wave of React starts here.

Your React components. Your npm ecosystem. A Rust-powered core. Build for the web with familiar tools and a fresh foundation.

Why PRNext?

Up to 7.5× the throughput.

PRNext vs Next.js 16.4.6. A server-rendered table with 1,000 rows.

Show detailsHide details
Same 1,000-row SSR table. Medians from six alternating pairs.
Next.js 16.4.6PRNext
Throughput46.4 req/s349.8 req/s
Latency p95194.05 ms25.10 ms
RAM (working set)395.2 MiB260.3 MiB
Server CPU / response27.43 ms/req3.97 ms/req

Nov 11, 2026 · 8 connections · 1 server worker each · 1 s warmup + 5 s measurement · Node 24.22.1 · shared Windows PC, Ryzen 5 3600, 32 GiB. Local synthetic benchmark; no universal or VPS speed guarantee.

Measured on a development build. RAM: summed observed working sets, not unique physical memory or exact peaks. The ratio is the median of paired runs. Both use their normal production stacks; bundled React renderers differ. Streaming throughput is similar, and PRNext uses more initial browser script CPU on this table.

Benchmark data ↗

How to use PRNext

The latest from PRNext.

All posts

FAQs

What is PRNext?

PRNext is an experimental Rust-powered runtime for Next.js applications. Keep React and npm, with React rendering running on Node.js. The framework is open source under the MIT license.

How do I get started?

Start with an existing Next.js project. The quickstart walks you through installing the packages, migrating your scripts, starting development and checking a production build. Read the quickstart

Will it work with my Next.js project?

Next.js compatibility is still partial. The prnext check command helps identify some incompatibilities, but it does not replace testing your routes, forms and integrations. Check the migration steps

Can I keep React and my npm packages?

Yes. Keep your React components and npm dependencies. The documented PRNext 0.1.22-alpha requires React, React DOM and react-server-dom-webpack 19.3.1. Libraries that depend on unsupported Next.js features still need checking.

Can I use it in production?

The alpha is intended for experimentation and feedback. Before considering a deployment, check your project’s compatibility and test its production build. A working development session alone does not validate your application. Test the production build

Where can I host my site?

PRNext Host is the separate service for deploying supported apps and static sites. Connect Codex, Cursor or Claude Code through MCP to work with your projects and deployments. New access currently uses the waitlist. Explore PRNext Host

Sponsors

Support the development of PRNext.

Become a sponsor (opens in a new tab)

Your name could be here.