Documentation

Juice Docs

Build React 19 Server Components on standard web APIs. One fetch handler, explicit runtime behavior, and deployment targets that stay close to the platform.

Get started API reference

Quickstart

npx @cmj/juice create my-app
cd my-app
bun run dev

Create your first app

Runtime dependencies

43ms

Cold start p50

33.5K

Requests per sec

25KB

Gzipped runtime

Primitives

Small pieces that map to the web platform.

Juice keeps the framework boundary narrow: React owns rendering, HTTP owns requests and responses, and the compiler emits an inspectable manifest that the runtime can read anywhere.

File-based routing

Layouts, pages, API routes, middleware, and dynamic params are discovered from the filesystem.

Server actions

React 19 form actions with parsed bodies, request context, cookies, route params, and CSRF protection.

Streaming SSR

Choose buffered, shell, or full-stream rendering based on correctness and TTFB tradeoffs.

Any runtime

Deploy one fetch handler to Cloudflare Workers, Bun, Deno, or Node.js.

Start here

Find the right path.

Get started

Scaffold an app, run the dev server, and add your first route.

Learn concepts

Understand the manifest, server rendering, client hydration, and navigation model.

Migrate

Map common Next.js and Remix patterns to standard Request and Response APIs.

Integrate

Add data, auth, payments, email, validation, file storage, and styling.

Compare

Coming from Next.js?

Juice gives you React server primitives without a proprietary request object or Node-first runtime assumption.

Concept	Next.js	Juice
Route handler	Proprietary `NextRequest`	Standard `Request`/`Response`
Middleware	Single file, edge only	Per-directory, onion model, everywhere
Data fetching	Magic `fetch` caching	Explicit `cache(fn)` dedup
Runtime	Node.js with edge opt-in	WinterCG-first: Workers, Bun, Deno, Node
Server bundle	~2MB+ runtime	25KB gzipped
Streaming	Always on, limited control	Three modes - you choose
AI tooling	None built-in	`llms.txt` + MCP server

Adoption notes

Choose with context.

Ecosystem is growing

Guides cover auth, Stripe, Prisma, Drizzle, Redis, Resend, and more. There is no plugin marketplace.

Partial rendering is not yet implemented

SPA navigations replace the full React tree. Layout preservation is on the roadmap.

HTTP knowledge helps

Your team should be comfortable with Request, Response, headers, status codes, and deployment runtime tradeoffs.