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.

Bolt migration guide

Move your Bolt.new app from preview to a production VPS

Bolt.new can get you to a prototype fast. Real production means a repo you control, a repeatable build, a server process, and a domain that does not depend on the builder.

Published April 4, 2026·by RepoAssistant Team

Bolt.new Domain VPS

What is probably broken in your Bolt.new app

The app works in Bolt.new preview, but the exported code still depends on builder-specific settings, hidden env vars, or platform hosting you do not own.

What production should look like for Bolt.new

The same Bolt.new app running on your own VPS with HTTPS, a stable deploy path, and fewer monthly subscriptions to juggle.

STEP 01

Capture what Bolt.new generated

Do not start with the server. Start by documenting the exact app shape Bolt.new produced.

Export the project to a GitHub repo or local codebase you own.
Write down the build command, start command, and Node version in the preview environment.
List every external service the app depends on before deploy day.

STEP 02

Rebuild the environment on a real host

Production fails when you miss the env vars or proxy settings Bolt.new was providing behind the scenes.

Add env vars to the server or deploy panel, not the repository.
Update callback URLs, auth redirects, and webhook endpoints for the final domain.
Make sure the app runs as a managed process that restarts on failure.

STEP 03

Deploy, test, and cut monthly spend

Once the app is on your VPS, the value comes from ownership, repeatability, and lower recurring cost.

Smoke test login, forms, API routes, and database writes on the live domain.
Keep backups and a rollback path before sending users over.
Compare the VPS bill against the builder stack so you can see the savings clearly.

Quick check

Is your Bolt.new 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 your Bolt.new 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 moves Bolt.new apps to a VPS you own so production is cheaper, simpler, and actually under your control.

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

Deploy my app

Related guides