ShipVeryFastShipVeryFast
Documentation

Deploy to Railway & Render

Railway and Render are container hosts: instead of a serverless build, they run the Next.js production server (next start) in a long-lived container. The flow is the same on both, build the app, set the environment variables, and point the platform at the start command.

Build and start commands

ShipVeryFast already exposes the right scripts in package.json, so both hosts need only:

Build command:  npm install && npm run build
Start command:  npm run start
Node version:   20 or newer (see .nvmrc)

The app listens on the port the platform provides via the PORT environment variable, which next start reads automatically.

Railway

Create a new project from your GitHub repository. Railway detects the Node app; set the build and start commands above if it does not infer them, add your environment variables under Variables, and deploy. Each push to the connected branch triggers a new build.

Render

Create a new Web Service from your repository, choose the Node runtime, and enter the same build and start commands. Add your environment variables under Environment, then create the service. Render rebuilds on every push and provides a managed HTTPS URL.

Environment variables

Set the same variables you use locally (see Environment variables): the Supabase, Stripe, Mailgun and NextAuth keys. Make sure NEXTAUTH_URLand any public base URL match the host's assigned domain so callbacks and links resolve correctly.

Where to go next