# PRNext

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.

[Deploy with PRNext Host](https://app.prnext.dev)

```sh
npm i @thomas.f/prnext
```

PRNext is an experimental Rust-powered runtime for existing Next.js applications. Keep React and npm, with partial Next.js compatibility. The framework and PRNext Host are separate products.

Use the alpha for experimentation and test your routes, rendering, dependencies and production build before adopting it. Compatibility with Next.js is partial; a benchmark is not a guarantee for another application.

## Why PRNext?

### Up to 7.5× the throughput.

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

Next.js 16.4.6: 46.4 responses/s. PRNext: 349.8 responses/s. The median paired throughput ratio is 7.5 on this 1,000-row SSR table. Dots represent equal batches, not individual response latency.

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](https://prnext.dev/benchmark-data/prnext-next-2026-11-11.json)

| Metric | Next.js 16.4.6 | PRNext |
| --- | --- | --- |
| Throughput (req/s) | 46.4 | 349.79999999999995 |
| Latency p95 (ms) | 194.05 | 25.097 |
| RAM (working set) (MiB) | 395.220703125 | 260.287109375 |
| Server CPU / response (ms/req) | 27.42888621794872 | 3.9663238398013383 |

## Your familiar tools. React, npm and a Rust-powered core.

Keep your components and npm packages. PRNext runs its core in Rust and renders React on Node.js. Start with your existing project and check its compatibility. Next.js support is still partial.

## How to use PRNext

### 1. Install PRNext

Keep your Next.js project. Add PRNext from your terminal.

### 2. Migrate your scripts

Switch your development and build scripts to PRNext, then check your project’s compatibility.

### 3. Develop your application

Start the development server, edit your components and check the result in your browser.

### 4. Build and run

Create the production build and test it locally before putting your site online.

[Read the quickstart](https://prnext.dev/llms/en/blog/getting-started-with-prnext.md)

## The latest from PRNext.

- [PRNext 0.1.22-alpha: Way more performance](https://prnext.dev/llms/en/blog/prnext-0-1-22-automatic-flight-presentation.md)

- [CVE-2026-98432: when waiting for a kernel fix becomes a concern](https://prnext.dev/llms/en/blog/cve-2026-98432-ubuntu-waiting-for-kernel-fix.md): CVE-2026-98432: why the wait matters, Ubuntu fixes in -proposed and the difference between mitigation, an available package and a patched running kernel.

- [CVE-2026-98432: check your Ubuntu VPS and reduce exposure](https://prnext.dev/llms/en/blog/cve-2026-98432-ubuntu-vps-mitigation.md): What we checked on two Ubuntu VPS instances: nftables, MPTCP, containers and service health. Temporary measures while waiting for a Linux kernel fix.

[All posts](https://prnext.dev/llms/en/blog.md)

## 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](https://prnext.dev/llms/en/blog/getting-started-with-prnext.md)

### 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](https://prnext.dev/llms/en/blog/getting-started-with-prnext.md)

### 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](https://prnext.dev/llms/en/blog/getting-started-with-prnext.md)

### 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](https://host.prnext.dev/)

## Sources

[GitHub](https://github.com/Lorkydey/PRNext)

[npm](https://www.npmjs.com/package/@thomas.f/prnext)

[Blog](https://prnext.dev/llms/en/blog.md)

---

Language: en

Canonical: https://prnext.dev/

Index: https://prnext.dev/llms.txt