Take Bolt.new output live on EU infrastructure
Bolt.new proves the idea in the browser; production asks harder questions about domains, jurisdiction and uptime. VibeDeploy answers them with EU-hosted infrastructure that takes the standard Vite export as-is.
Why VibeDeploy for Bolt.new
Bolt's built-in publishing keeps the site with StackBlitz, a US-headquartered company, and your own domain there needs a paid Bolt plan. If your users, clients or compliance requirements sit in Europe, the export is your decision point: build it once, deploy to VibeDeploy, and the site runs under EU jurisdiction with a domain and snapshots instead of a sandbox URL.
Real servers, EU jurisdiction
The production build leaves the WebContainer and runs on EU data-centre infrastructure operated by a European company, with a DPA on every paid plan.
Vite output deploys untouched
Bolt's default Vite + React + Tailwind export builds to a dist folder that deploys with zero configuration. Drag it in or push the repo; an API of your own can join it later as a container.
Costs that survive success
Flat per-plan pricing with bandwidth included and no overage billing, instead of a hosting cap that switches the site off for the rest of the month.
The Bolt.new to production workflow
- 1
Prove the app inside Bolt.new
StackBlitz's in-browser environment is where you iterate. The moment the preview behaves the way you want, the building phase is over and the shipping phase starts.
- 2
Download the source
Open the project and click its title in the top-left corner; under Export, choose Download to get a ZIP of the complete source. Unpack it on your own machine.
- 3
Compile the production bundle
Bolt projects are typically Vite-based, so two commands produce the dist folder that actually gets served.
npm install npm run build - 4
Create the site on VibeDeploy
A 14-day trial needs no credit card and covers one site on your own domain, with SSL and a restore point before every deploy. Create the site in the dashboard and upload the dist folder.
- 5
Route your domain to it
A TXT record proves the domain is yours, and a CNAME (or an A record at the apex) points it at VibeDeploy; the SSL certificate then issues automatically inside a minute. The vibedeploy.eu subdomain every site gets keeps answering as well.
Further reading on Bolt.new
Bolt.new hosting at a glance
How Bolt.new's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Bolt.new default / generic alt | VibeDeploy |
|---|---|---|
| Who runs the hosting | StackBlitz, Inc. (US) or Netlify | Tnet Comm.V (Belgium) |
| Default URL | *.bolt.host | *.vibedeploy.eu or your domain |
| Traffic | Free: 10 GB and 333,333 requests a month, hard limit | Included per plan, no overage billing |
| Custom domain | Paid Bolt plans only | Every plan, the trial included |
| Backend | Bolt Database and server functions | Containers next to the site (deploy_app) |
| GDPR DPA | US-headquartered processor, check your Bolt agreement | All paid plans, EU processor |
Common questions about deploying Bolt.new
Where is the ZIP download for a Bolt.new project?expand_more
Inside the open project, click its title in the top-left corner and pick Export, then Download, to save an archive of the complete source. Extract it locally, install the listed packages, and run the project's build command. With the common Vite setup, npm run build creates the dist directory that is ready for a static host.
What turns a downloaded Bolt project into a public website?expand_more
First compile the extracted source, then send the resulting output folder to VibeDeploy or connect a GitHub repository so pushes rebuild it. Register your domain in the dashboard, publish the TXT record it asks for and aim a CNAME at the platform. An SSL certificate is provisioned automatically, with no separate certificate setup.
Do StackBlitz-specific pieces of a Bolt project survive in production?expand_more
Everything client-side does. The typical Vite + React + Tailwind output compiles to static assets, and the WebContainer-only conveniences such as mock APIs and hot reload never make it into a production build in the first place.
Is there an automatic redeploy path when I keep editing in Bolt?expand_more
Bolt connects to GitHub natively and syncs its commits for you, so the loop needs no manual step: connect that repository to VibeDeploy and VibeDeploy rebuilds and redeploys on every push to that repo.
How do server-side routes or APIs from a Bolt project behave?expand_more
Bolt's standard templates are single-page apps whose calls to services such as OpenAI or Supabase go straight from the visitor's browser, and VibeDeploy serves those unchanged. Code that needs a process of its own, an Express API for instance, runs as a container beside the site in Belgium, started by your AI through the deploy_app MCP tool, optionally with a Postgres or Redis service. Snapshots do not capture container volumes yet, so export that database on your own schedule. Pieces that live in Bolt Cloud, such as Bolt Database and its stored secrets, remain with Bolt.
Bolt can publish the site itself. Why deploy here instead?expand_more
Bolt's own hosting gives you a *.bolt.host address and asks for a paid Bolt plan before it accepts your domain, and its Netlify alternative bills bandwidth in credits per GB. VibeDeploy is the European counterpart: a Belgian operator, flat per-plan pricing with no overage billing, and your own domain on every plan, the trial included.
Can I continue a Bolt.new project in Claude Code?expand_more
You can. Pull the code out through Bolt's GitHub sync or the Export, then Download entry under the project title, and start Claude Code in that folder; its /init command drafts a CLAUDE.md that records how the project builds. Add VibeDeploy as an MCP server (claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp), authorise it with /mcp, and the agent publishes the build to hosting in Belgium. Whatever lives in Bolt Cloud, Bolt Database or stored secrets for example, has to be moved on its own.
More tool workflows
Put your Bolt.new work into production
14-day free trial, no credit card. Your own domain and snapshots included. Runs on EU infrastructure.