Deploy HeyBoss

Deploy HeyBoss sites with VibeDeploy

HeyBoss builds a complete website from a single prompt in minutes and lets you unlock and download the front-end code. When your site is ready, VibeDeploy hosts that React export on an EU-resident host with a custom domain, automatic SSL, and flat per-plan pricing.

Deploy your HeyBoss site See pricing

Why VibeDeploy for HeyBoss

HeyBoss generates and hosts a website end to end, and it can export the front-end React code once you unlock it for a project. If you would rather own the deploy and serve the site from the EU on a predictable flat plan with your own domain, you move that export to a dedicated host. That is the gap VibeDeploy fills.

public

EU hosting for a HeyBoss export

HeyBoss hosts what it generates on its own infrastructure. VibeDeploy serves your exported front-end from a Belgian data centre instead, so your site and your visitors' data stay in the EU. A DPA is available on every paid plan.

shield_lock

Flat pricing, your own code

Once you unlock code export for a project, the React front-end is yours to host anywhere. VibeDeploy is one flat price per plan with custom domains and automatic SSL included, so your hosting bill stays predictable.

settings_suggest

Framework detection

HeyBoss exports a React front-end. VibeDeploy detects the build command and output directory for Vite, static Next.js export, Astro, SvelteKit or plain HTML, so most exports deploy with no extra config.

How to deploy a HeyBoss site

1
Build your site on HeyBoss
Prompt HeyBoss to generate the site as normal; its multi-agent system produces a React front-end with pre-rendered static pages. VibeDeploy serves static and SPA output: a React SPA, Vite, static Next.js export, Astro, SvelteKit, or plain HTML. When it looks right, you are ready to export.
2
Unlock and download the code
In HeyBoss, use the download button on the project page to unlock code export (a one-time purchase per project), then choose Download Code to get the front-end React files. Install dependencies and produce a production build, which writes the output folder.
```
npm install && npm run build
```
3
Connect to VibeDeploy
Start a 14-day free trial at vibedeploy.be (no credit card). Push the exported files to a GitHub repo so every push builds and redeploys automatically, or drag the build output folder into the dashboard for a one-off deploy. Either way you get a live URL at name.vibedeploy.be.
4
Add your custom domain
In site settings, add your domain and point a CNAME at VibeDeploy. SSL provisions automatically, usually within 60 seconds. Until then the site stays live at name.vibedeploy.be.
5
Optional: deploy from a Claude or Cursor session
If you open your exported HeyBoss project in an MCP-capable client such as Claude, Cursor, or Windsurf, that client can deploy through the VibeDeploy MCP server at https://mcp.vibedeploy.be/mcp. This runs from your editor, not from inside the HeyBoss builder, which does not connect to external MCP servers.

HeyBoss hosting at a glance

How HeyBoss's default hosting and a generic alternative compare to VibeDeploy.

Feature	HeyBoss default / generic alt	VibeDeploy
Hosting location	HeyBoss infra	EU (Belgium)
Pricing model	Plan + paid code unlock	Flat per plan
Custom domain	Yes	Yes, on every plan
Automatic SSL	Yes	Yes
Best fit	All-in-one generate and host	Static / SPA front-ends

Common questions about deploying HeyBoss

Does VibeDeploy run a HeyBoss backend too?expand_more

VibeDeploy serves the static or SPA front-end. HeyBoss code export gives you the front-end React, which is exactly what fits a static-edge host. What VibeDeploy does not run is an always-on server of your own; if part of your app needs a live backend running continuously, keep that on a server host.

Can I get my code out of HeyBoss?expand_more

Yes, with a caveat. Code export is a paid unlock per project rather than a free feature, but once purchased you can download and re-download the front-end React files for that project as often as you like. That export is what lets you host the site on VibeDeploy in the EU.

What about a static Next.js site from HeyBoss?expand_more

Static export and SPA-mode Next.js work out of the box, as does a plain React SPA. Server-side rendering and API routes need a server running, which is not part of VibeDeploy's static-edge model. For static output, just deploy it.

Do I have to use GitHub, or can I upload once?expand_more

Either. You can drag the build output into the dashboard for a quick one-off, then connect a GitHub repo later so every push rebuilds and redeploys. Same hosting either way.