Remix on Railway — the Remix-lineage full-stack starter

One click provisions a production-shaped full-stack app: a React Router v7 (framework mode, SSR) server, a PostgreSQL database, Prisma with migrations applied automatically on boot, and an email/password auth skeleton (bcrypt + cookie sessions). No form fields, no manual wiring — the deploy button gives you a running, DB-connected app behind a public URL.

This is the successor template to the Remix Indie Stack (archived), ported to the officially supported React Router v7 path and to Postgres. The app itself is a working notes app — register, create notes, log out, log back in — that doubles as a reference for your own domain model.

Deploy and Host

Click the deploy button. Railway provisions exactly two services:

Service	What it is
app	Built from the GitHub repo's Dockerfile (Node 22 LTS, multi-stage, `npm ci`). Boots with `prisma migrate deploy` (idempotent) then serves on Railway's injected `PORT`. Healthcheck: `GET /healthcheck.jpg` → 200.
Postgres	Railway's Postgres 18 image with a persistent volume.

Wiring is preconfigured: DATABASE_URL on the app references ${{Postgres.DATABASE_URL}}, and SESSION_SECRET is generated fresh per deployment via ${{secret(32, ...)}}. Nothing to type.

About Hosting

Hosting costs roughly $5/month at idle-to-light usage: the Postgres service (~~$3–4/mo for the smallest volume + memory) plus the app container (~~$1–3/mo). Both scale with usage; you can sleep the app when developing locally.

Why Deploy

Migrations just work: every boot runs prisma migrate deploy before the server starts — first deploy creates all tables; later deploys apply new migrations. No manual DB steps.
Actually verified: the repo ships a Cypress smoke flow (register → create note → logout → login → data persisted) that is the same script used to verify the template itself.
Current stack: React Router v7 framework mode (the official successor to Remix v2), Prisma 6, Tailwind 4, Node 22 LTS pinned in the Dockerfile.
Not an image dump: the app service is sourced from the public GitHub repo, so you can fork it, connect your own fork, and let Railway rebuild on every push.

Common Use Cases

Starting a SaaS or dashboard app where you want auth + database from minute zero.
Learning the Remix-lineage stack (loaders, actions, cookie sessions, Prisma) on a real deployment instead of localhost.
Prototyping with a team: everyone deploys their own copy in one click and iterates on the same schema.

Dependencies for

Deployment Dependencies

A Railway account (the button handles the rest).
None of the deploy-form fields need input — all variables are preconfigured or generated.
After deploy: open the public URL, sign up, and start writing notes. To make it yours, fork the repo, change prisma/schema.prisma, commit a migration with npx prisma migrate dev, and push — the next deploy applies it automatically.