RepoAssistant logoRepoAssistant

Deploy from Bolt.new

Deploy a Bolt.new app to your own server.

Bolt.new can generate an app in minutes. Getting that app running in production takes a real release pipeline. We take your Bolt project to a server you own, with Git-based deploys and a clear way back if a release goes wrong.

See pricing

What changes

Before

  • A sandbox or snapshot
  • No release history
  • Demo data and undeclared dependencies
  • Unknown steps to production

After

  • Production server you own
  • Git push, deploy, health check
  • Secrets, database, and backups set
  • Rollback and handover documentation

Where it stalls

Why Bolt.new apps get stuck before production.

01

Exports are snapshots

A Bolt export captures code, not the conversation, history, or full configuration. A repository your team owns becomes the source of truth and the deployment trigger.

02

Invisible dependencies

SDKs, environment variables, rate limits, storage, and generated files may be referenced but never defined. We map every one before touching a server.

03

Demo defaults leak into prod

Bolt demos run on defaults. Real production needs real secrets, a real database, and an access model that is not anyone-with-the-URL.

The move, step by step

From Bolt.new project to production server.

  1. Step 01

    Move the app into an owned repo

    Push the project to GitHub, either via the project sync or a clean commit. The repository is what ships, not the sandbox.

  2. Step 02

    Reproduce the stack

    Record dependencies, environment variables, storage, and auth. Verify the app builds and runs locally with a clean checkout before provisioning anything.

  3. Step 03

    Choose and provision the target

    Pick the smallest credible target between a VPS and a managed container service, and stand up the database, backups, and secrets.

  4. Step 04

    Wire the pipeline

    Lint, build, deploy, smoke test, and rollback hooked to pushes on the production branch.

  5. Step 05

    Point the domain and hand over

    Switch DNS, verify HTTPS and health checks, then hand over access with a written runbook for the team's next release.

Pricing

One fixed price to get Bolt.new into production.

Starter

$99

Deploy your repo to production. HTTPS, env vars, server process, smoke test, handover notes.

Fix & Deploy

$149

Fix a blocked build, env, Nginx, or database issue and ship the app to production in 24h.

Full Setup

$249

Full VPS setup with app deploy, database, Docker or Nginx, backups, logs, smoke test, and handover.

Hosting adds $10/month on a managed server. Cancel anytime.

What each plan includes

Bolt.new deployment questions

Can I keep using Bolt.new after moving?

Yes. Keep the GitHub project sync so your owned repository stays current while you keep prompting and iterating in Bolt.

Do I need Docker?

Not necessarily. We pick the least complex target that fits the workload, whether that is a plain VPS process or a containerized deploy.

How fast can it be live?

On the Fix & Deploy plan we ship a working production deployment within 24 hours or refund.

Bolt.new

Read the full guide: Deploy a Bolt app with a real release pipeline

Take a Bolt-built application from exported files or GitHub into a production setup with source control, secrets, testing, and a rollback path.

Read the guide

Free tools

Check the numbers before you buy a server.