Migrate from Replit

Replit charges $20–$700/mo for "Always-on" hosting of vibe-coded apps. If your app is fundamentally a frontend (HTML / React / etc.) with no need for a long-running Python/Node process, VibeHost hosts it for free on the static runtime.

This isn't a knock on Replit — their dev environment is great for prototyping. It's that "deploy to a real URL" doesn't have to live on the same platform you developed on.

Where your Replit app lands

Your Replit app is...	Where it lands on VibeHost
Static HTML / pure frontend (React, Vue, Vite-style)	Static runtime — free tier
Server-rendered app with API routes	Server-side rendering is in private beta — see the Next.js guide for status, or keep the backend on a managed service for now
Python / Flask / FastAPI backend	Not VibeHost — pair with Fly.io / Render / Railway for the backend, VibeHost for the frontend
Long-running bot / cron worker	Not VibeHost — use a VM or a dedicated worker host

Static case (most vibe-coded apps)

If your Replit app is HTML + CSS + JS (with or without a build step like Vite):

1. Export from Replit

In Replit: Three-dot menu → Download as zip. Unpack locally.

unzip your-replit-app.zip -d your-replit-app
cd your-replit-app

2. Build (if needed)

If there's a package.json:

npm install
npm run build

Build output usually lands in dist/, build/, or out/. Check package.json scripts to confirm.

If there's no build step (plain HTML), the source dir itself is what you deploy.

3. Deploy

vibehost app create my-app
vibehost link --app my-app
vibehost deploy ./dist            # or ./build, or .

Verify the URL works. If it's an SPA with browser-history routing:

vibehost deploy ./dist --spa

4. Replace the Replit URL

If anyone has the Replit URL bookmarked or linked, set up a redirect from the Replit app to the VibeHost URL.

In Replit, edit index.html to:

<!doctype html>
<meta http-equiv="refresh" content="0;url=https://my-app.vibehost.space">
<a href="https://my-app.vibehost.space">Moved to https://my-app.vibehost.space</a>

After 30 days, turn off Always-on on Replit and let the Repl idle.

5. Stop the Replit bill

Settings → Subscriptions → Cancel Hacker / Pro / Core. Replit will keep your projects but pause Always-on hosting.

Annualized savings: $240 (Hacker $20/mo) to $700+ (Pro deployments) depending on what tier you were on.

Server-rendered case

If your Replit app is a server-rendered framework (Next.js with API routes, SvelteKit on Node, Remix on Node), VibeHost's server runtime is currently in private beta — see the Next.js guide for status. Until it's generally available, the pragmatic path is the split-and-pair pattern below.

Backend-heavy case

If your Replit app is meaningfully a backend (Flask / FastAPI / Django, a Discord bot, a polling worker), VibeHost is the wrong tool — we host frontends, not arbitrary processes.

The split-and-pair pattern:

Frontend → VibeHost (static).
Backend → Fly.io, Railway, Render, fly.machines, or any managed compute host.

Architecturally cleaner anyway. Cost is usually still 50–80% lower than Replit Always-on at the same scale.

Pricing comparison (illustrative, 2026-05)

Tier	Replit	VibeHost equivalent
One static site, low traffic	Hacker $20/mo	Free ($0)
Multiple static sites + custom domain	Core $30/mo	Business $20/mo (unlimited apps in one workspace)
Server-rendered app with DB	Pro $35/mo + DB	Frontend on VibeHost free; pair with a managed backend host until the server runtime ships GA
5+ deploys, heavy traffic	Pro Deployments $700+/mo	Enterprise (talk to sales)

The fundamental difference: Replit's pricing tracks "always-on compute". VibeHost's tracks the workspace tier — number of apps doesn't change the bill. If you're hosting many small sites, the spread is dramatic.