---

[Bolt.new](https://bolt.new) is an AI-powered, full-stack development environment from StackBlitz — describe an app in a chat window and it scaffolds a working project running inside a browser-based WebContainer. Bolt's built-in deploy button targets Netlify. This guide covers the alternative: deploying Bolt.new apps with [DeployHQ](https://www.deployhq.com), where you choose between free Static Hosting on Cloudflare's edge and full-server deployment to your own infrastructure.

## Why Deploy Beyond Bolt.new's Defaults?

Bolt's one-click Netlify deploy is fine for sharing a preview. For shipping a real project, owning the deploy makes more sense:

- **Avoid vendor lock-in.** Each platform's URL accumulates SEO equity, OAuth callback URLs, and integrations that don't migrate cleanly. Picking a portable host up front keeps your options open.
- **Predictable pricing.** Netlify's build-minute caps and bandwidth tier bite earlier than you'd expect on a chatty Vite project. DeployHQ's pricing is flat across the static and managed-VPS tiers.
- **Hosting choice.** Deploy to your own VPS, dedicated server, or shared host over SFTP/SSH/Rsync — or run on Cloudflare's global edge — all from the same DeployHQ project.

## Two Deploy Paths — Pick the Right One

Bolt.new is framework-agnostic — it scaffolds across Vite (React/Vue/Svelte), Astro, SvelteKit, Next.js, and Remix depending on what you ask for. The right deploy target depends on whether your project includes a server-side component:

| Your Bolt project | Deploy target | Why |
|---|---|---|
| Pure frontend — Vite + React/Vue/Svelte SPA, Astro static, SvelteKit static, Next.js static export | **DeployHQ Static Hosting** | Compiled output ships to Cloudflare's edge for free during beta; framework auto-detected |
| Full-stack starter with a `server/` directory (Express, Hono, Fastify) or Next.js server actions | **DeployHQ Managed VPS or your own server** | The server code needs a Node runtime; Static Hosting doesn't provide one |

Both paths use the same DeployHQ project and the same Git workflow — only the deploy target differs. You can start on Static Hosting and switch to Managed VPS later without rewriting your pipeline.

## Step 1: Build Your App with Bolt.new

Navigate to `bolt.new` and sign in or create an account. With Bolt v2, the platform supports Figma imports, GitHub repository integration, and team collaboration alongside the core AI assistant that generates entire applications from a text prompt — no local setup required.

Enter a prompt describing the app: *"Create a portfolio website with sections for About, Projects, and Contact."* The AI generates the full project. You can adjust the result, ask Bolt to add features, or iterate until the app matches what you need.

Bolt's scaffold choice depends on the prompt. Simple UIs typically come out as Vite + React or Vite + Svelte. Marketing sites lean toward Astro. Anything with routing-heavy navigation can come out as SvelteKit or Next.js. The framework choice matters for deployment — covered in Step 4 (Path A) below.

## Step 2: Export Your Project to GitHub

Bolt runs your project inside a StackBlitz WebContainer in the browser. To deploy on DeployHQ, the code needs to live in a normal Git repository.

In the Bolt IDE, click the **GitHub** icon in the top toolbar (or **Export → GitHub** depending on your Bolt version), authorize the GitHub integration, choose a repository name and visibility, and push. Bolt commits the full project — `package.json`, framework config files, `src/`, `public/`, and any `.bolt/` metadata directory — to the `main` branch of the new repository.

Once the repository is live on GitHub, both deploy paths (Static Hosting and Managed VPS) connect DeployHQ to that same repository.

## Path A — DeployHQ Static Hosting (recommended for pure frontends)

If your Bolt project is a pure frontend — Vite + React/Vue/Svelte SPA, Astro static, SvelteKit static, or Next.js with `output: 'export'` — Static Hosting is the cleanest fit. It runs on Cloudflare's global edge, framework-detects the build, and is free during beta.

The end-to-end walkthrough — including the framework→output-directory mapping for every Bolt scaffold (Vite ships to `dist/`, Next.js export to `out/`, SvelteKit to `build/`, Remix to `build/client/`), the WebContainer-path cleanup gotcha, and the SPA mode toggle per framework — lives in [How to Deploy a Bolt App to DeployHQ Static Hosting](https://www.deployhq.com/blog/deploy-bolt-app-to-deployhq-static-hosting). The whole loop takes under 15 minutes.

In summary: you connect DeployHQ to the GitHub repo, point it at Static Hosting, set the output directory based on your framework, run `npm ci && npm run build` in the [build pipeline](https://www.deployhq.com/features/build-pipelines), and push. Every subsequent push deploys atomically with one-click rollback to any previous version.

For the broader positioning around AI-built apps and Static Hosting, the [free static hosting for AI-built apps](https://www.deployhq.com/blog/free-static-hosting-for-ai-built-apps) post covers the choice between v0, Bolt, Lovable, and Firebase Studio as starting points and where each one fits.

## Path B — Your Own Server (Managed VPS, SFTP, SSH, Rsync)

If your Bolt project includes a `server/` directory running Express, Hono, or Fastify, or uses Next.js server actions, Static Hosting can't run that code. [DeployHQ Managed VPS](https://www.deployhq.com/hosting/managed-vps) — or a server you already run — keeps both the frontend and the Node server running end to end.

The pipeline:

1. **Create a DeployHQ project** and connect it to your GitHub, GitLab, or Bitbucket repository.
2. **Add a server** under **Servers & Groups → New Server**. Pick Managed VPS, SFTP, SSH, Rsync, or S3 depending on where you're hosting, and enter the connection details.
3. **Configure the build pipeline** under the project's Configuration tab. For a typical Bolt project, `npm ci && npm run build` covers most frameworks. Adjust if your `package.json` uses pnpm or yarn instead of npm.
4. **Set environment variables** in DeployHQ's environment-variable UI — Vite uses `VITE_*` prefixes, Next.js uses `NEXT_PUBLIC_*`, Astro uses `PUBLIC_*`. Secrets that should never reach the client (database URLs, server-only API keys) stay on the server side.
5. **Set the deploy path** to where the server expects your files (`/var/www/your-app`, `/public_html`, or wherever your hosting provider drops compiled output).
6. **Deploy** from the **Deployments** tab — pick the branch (typically `main`), select the configured server, and click Deploy.

For a Node server that needs to run continuously, set up a process manager (`pm2`, `systemd`, or your provider's equivalent) and a post-deploy SSH command to restart it after each deploy.

[Sign up free for DeployHQ](https://www.deployhq.com/signup) to start a project — the free tier covers the first connected repo, and the included Static Hosting site lets you try Path A end to end before deciding which suits the project.

## Step 5: Set Up Automatic Deployments

One of DeployHQ's most useful features is [automatic deployments](https://www.deployhq.com/features/automatic-deployments) triggered by a Git webhook. Once configured, every push to your repository kicks off a deployment — no manual intervention required.

In DeployHQ's project settings, navigate to **Automatic Deployments** and copy the webhook URL. In your GitHub repository's **Settings → Webhooks**, add a new webhook, paste the URL, set the content type to `application/json`, and choose the **push** event. From that point on, pushing to your configured branch triggers a deployment.

This is particularly useful when iterating quickly with Bolt: tweak the app in the IDE, push to GitHub, watch DeployHQ deploy within minutes.

The same webhook works whether you're deploying via Path A (Static Hosting) or Path B (Managed VPS or your own server) — DeployHQ runs whichever pipeline you configured.

## Step 6: Monitor Your Live Application

DeployHQ provides a detailed log of every deployment so you can monitor status in real time. The logs show files transferred, errors encountered, and the success or failure of each step. If something breaks, the [one-click rollback](https://www.deployhq.com/features/one-click-rollback) button on the dashboard reverts to the previous deployment in seconds while you and Bolt work out what went wrong.

## Building With Other AI Tools?

If you're evaluating the broader AI-app-builder landscape, the DeployHQ deployment guides cover the major options:

- [Lovable](https://www.deployhq.com/guides/lovable) — Vite + React with Supabase backend
- [v0](https://www.deployhq.com/guides/v0) — Vercel's AI-powered platform, primarily Next.js
- [Firebase Studio](https://www.deployhq.com/guides/firebase-studio) — Google's AI-powered cloud IDE
- [Replit](https://www.deployhq.com/guides/replit) — full development environment with deploys

For AI-assisted coding editors that work alongside your local stack, see the [Cursor](https://www.deployhq.com/guides/cursor), [Windsurf](https://www.deployhq.com/guides/windsurf), and [Cline](https://www.deployhq.com/guides/cline) setup guides.

---

Questions or feedback on deploying Bolt.new projects with DeployHQ? Email [support@deployhq.com](mailto:support@deployhq.com) or follow [@deployhq](https://x.com/deployhq) on X for product updates.