# How to host a website made with Bolt

By Avatar 8 (Avatar 8 LLC) · Published November 21, 2026 · https://deed.page/blog/host-a-website-made-with-bolt

To host a website made with Bolt means putting the app you built in Bolt on a server so anyone can open it at a normal HTTPS address. Bolt's Publish button does that for free at a `bolt.host` address; to host it elsewhere you build the project into a `dist` folder and upload it, and deed.page's Free plan holds 25 sites of up to 25 MB each with no account ([pricing](https://deed.page/pricing)).

This guide covers when Bolt's built-in hosting is enough, which Bolt projects a static host can serve, and how to publish one with `curl` or through MCP. Every deed.page command here was run against production on November 21, 2026, and the test sites were then deleted.

## How do I host a website made with Bolt?

The short answer: click Publish in Bolt, or download the project, run `npm run build`, and upload the `dist/` folder to a static host with a fallback to `index.html`.

Bolt's help center, checked November 21, 2026, says Free and Pro users can publish to a `.bolt.host` domain, custom domains are for paid plans, and Free sites show a "Made in Bolt" badge ([Bolt: Host your project](https://support.bolt.new/bolt-cloud/hosting)). Its [FAQ](https://support.bolt.new/reference/faq) lists free hosting as up to 10 GB of bandwidth and 333,333 requests a month, with no way to raise them; past that, the site goes offline for the rest of the month. If those terms suit you, stay on Bolt. Host it yourself when you want a different address, your own release process, or an agent that keeps updating the page.

## Check which kind of Bolt project you have

Bolt hosting runs React, Vue, Svelte and other single-page apps, plus Next.js apps that render pages on a server. For TanStack Start, SvelteKit, Remix or Astro, Bolt's own guide says to ask Bolt to build static HTML files before publishing ([Bolt: Host your project](https://support.bolt.new/bolt-cloud/hosting)). For a static host:

- **Vite apps** (React, Vue, Svelte) build to plain files in `dist/`. Open `package.json`: if the `build` script runs `vite build`, deed.page fits.
- **Apps with server rendering, API routes, or server-side secrets** need a host that runs a server. A static host only serves the files.
- **A Bolt database or sign-in** keeps working only if the browser calls it directly with a public URL and key baked in at build time. Server-side code does not move with the files.

To get the code, open the project, click the project title in the top left, then **Download** ([Bolt: Manage your projects](https://support.bolt.new/managing-projects/projects-files)). It arrives as a zip; Bolt says download works on desktop, not mobile.

## Build it and publish it with one curl

Unzip the project, then build and upload:

```bash
npm install && npm run build
tar -C dist -czf site.tar.gz . && curl -T site.tar.gz "https://deed.page/v1/sites?slug=pottery-studio-bolt-w5n2&spa=1&ref=blog"
```

Our test was a React + TypeScript Vite app built with `vite build`. The `dist` folder had 8 files (HTML, CSS, JavaScript, images), and the tarball was 90 KB. The reply had `"url": "https://pottery-studio-bolt-w5n2.deed.page/"`, `"version": "v1"`, `"files": 8`, `"expires_at": null`, and a `deed_tok_…` owner token shown once. Keep that token; it is the only credential. Pick your own suffix, since that slug is only an example. A stranger sending the same request got `409 slug_taken` with the suggestion `pottery-studio-bolt-w5n2-2` ([choosing a slug](https://deed.page/blog/choosing-a-slug)).

`spa=1` sends unknown paths to `index.html`, so a deep link such as `/classes/wheel-throwing` returned the app with status 200 while `/assets/index-….css` still served as `text/css` and the script as `text/javascript` ([SPA mode](https://deed.page/blog/spa-mode-client-routes)). Send `spa=1` on every publish.

To ship a new build, send it with the token:

```bash
curl -T site.tar.gz -H "Authorization: Bearer $DEEDPAGE_TOKEN" \
  "https://deed.page/v1/sites?slug=pottery-studio-bolt-w5n2&spa=1&ref=blog"
```

An identical tarball returned `"unchanged": true` and no new version; a changed build returned `"version": "v2"` at the same URL. Bigger builds go up in parts ([large sites](https://deed.page/blog/plan-upload-large-sites)).

## Publish through MCP instead

If an agent such as Claude or Cursor holds the built files, it can publish through deed.page's MCP server at `https://deed.page/mcp` ([docs](https://deed.page/docs)). The call looks like this:

```json
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"publish_site","arguments":{"slug":"pottery-studio-bolt-mcp-h8c4","spa":true,"files":{"index.html":"<!doctype html><title>Pottery studio</title><h1>Pottery studio, built in Bolt</h1>"}}}}
```

It returned `ok: true`, `version: "v1"`, the subdomain URL, and a token, and a client route like `/glaze/celadon` served the page. `update_site` with that token gave `v2` at the same address; without the token it refused with `unauthorized`. The [MCP walkthrough](https://deed.page/blog/mcp-publish-walkthrough) covers the rest.

## FAQ

**Can I host a Bolt site for free outside Bolt?**
Yes, if it builds to static files. deed.page's Free plan is $0 for 25 sites of 25 MB each, with 10 GB of transfer a month per owner; Hobby at $3 a month raises that to 100 GB ([pricing](https://deed.page/pricing)).

**Will my Bolt database still work after I move the site?**
Only the parts the browser calls directly. Values baked in at build time keep pointing at the same backend, but server-side functions and secrets do not come along with the `dist` folder.

**Will the site disappear if nobody visits it?**
No. deed.page sites do not expire unless you send `X-Ttl` for a throwaway page ([TTLs](https://deed.page/blog/ttl-for-throwaway-pages)). Free sites show a small "Published with deed.page" link; Hobby removes it.
