Deploying to Railway
Deploy your RivetKit app to Railway.
Steps
Prerequisites
- Railway account
- Your RivetKit app
- If you don’t have one, see the Quickstart page or our Examples
- Access to the Rivet Cloud or a self-hosted Rivet Engine
Deploy to Railway
- Connect your GitHub account to Railway
- Select your repository containing your RivetKit app
- Railway will automatically detect and deploy your app
See Railway’s deployment docs for more details.
Set Environment Variables
After creating your project on the Rivet dashboard, select Railway as your provider. You’ll be provided RIVET_ENDPOINT and RIVET_PUBLIC_ENDPOINT environment variables to add to your Railway service.
See Railway’s environment variables docs for more details.
Connect to Rivet
There is nothing to register in the dashboard. As a Runner, your app opens a connection out to Rivet on startup, so it does not need a public domain or a URL pasted into a connect form.
Once your Railway service is running, open the Rivet dashboard and confirm your app appears under Runners. It reconnects automatically if the connection drops.
Configure Multi-Region (Optional)
Configure Multi-Region to deploy closer to your users.
Do not enable App Sleeping for a Runner. Sleeping suspends the process, which drops its connection to Rivet, and Railway only wakes on inbound HTTP. Runner traffic is outbound, so the service would never wake and actors could not be scheduled to it.