Softgen workflow

Take Softgen output live on EU infrastructure

Softgen compiles a natural-language spec into a real Next.js project and exports it to GitHub on every plan, so the code is genuinely yours. Where the front-end runs is the open question. Point it at VibeDeploy and it runs under EU jurisdiction on a flat plan, with your own domain and SSL included.

Deploy your Softgen site See pricing

Why VibeDeploy for Softgen

Once Softgen has written the Next.js app and pushed it to your repository, the default next move is a US-based Vercel deploy. The choices that remain are jurisdiction and cost shape. Aiming the export at VibeDeploy resolves both: EU data centres, a flat per-plan price, and GitHub-triggered redeploys that keep the workflow automated.

public

European serving for an exported build

The Next.js project Softgen pushes to GitHub moves onto EU data-centre infrastructure with a DPA on every paid plan. The plain-English way you specified the app does not change.

shield_lock

Predictable pricing, code you own

GitHub export already gives you the whole codebase; hosting it here is a flat per-plan figure with domains and SSL folded in, rather than a plan-plus-token bill that climbs while you keep generating.

settings_suggest

Redeploys on every commit

Connect the repository Softgen exported to and each push rebuilds and redeploys. Framework detection covers the Next.js output, plus Vite, Astro and SvelteKit.

The Softgen to production workflow

1
Specify the app on Softgen
Write the requirements in plain English and let Softgen assemble the Next.js frontend from React, Tailwind and shadcn/ui. Deployable here is static and SPA output, meaning a static Next.js export, a React SPA, Vite, Astro, SvelteKit or plain HTML. Move on once the preview matches the spec.
2
Push the project to GitHub
Every Softgen plan includes GitHub export, so send the project to a repository. Then install the dependencies and run the production build so the compiled output for static export or SPA mode 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 the GitHub repository 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 Softgen 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 Softgen builder itself does not connect to external MCP servers.

Softgen hosting at a glance

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

Feature	Softgen default / generic alt	VibeDeploy
Hosting location	Vercel (US)	EU (Belgium)
Pricing model	Plan + usage tokens	Flat per plan
Custom domain	On your chosen host	Yes, on every plan
Automatic SSL	On your chosen host	Yes
Best fit	Full-stack spec-to-app	Static / SPA front-ends

Common questions about deploying Softgen

Does VibeDeploy run the Firebase or Supabase backend Softgen set up?expand_more

The Firebase or Supabase layer Softgen provisions is an external service the front-end reaches from the browser, so it keeps working from a static deploy. A static-edge host will not run an always-on server or SSR process of your own; keep that on a server host and serve the front-end layer here.

Can I get my code out of Softgen?expand_more

Ownership is the point: GitHub export ships on every plan and you retain 100% of the code, so nothing keeps you on the platform. That repository is exactly what lets you host the app on EU infrastructure instead of the default target.

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

Configured for static export or SPA mode, Next.js deploys without adjustment. The server side is what does not carry over: SSR and API routes need a running Next.js process, which a static-edge host does not provide. Server-rendered apps belong on a server host; exported ones deploy here as-is.

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

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