Move from Vercel to VibeHost

Most Vercel projects on VibeHost today fall into one of two buckets:

• Static export (Next.js output: 'export', Astro static, Vite SPA, MkDocs, etc.) — supported now. The flow is the same as the Netlify migration: build locally, vibehost deploy ./out, move your custom domain.
• Server-rendered apps (Next.js with API routes / server actions / ISR, SvelteKit on Node, Remix on Node) — in private beta. See the Next.js guide for status and how to request access.

A full Vercel-to-VibeHost migration walkthrough — env var transfer, ISR cache notes, cron replacement, feature-parity table — is in the works and ships alongside general availability.

In the meantime

• Static export migration? Follow the Netlify recipe — same shape, just substitute "Vercel" for "Netlify" at each step. The static deploy, _redirects / _headers, and custom-domain steps all apply unchanged.
• Server-rendered Next.js? Read the Next.js guide, then email contact@vibehost.com with your workspace slug to request beta access.
• Want notification when this recipe goes live? Star the repo or follow the changelog.

See also

• Next.js — current status and runtime details
• From Netlify — the closest currently-complete migration walkthrough
• Custom domains — DNS provider walkthroughs for the cutover step