Skip to main content

Official documentation for one product with two tiers

React on Rails keeps Rails conventions and adds modern React.

Start with one recommended path, then branch into SSR, streaming, RSC, migration, or Pro only when you need them.

Start with the docsReview examplesUnderstand Pro

Recommended first run

  1. npx create-react-on-rails-app@latest my-app
  2. bin/rails db:prepare
  3. bin/dev

If you are not starting fresh, the docs route you into existing-app install, migration, or Pro upgrade paths instead.

Choose your path

Docs should start from your situation, not from our internal file layout.

Persona A

Starting a new Rails + React app

Use the CLI-backed happy path, get to a working app quickly, and customize from a clean baseline.

Create a new app

Persona B

Adding React to an existing Rails app

Keep the Rails app you already have, install React on Rails, and render components without rebuilding the stack.

Install into an existing app

Persona C

Already on OSS and need more performance

See what Pro adds, how the upgrade works, and where higher-throughput SSR or RSC support fits.

Compare OSS and Pro

Persona D

Evaluating Rails + React options

Compare React on Rails with Hotwire/Turbo, Inertia Rails, and react-rails before you dive into migration details.

Compare the options

Recommended flow

Keep the first-run path obvious. Put alternatives behind it, not in front of it.

Recommended for new projects

Start with one working path before you branch into deeper configuration.

npx create-react-on-rails-app@latest my-appFollow the new-app guide

For mature Rails apps

Install React on Rails into an existing codebase, keep your routes, and add components incrementally.

bundle exec rails generate react_on_rails:install --typescriptUse the install guide

When OSS is no longer enough

Pro is an upgrade tier, not a separate product. Add it when you need more SSR throughput or guided support.

bundle add react_on_rails_proReview the upgrade path

Migration and evaluation

Modern docs need concrete migration routes, not generic reassurance.

Compare Rails + React approaches

Use the new evaluator guide first, then branch into concrete migration docs if React on Rails is the right fit.

Open guide

Migrate from react-rails

Swap from `react-rails` to React on Rails with a migration checklist grounded in a real sample app.

Open guide

Migrate from vite_rails

Keep Vite-era lessons that still matter, then move to the supported React on Rails integration model.

Open guide

Browse sample apps

Open repositories that back the migration and evaluation docs with concrete examples.

Open guide

Production feedback

React on Rails Pro is an upgrade tier for teams that need more, not a separate ecosystem.

Our blog and product pages were 80-90% faster after moving to React on Rails Pro.

Paul BenigeriHead of E-Commerce, HVMN

The team helped us set strong design foundations and move to server rendering with much faster page performance.

Leora JusterFull-Stack Lead Software Developer, ResortPass