Deploy Softgen

Deploy Softgen sites with VibeDeploy

Softgen turns a natural-language spec into a production-ready Next.js project and exports it to GitHub on every plan. When your front-end is ready, VibeDeploy publishes that build to an EU-resident host with a custom domain, automatic SSL, and flat per-plan pricing.

Deploy your Softgen site See pricing

Why VibeDeploy for Softgen

Softgen writes a Next.js frontend with React, Tailwind and shadcn/ui, backed by Firebase or Supabase, and gives you GitHub export on every plan so you keep full ownership. The usual deploy path from there is Vercel. If you would rather serve the front-end from the EU on a predictable flat plan, you point that export at a dedicated host. That is the gap VibeDeploy fills.

public

EU hosting for a Softgen build

Softgen's default deploy path is Vercel, which is US-based. VibeDeploy serves your exported front-end from a Belgian data centre, so your site and your visitors' data stay in the EU. A DPA is available on every paid plan.

shield_lock

Flat pricing, code you own

You keep 100% of the code through Softgen's GitHub export. VibeDeploy hosting is one flat price per plan with custom domains and automatic SSL included, so your hosting bill stays predictable.

settings_suggest

Framework detection

Softgen produces a Next.js project. 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 Softgen site

1
Build your app on Softgen
Describe the app in plain English and let Softgen generate the Next.js frontend with React, Tailwind and shadcn/ui. VibeDeploy serves static and SPA output: a static Next.js export, a React SPA, Vite, Astro, SvelteKit, or plain HTML. When the preview looks right, you are ready to export.
2
Export to GitHub
Softgen offers GitHub export on every plan. Push the project to a repository, then produce a production build (commonly npm run build), which writes the output folder for static export or SPA mode.
```
npm install && npm run build
```
3
Connect to VibeDeploy
Start a 14-day free trial at vibedeploy.be (no credit card). Connect the 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 Softgen 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 Softgen builder, which 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

VibeDeploy serves the static or SPA front-end. Softgen backs apps with Firebase or Supabase, which are external services your front-end calls from the browser, so they keep working from a static deploy. What VibeDeploy does not run is an always-on server or SSR process of your own; for that part use a server host.

Can I get my code out of Softgen?expand_more

Yes. Softgen includes GitHub export on every plan and gives you 100% ownership of the code, so you are not locked in. Once the project is in your repository you can host it anywhere, including on VibeDeploy in the EU.

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

Static export and SPA-mode Next.js work out of the box. Server-side rendering and API routes need the Next.js server running, which is not part of VibeDeploy's static-edge model. For SSR-heavy Next.js use a server host; for static-export Next.js, just deploy the output.

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 the exported GitHub repo later so every push rebuilds and redeploys. Same hosting either way.