RepoAssistant logoRepoAssistant
← All guides

Bolt migration guide

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

Bolt.newVPSDomain

Short answer

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

Why this matters

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.

Walkthrough

  1. 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.
  2. 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.
  3. 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.

Where RepoAssistant fits

RepoAssistant moves Bolt.new apps to a VPS you own so production is cheaper, simpler, and actually under your control.