Guides / Comparisons
Railway vs Vercel for launching a new product
Where the app runs. Shipyard can set up either Railway or Vercel for you. This is how they differ when the goal is to get a new product live quickly.
The short answer
- Railway runs the web service, background workers and Postgres in one project, so there is one place for logs and one bill.
- Vercel has no database of its own and no background workers, so a launch on Vercel always pairs it with Supabase.
- Pick Railway if the product needs a worker or you want the database next to the app. Pick Vercel if you already deploy there and the product is mostly pages and API routes.
Railway
Web service, worker and Postgres in one project.
- Token: Account token, or a token for one workspace
- Set up first: Add a payment method and choose the Hobby plan ($5 a month). A trial account cannot attach a custom domain.
- Set up first: Install the Railway GitHub app on the account that owns your repos, with access to all repositories, so Railway can deploy from them.
- Stays manual: Creating the Railway account and adding a payment method (Hobby plan, $5 a month).
Vercel
Needs a separate database. No background workers.
- Token: A token scoped to one team, or to your personal account
- Set up first: Install the Vercel GitHub app on the account that owns your repos, with access to all repositories, so Vercel can deploy from them.
- Set up first: A product that takes money needs the Pro plan. The free Hobby plan is for non-commercial projects only.
- Stays manual: Creating the Vercel account. A commercial product needs the Pro plan; the free Hobby plan is for non-commercial projects.
Have this set up for you
Shipyard connects your accounts once and then does all of this for every new product, in about an hour.
See how it works