What do I need to set up Bolt.new on a VPS?

You need a VPS (starting at $4-6/month), SSH access, and the app code in a GitHub repo. For Bolt.new and VPS, you also need environment variables, a domain, and SSL configured before going live.

How long does it take to move to a VPS?

A straightforward Bolt.new deployment takes 2-4 hours for someone familiar with servers. RepoAssistant does it in 24h with a ship-or-refund guarantee.

How much does it cost to host Bolt.new on a VPS?

A VPS for Bolt.new or VPS starts at $4-6/month for a 1-2 GB instance from providers like Hetzner, DigitalOcean, or Hostinger. RepoAssistant's deploy service is a fixed $39-149 one-time fee.

What if something breaks after deployment?

Every deployment includes a smoke test (login, forms, database writes, API calls) and a handover doc with restart, rollback, and deploy commands. If the app is blocked pre-launch, we fix and ship within 24h or refund.

Env vars rescue

Bolt.new env vars work in preview but break on production

Bolt.new injects environment variables automatically. When you export the code, those variables disappear and the app fails until you recreate them correctly on the server.

Bolt.new Supabase VPS

What is probably broken

The app ran fine in Bolt.new. After export, nothing works because every secret, API key, and callback URL is missing.

What production should look like

A clean environment variable map for the production server with secrets rotated where needed.

STEP 01

Audit every variable the app needs

Search the codebase for `process.env` references and list each one.

Separate public frontend variables from server-only secrets.
Identify which variables must be available at build time vs runtime.
Note which URLs and keys still point to preview or test values.

STEP 02

Set variables on the production server

Load env vars from the deploy panel or server environment, not from files.

Add each variable to your deploy panel environment store.
Update all callback URLs, auth redirects, and webhook endpoints to the production domain.
Rotate any key that was ever visible in Bolt.new preview or a public repo.

STEP 03

Rebuild and verify

After setting env vars, rebuild the app and test every integration.

Run a clean production build with the new environment.
Test database connections, auth flows, payment webhooks, and email.
Confirm no preview URLs remain in the running app.

Quick check

Is your app production-ready?

If you cannot tick all five, we can fix it. Send us the repo and we handle the rest.

?Custom domain with HTTPS
?Environment variables configured
?Database wired and backed up
?Auto-deploy on push
?Smoke tested and live

Free checklist

Deploying this yourself?

Get the exact 5-step checklist we run before every deploy. No fluff, just the things that actually break.

Done-for-you deploy

RepoAssistant cleans up Bolt.new environment variables during production deploy so nothing breaks on launch.

Fixed price per repo. 24h delivery or full refund. No hourly billing.

Deploy my app

Related guides