ZIP export or GitHub — both routes work

Host a bolt.new buildon your own address

Bolt runs your project in the browser and hands you the code. Export it once and dplooy builds it and serves it from your own subdomain, with free SSL and analytics you can read.

1Export the projectGitHub or ZIP
2Build the outputor let us do it
3Deploylive on your subdomain

The preview is not the product

Bolt's in-browser preview is what makes it fast to build in. It isn't where a finished site should live.

Living in the preview

  • The URL belongs to the tool, not to your project
  • Tied to the session and the account you built in
  • No custom domain to hand to a client
  • No analytics you can export or act on
  • Search engines have nothing to index

Hosted on dplooy

  • yourname.dplooy.com, or your own domain on Pro
  • Free SSL, managed and renewed for you
  • Views, visitors, countries and referrers with CSV export
  • robots.txt, sitemap.xml and a 25-point SEO audit
  • Redeploy from GitHub on every push, or upload again by hand

Export once, then deploy as often as you like

1

Get the code out of Bolt

Two options. Push the project to GitHub from Bolt's GitHub integration, which is the one to pick if you'll keep working on it. Or use the export menu on the project and download a ZIP of the whole thing for a one-off.

2

Decide who runs the build

Bolt projects are usually Vite and React, which means the browser can't run them as-is. Either run npm install and npm run build yourself to get a dist folder, or hand the repo to us and let the build run on GitHub's servers.

3

Deploy it

For the GitHub route: click Deploy from GitHub, pick the repo and branch, and confirm Set up build & deploy when we detect Vite. For the local route: click Choose folder and pick dist, or drag the ZIP of your built output in and choose ZIP to site.

4

It's live on your subdomain

Served over HTTPS with free SSL. Through GitHub, every later push rebuilds and redeploys to the same URL — analytics, custom domain and settings all preserved.

A ZIP of the whole project is not a website

The ZIP Bolt hands you contains package.json, a src folder and node_modules — source code a browser cannot execute. Uploading it produces nothing useful, so we detect that shape and tell you instead of hosting a blank page. Build first, then upload only the dist folder — or skip the whole question by deploying through GitHub, where we run the build for you.

What the built site gets

Once it's out of the preview, it behaves like any other production site.

Your own subdomain

yourname.dplooy.com instead of a link that names somebody else's product. Point a custom domain at it on Pro.

Free SSL, always on

Every site is served over HTTPS with a certificate we manage. Nothing to buy, configure or renew.

Real analytics

Views, unique visitors, countries, referrers and devices — for the whole site, exported as CSV whenever you want it.

Findable in search

robots.txt and sitemap.xml are generated for you, and the SEO analyser scores 25 checks and tells you what to fix.

Editable after publishing

Change text, images and colours on the live page with the visual editor, on any plan. Pro adds a full in-browser code editor.

Private when you need it

Password-protect the whole site on Pro, or put an email gate in front of it and collect the addresses.

Frequently asked questions

Which export should I use, GitHub or ZIP?

GitHub, if the project is still moving — it gives you version history and lets Dplooy rebuild and redeploy on every push. ZIP, if the site is finished and you just want it online once. Both end at the same place.

Do I need Node installed on my machine?

Only for the local route. If you deploy through GitHub, Dplooy commits a workflow that runs npm install and your build command on GitHub's servers — nothing has to be installed locally.

My Bolt app has a backend. Can you host that?

No, and that's deliberate. Dplooy serves static files rather than running your code, which is why sites here are fast and cheap. Host the front end with us and keep the API wherever it runs today — just allow your dplooy domain in its CORS settings.

What if my project isn't Vite?

We read package.json and detect Next.js, Nuxt, SvelteKit, Astro, Angular and Create React App as well, filling in the right build command and output folder for each. Next.js needs a static export — set output: "export" in next.config — because there's no Node process here to render pages on demand.

Will client-side routing work?

Yes. Single-page apps are detected at deploy time, so deep links fall back to index.html and answer with a 200 rather than a 404, which means they can be indexed. Missing assets still return a real 404.

Can I use my own domain?

Yes, on Pro. Connect any domain you own, add the DNS records we show you, and the site answers on your address with SSL we manage.

Is it free?

Yes, on the free plan: 3 hosted projects, free SSL and analytics. Free-plan sites are removed after 3 days. Plus and Pro sites stay up indefinitely, and Pro adds custom domains and password protection.

Get it out of the browser tab

Create a free account, connect the repo or drop the build in, and it's live in minutes.