When to use vite-ssr-boost and when not to

Use vite-ssr-boost to add SSR to a Vite app while keeping React Router Data-mode route objects. Start with the managed CLI, or own the transport through runtime adapters.

The table describes configuration and migration steps, not measured effort or performance. The Next.js column covers the App Router; the Vike column covers React integration. Each cell about another project links to its official documentation.

Topic	vite-ssr-boost	React Router Framework mode	Next.js	Vike	TanStack Start
Routing model	Data-mode route objects	Route modules and routes.ts	App Router; file-system routing	Filesystem, route strings or route functions	TanStack Router; file-system routing
Migration effort from an existing React Router SPA	Add plugin, HTML outlet, entries and scripts	Convert routes to modules; add plugin, config and root entry	Migrate Vite setup to Next.js; retain React Router for SPA, move to App Router for streaming	Retain React Router during migration; migrate routing afterward	Convert routes, links and hooks to TanStack Router; add Start routing setup
Data loading	Route loaders; see contract below	loader and clientLoader	Fetch in Server Components; pass props to Client Components	+data and useData()	createServerFn from loaders or components
Streaming SSR	React streams and Suspense	Suspense with loader promises	Server Components and streaming	HTML streaming via vike-react	Document SSR and streaming
SPA output from the same code	--focus-only client	ssr: false	output: 'export'; excludes server features	ssr: false via vike-react	spa: { enabled: true }
RSC	No implementation	Opt in with unstable_reactRouterRSC	Pages and layouts use Server Components by default	Via vike-react-rsc	Opt in with rsc.enabled
Server ownership	CLI or transport supplied by the application	Node server template or Express integration	next start or server supplied by the application	+server: true, +server.js or renderPage()	Hosting integration or server forwarding to the Fetch entry
Hosting targets	Node/Express CLI; Fetch runtimes via adapters; SPA files	Node/Docker, Vercel, Cloudflare Workers, Netlify	Node, Docker, export files or platform adapters	Node, Bun, Deno; Cloudflare, Netlify, Vercel	Node/Docker, Bun, Cloudflare Workers, Netlify, Vercel

The RSC implementations linked above have different release contracts: React Router labels its support experimental, as do Vike and TanStack Start. Consult those pages before selecting an RSC integration.

Loader data in vite-ssr-boost

Loader and action promises stream by default in Data mode. Use Suspense with <Await> or React 19 use() for slow fields, and opt into hydration: 'early' when the shell should become interactive before slow boundaries finish. See Stream loader data for the value matrix and custom-state constraint.

Choose a project

• Choose vite-ssr-boost when you already have a Vite app with React Router route objects and want to keep that structure while adding SSR. The migration guide shows the entry changes; choose the Fetch path when you also want to own transport and asset delivery.
• Choose React Router Framework mode when you want its route module API, generated route types and rendering configuration. Its mode guide describes that integration, and its adoption guide explains the route conversion it requires.
• Choose Next.js when you want the App Router's file-system routing, Server Components and Server Functions. Those are part of its documented App Router model, while vite-ssr-boost does not implement them.
• Choose Vike when you want its page configuration and routing with a choice of server integration. Its routing guide documents filesystem routes, route strings and route functions, and its server guide documents the integration points.
• Choose TanStack Start when you want TanStack Router with document SSR, streaming and server functions. The Start overview describes that combination; use its routing guide to assess the route structure you would adopt.