Updated 6 min readBy The VibeDeploy team

v0 and Bolt output, shipped to production in Europe

What v0 and Bolt actually hand you, how to turn it into a build or a container, and what running it in production on EU infrastructure involves.

Built it? Ship the folder

Run the build, drop dist/ or out/ into VibeDeploy and get a live URL on servers in Belgium. 14 days free, no card.

Every code generation tool has a moment where its responsibility ends, and a default for what happens next. v0 is Vercel's product, and its Publish button deploys to a connected Vercel project. Bolt publishes to its own bolt.host address and can hand projects to Netlify instead. Neither default is wrong, but both are defaults, and for a European project the deploy target is exactly the decision worth making on purpose, because it fixes your jurisdiction, your billing model and your operating workflow in one move.

This piece covers the path from either tool to a production site on EU infrastructure, starting with the part most guides skip: understanding what you are actually holding when the generator finishes.

What each tool hands you

The two tools produce different artifacts, and the difference determines your first step.

v0 builds whole Next.js apps. According to v0's own documentation, it "uses Next.js, React, TypeScript, Tailwind CSS, and shadcn/ui", and its previews now run the full application in Vercel Sandbox, server-side code and API routes included. Connect a GitHub repository and the code lives there; without one, v0 still lets you take the code out. Its FAQ answers the obvious question directly: for the full experience your repository should be connected to a Vercel project, but "You can still export code and deploy elsewhere."

Bolt gives you a whole project, with optional Bolt services around it. Bolt's documentation describes the download: click the project title in the top left, then Export, then Download, and you get a ZIP "to work on it outside of Bolt, using your own code editor." A GitHub connection works too. Bolt also offers its own database and server functions; if your project uses them, those parts live in Bolt's cloud rather than in the files you download.

The common ground matters more than the differences: both tools hand you an ordinary JavaScript project with a package.json, which you can build and run like any other.

From project to build

A production host serves the compiled result, not your source. For a Vite project that means:

npm install
npm run build

which produces a dist/ folder of plain HTML, JS and CSS. For a Next.js app that only renders in the browser, add output: 'export' to the Next.js config to get a static out/ folder. That folder is the deployable unit, and it is worth running this step locally at least once even if an agent will handle it later, because a production build is stricter than a preview, and finding an error on your own machine beats finding it mid-deploy. On VibeDeploy, uploading a project that has a package.json but no build output is refused with the code UNBUILT_PROJECT, precisely so that nobody ships source files by accident.

Two honest boundaries to check before continuing. If the generator hardcoded localhost URLs for API calls, replace them now, since they point at a machine your visitors do not have. And if the app has a real server side, such as Next.js API routes or server actions from v0, or an Express backend from Bolt, a static export cannot carry it. On VibeDeploy that server can run as a container next to the site, deployed by your AI through the MCP tool deploy_app and isolated with gVisor: your own server, plus Postgres, MySQL or Redis if it needs them, up to 6 services with 2 CPU and 2 GiB in total. Container data is not yet included in snapshots. Parts that run on Bolt's database or server functions stay with Bolt unless you rebuild them elsewhere.

Landing the build on European infrastructure

With a build folder in hand, VibeDeploy accepts it in four ways, and which you pick is a workflow preference rather than a capability difference:

  • Drag it in. Upload the build folder or a ZIP in the dashboard, and the site is live on a platform subdomain with HTTPS. The step-by-step version is at deploy localhost to production.
  • Let an agent do it. If you iterate in Cursor, Windsurf or Claude, connect the VibeDeploy MCP server once and deployment becomes something you ask for in the same conversation where the code changes. The Cursor and Windsurf pages show the configuration; how MCP changes iteration rhythm is explored in from a ChatGPT or Claude chat to a live European website.
  • Paste the deploy guide. A chat assistant without MCP can still deploy from the guide in your dashboard: it either sends the files itself or gives you a deploy page to open in your browser.
  • Connect a repository. Push the project to GitHub and every push builds and redeploys, which suits Bolt's download-and-iterate loop and v0's GitHub sync well.

Tool-specific notes live at /for/v0 and /for/bolt. Your own domain comes afterwards: add it in the dashboard, set the DNS records it shows you, and the certificate is issued automatically. The 14-day trial already lets you link one domain you own.

What "production" adds that the generator could not

Uploading files makes a site reachable. Production is the set of behaviours around the files, and none of them exist inside v0 or Bolt because none of them are code:

  • Staging, on Studio and Business, gives regenerated versions a testing copy at its own address to be reviewed on before they replace the live site, which matters when the diff was written by a model rather than read by a person.
  • Restore points make every deploy reversible: a restore point is taken before each deploy, and an earlier version comes back in one click from the dashboard within your plan's window (3 days on the trial, Solo and Maker, 7 on Studio, 30 on Business). An iteration that looked fine in the preview and wrong in reality costs one restore instead of an evening.
  • Forms need a receiving end; on VibeDeploy the built-in relay emails submissions to you from the same Belgian platform, instead of a third-party handler the generator picked for you.
  • Analytics are built into the hosting, so measurement does not drag a foreign processor into an otherwise clean site.

The deeper treatment of these four, and why AI-generated frontends need them more rather than less, is in deploying AI-generated frontends to production in the EU.

Why the EU part is not decoration

The build folder is identical wherever you host it. What changes with the target is everything around the folder: the company operating the machines, the law that reaches them, and the answers you give when a customer's questionnaire arrives. On VibeDeploy the operator is Tnet Comm.V in Belgium, sites run on its own Kubernetes cluster in Belgium, and a DPA covers the processing on every paid plan. The eight sub-processors are named on a public list, and customer site content does not pass a US processor unless you use the AI site-builder features. For a site aimed at European users, that turns a future compliance conversation into a short one. The reasoning in full is in data sovereignty for AI-built websites, and if you are still comparing hosts, the European alternatives to Vercel and Netlify list has the options side by side.

Cost stays flat rather than metered: 4, 15 or 39 euro per month depending on scale, prices including VAT where it applies, with a 14-day trial and no card up front, compared on the pricing page.

The generators have made frontends cheap. Treat the deploy target as the one decision in the pipeline that is still entirely yours, and spend it deliberately.

Sources

Vendor documentation checked on 13 October 2026:

From the VibeDeploy team

Ship your AI-built site in minutes

VibeDeploy hosts your AI-built websites in the EU with custom domains, automatic SSL, and a 14-day free trial that gets you online today.

Deploy guides for this topic

Related reading