HeyBoss workflow

Take HeyBoss output live on EU infrastructure

HeyBoss spins up a full website from one prompt and, once you unlock export, hands you the front-end React code. Where that code runs is still your call. Point it at VibeDeploy and the site runs under EU jurisdiction on a flat plan, with your own domain and SSL included.

Deploy your HeyBoss site See pricing

Why VibeDeploy for HeyBoss

HeyBoss is happy to generate and host the site in one place, and its per-project code unlock means the React front-end can leave whenever you want it to. The choices that remain are jurisdiction and cost shape. Bringing the export to VibeDeploy settles both: EU data centres, a flat per-plan price, and GitHub-triggered redeploys that keep the workflow automated.

public

European serving for an unlocked build

The React front-end you download from HeyBoss moves onto EU data-centre infrastructure with a DPA on every paid plan. The single-prompt way you generated the site does not change.

shield_lock

Predictable pricing, code you hold

After the one-time unlock the code is yours; hosting it here is a flat per-plan figure with domains and SSL folded in, rather than staying on the platform's bundled hosting.

settings_suggest

Redeploys on every commit

Push the exported files to GitHub, connect the repository, and each commit rebuilds and redeploys. Framework detection covers a React SPA, Vite, Astro, SvelteKit and static Next.js exports.

The HeyBoss to production workflow

1
Generate the site on HeyBoss
Prompt the builder the way it is designed for; its multi-agent pipeline assembles a React front-end and pre-renders the pages. Deployable here is static and SPA output, meaning a React SPA, Vite, a static Next.js export, Astro, SvelteKit or plain HTML. Move on once the result looks right.
2
Unlock the code and download it
On the HeyBoss project page, the download button opens a one-time code unlock for that project; after purchase, choose Download Code to receive the front-end React files. Install the dependencies and run the production build so the compiled output folder is written out.
```
npm install && npm run build
```
3
Hand the build to VibeDeploy
Open a 14-day trial at vibedeploy.eu; no card is requested. Then either link a GitHub repository holding the export so each push triggers a rebuild and redeploy, or drop the output folder onto the dashboard for a one-time publish. Both routes end at a live name.vibedeploy.eu URL.
4
Attach the domain you actually want
Add your own domain in the site settings and create a CNAME pointing at VibeDeploy. The certificate issues on its own, typically inside a minute, and the platform subdomain keeps serving until it does.
5
Optional: let an MCP client do the deploying
Open the exported HeyBoss project in Claude, Cursor, Windsurf or another MCP-capable client and it can deploy through the VibeDeploy MCP server at https://mcp.vibedeploy.be/mcp. Note the boundary: this runs from your editor, because the HeyBoss builder itself 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

The export you receive is the front-end React, which is precisely what a static-edge host is built to serve. A static-edge host will not run an always-on server of your own, so any part of the app that needs a live continuous backend belongs on a server host while the front-end runs here.

Can I get my code out of HeyBoss?expand_more

You can, with a caveat worth knowing: export is a one-time paid unlock per project rather than a free action. Once unlocked, the front-end React files download and re-download freely for that project, and that is the export that lets the site run on EU infrastructure.

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

A static export or SPA-mode Next.js deploys without adjustment, as does a plain React SPA. The server side is what does not carry over: SSR and API routes need a running process, which a static-edge host does not provide. Static output deploys here as-is.

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

Both routes share one hosting layer. It is common to drag the build output onto the dashboard first to confirm the site is live, then connect a GitHub repository later so subsequent pushes redeploy on their own. Switching between them costs nothing.