Skip to main content
Hostwares

Can you host a Bolt app outside Bolt Cloud?

Yes. Bolt Cloud is Bolt's built-in hosting with a bolt.host address, but the project exports as source code or pushes to GitHub, and from there it runs on any host. What does not come with the code: secrets from Bolt's settings, and any database Bolt provisioned through an integration, which stays where it is until you move it. On your own hosting you set the environment variables yourself, add a managed Postgres or a dedicated Supabase if the app needs one, and attach the domain on the host's Domains tab; on Bolt Cloud a custom domain needs a paid plan.

Step by step

  1. 1

    Push the project to GitHub

    Use Bolt's GitHub integration, or download the project and push it from your computer. Check the repository has package.json and src/. Bolt Cloud keeps serving the bolt.host address in the meantime, so nothing goes down.

    From a downloaded project

    git init && git add . && git commit -m "bolt export"
    git remote add origin https://github.com/<you>/<repo>.git && git push -u origin main
  2. 2

    Decide what the database will be

    If the app used Supabase through Bolt's integration, the project is yours in Supabase Cloud already: keep it, or move it to a dedicated Supabase at Dashboard → Supabase → New with a dump and restore. If the app used a Bolt-provisioned database with no export, add a managed Postgres from Hostwares (create_database over MCP) and run the app's migrations against it. A frontend-only app skips this step.

  3. 3

    Deploy the repository

    Dashboard → Deployments → New: repository, branch, pack. Vite, Next.js, Astro and Node servers are detected and the commands are filled in; a Dockerfile is used as-is. The order creates an invoice and the build starts once it is paid. From Claude Code or Cursor: "Deploy this repo to Hostwares as my-app".

  4. 4

    Re-enter the secrets and keys

    Bolt's secrets are not in the repository. Add each on the Environment tab (set_env over MCP) with the right prefix: VITE_ for a Vite app's browser-visible values, NEXT_PUBLIC_ for Next.js. Server-only keys go in without a prefix.

    Variables are read at build time, so the site rebuilds after you change them; the current version keeps serving until the new build is ready.

  5. 5

    Attach the domain and verify

    Domains tab, enter the domain, create the record it shows at your registrar; the certificate is issued once DNS resolves (verify_ssl). Then open a deep link and an API route; http_check and diagnose_site over MCP do both and read the logs if something fails. Unpublish on Bolt Cloud once the new host answers.

What breaks, and the fix

process.env or import.meta.env values are empty
Bolt's secrets are not exported. Add them on the Environment tab with the right prefix.
The app cannot reach its database
The connection string pointed at a Bolt-provisioned service. Create a managed Postgres or a dedicated Supabase and set the new string.
Supabase sign-in redirects to bolt.host
Add the new domain to Site URL and Redirect URLs in the Supabase project's Auth settings.

What it costs

  • A Frontend pack from $1/mo; $5/mo for the pack most production apps pick (1 vCPU / 4 GB / 25 GB).
  • A managed Postgres from $10/mo or a dedicated Supabase pack from $5/mo if the app has a database.
  • A domain from $11.39/yr if you register it with us. Flat for the term; nothing metered.

App

$1/mo

Starter Frontend pack, 1 vCPU / 1 GB RAM / 10 GB

Database, users and files

$5/mo

Smallest dedicated Supabase pack; several projects fit on one

For comparison

  • Bolt Pro (custom domains on Bolt Cloud need a paid plan): $20/mo (checked 2026-11-06, bolt.new)

Questions

Does Bolt lock the code in?+

No. Bolt's docs describe exporting the project as source code or pushing it to GitHub, and the result is a normal Vite or Next.js project.

Can I keep a custom domain on Bolt Cloud instead?+

Yes, on a paid Bolt plan, under Domains & Hosting in the project settings. The free plan gives a bolt.host address only.

What happens to my database?+

A Supabase project connected through Bolt's integration is yours and keeps running; point the exported app at it or move it. A database Bolt provisioned itself needs a replacement on the new host and the migrations run again.

Can I keep editing in Bolt after moving?+

Yes. Keep the GitHub sync on and each push redeploys. Or edit the repository in Cursor or Claude Code and deploy from there over MCP.

Does a Node backend from Bolt deploy?+

Yes. Packs run the start command, so an Express or Hono server deploys the same way as a static build; set_app_port fixes a custom port.

What does it cost?+

A Frontend pack from $1/mo, plus a managed Postgres from $10/mo or a dedicated Supabase from $5/mo if the app has data. Flat for the term.