Bolt domain guide

Connect your own domain to a Bolt.new app

Bolt.new preview runs on its own infrastructure. Moving to a custom domain requires exporting the code, deploying to a server, and configuring DNS and HTTPS.

What is probably broken

The app works in Bolt.new but you cannot point your own domain to it with proper HTTPS.

What production should look like

The Bolt.new app serving from your custom domain with valid HTTPS and a stable deploy path.

STEP 01

Export and deploy the app

Get the code out of Bolt.new and onto a server that you control.

  • Export the Bolt.new project to a GitHub repo.
  • Deploy the app on a VPS or Vercel project.
  • Confirm the app builds and runs on the server.

STEP 02

Configure DNS and HTTPS

Point your domain to the server and enable SSL.

  • Add an A record from your domain to the server IP.
  • Wait for DNS propagation.
  • Request and install an SSL certificate on the server.

STEP 03

Test and switch traffic

Verify everything works on the new domain before sending users.

  • Test all auth flows, database calls, and API routes on the new domain.
  • Update any hardcoded URLs in the app to use the new domain.
  • Monitor logs for errors during the first 24 hours.

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.

No spam. Your email is only used to send the checklist.

Done-for-you deploy

RepoAssistant handles Bolt.new to custom domain migration with HTTPS and production config.

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

Deploy my app

Related guides