Move Your Bolt App to Your Own Hosting

Review the Project for External Deployment

Ask Bolt to identify what the project needs outside Bolt before moving it.

External Deployment Review

Identifies the framework, build settings, backend, environment variables, and external services, then returns a short deployment checklist.

Review this project specifically for deployment outside Bolt. Identify: - the framework and project type - the production build command and output directory - whether the project uses Bolt Database, Supabase, or another backend - every environment variable required in production — names only - authentication or redirect URLs that may need the new production domain - external services such as APIs, Stripe, storage, email, or webhooks Do not change or migrate anything yet. Give me a short deployment checklist containing only what I need to configure after moving the app to another host.

Open Bolt

Keep the result for the next steps.

Connect the Project to GitHub

Open the project in Bolt and click the GitHub icon.

Connect your GitHub account Create a repository for the project

The project is available in GitHub

Bolt keeps your code in GitHub so it can be deployed outside Bolt and updated later.

Get Hostinger Web App Hosting

This workflow uses Hostinger to host the production version of your Bolt app.

Get Hostinger Web App Hosting

Deploy your Bolt project from GitHub and keep future updates connected.

USED IN THIS TUTORIAL

https://www.hostg.xyz/SHJyP

Already have Hostinger hosting? Continue below.

Create the Web App and Deploy

Then in Hostinger:

Create a new Web App Choose GitHub as the source Connect your GitHub account Select the Bolt repository Review the detected build settings Add any required production environment variables Deploy the app

Start with the temporary URL before connecting your real domain.

Hostinger supports GitHub deployment for Bolt projects and can automatically detect supported frameworks and build settings.

Test the Temporary URL

Open the temporary URL and test the important parts of the app.

Main pages and routes

Login and authentication

Database-connected features

Forms and uploads

External APIs

Images and assets

NOTE

If something worked inside Bolt but fails on Hostinger, check the production environment variables and backend configuration first.

Connect Your Production Domain

Connect your production domain to the Hostinger deployment, then verify it.

The domain works

HTTPS is active

Authentication still works

Database features still work

Production services are connected

Redirect URLs use the new domain where required

IMPORTANT

If the project uses Bolt Database or Supabase authentication, check its Site URL / allowed redirect URLs after moving to the production domain. Bolt documents that these URLs matter for authentication and password-reset flows.

Keep building normally in Bolt. Your workflow becomes Bolt → GitHub → Hostinger.

Push or sync the updated project to the deployed GitHub branch and Hostinger can redeploy the latest version automatically.