How to deploy a Lovable or Bolt app to Vercel or Railway
Checked against official pricing pages and docs on Oct 16, 2026. Plans change, so confirm on each official site.
Lovable and Bolt both host your app for you. Move it to your own host when you want a custom setup, a bill you control, or room to grow beyond the builder. The path is the same for both: get the code into GitHub, then import that repo into Vercel or Railway.
Disclosure: Railway links on this page are affiliate links: if you sign up, we may earn a commission at no cost to you. It never affects scores or rankings.
Step 1: get the code into GitHub
Lovable: connect your workspace to GitHub and link the project to a repository (Lovable docs: “Sync your Lovable project with GitHub”). The sync is two-way, so you can keep editing in Lovable after you deploy elsewhere. GitLab and Bitbucket are also supported. Bolt: connect GitHub from the project (Bolt Help Center: “GitHub for version control”), or download the code and push it yourself.
Step 2a: deploy on Vercel
In Vercel, import the GitHub repository. Vercel detects common frameworks (Vite, Next.js) and sets the build command. Add your environment variables (for example your Supabase URL and anon key), then deploy. Every push to the repo triggers a new deploy. Cost: Vercel Hobby is $0, but it’s for personal, non-commercial projects. Pro is $20/mo per seat and includes $20 of usage credit.
Step 2b: deploy on Railway
In Railway, create a new project and choose Deploy from GitHub repo. Railway builds and runs the app and redeploys on every push (GitHub autodeploys). Railway also runs long-lived servers, workers and databases such as Postgres next to the app, which helps if your app grew a real backend. Cost: the Free plan starts with a 30-day trial with $5 of credit, then $1/mo, with up to 0.5 GB RAM per service. Hobby is a $5 minimum and includes $5 of monthly usage.
Step 3: don’t forget the backend
Moving the frontend doesn’t move the database. If a Lovable app uses Lovable Cloud, the backend stays on Lovable and keeps drawing Lovable credits, and it pauses if the workspace runs out. If the app uses Supabase, add the same Supabase keys as environment variables on the new host. Then update the auth redirect URLs to your new domain in your auth provider.
Vercel or Railway?
Choose Vercel for a static or Next.js frontend with serverless functions and the best preview-deploy workflow. Choose Railway if you need a long-running server, background jobs, or a database next to the app. Both connect custom domains.