Migrate from Vercel to PromptShip

Why teams move

• Cold starts and execution timeouts. Vercel functions cold-start, then time out, fine for request-scoped work, painful for anything that needs warmth or longevity.
• No real WebSockets. Vercel's edge runtime makes long-lived connections impractical. Real-time apps end up bolted onto a third-party WebSocket service.
• No background workers or cron. You ship them on Upstash, Inngest, or QStash and pay per invocation.
• Edge-only restrictions for backend code. Native modules, long-lived state, and most workloads bigger than a typed handler do not fit cleanly.
• Per-request and per-function billing that scales unpredictably with traffic.

Move all of it, or just the parts Vercel can't run

PromptShip runs Next.js SSR and static sites the same way it runs your backend services, so a full migration is one deploy, not a re-platforming project. Connect your repo, attach a managed Postgres or keep pointing at Supabase / Neon / whatever you're already on, ship.

Prefer to move gradually? Leave Next.js on Vercel, point its API requests at a PromptShip app, and stop paying Vercel for the compute that drives the bill, real-time, workers, long jobs, the database side.

Set NEXT_PUBLIC_API_URL to your PromptShip app URL, deploy, done. CORS is straightforward; both sides serve HTTPS by default. When you're ready to move the frontend, that's just another deploy.

PromptShip vs Vercel

Where each platform actually shines.

Static assets on PromptShip are still CDN-cached globally (Cloudflare in front). Vercel's edge advantage kicks in when you need code running at POPs or heavy Next.js ISR, real, but invisible for most apps. The items above tend to matter more, and the bill stays predictable as traffic grows.

Step-by-step migration

1. 1. Add the PromptShip MCP to your AI IDE. One command in Claude Code, Cursor, or Codex.
2. 2. Move your API routes to a backend service. Most Next.js API routes are already standard Node handlers, Express, Hono, Fastify, or whatever your framework prefers. Your AI IDE will do the bulk of this.
3. 3. Deploy via MCP. PromptShip builds the image, attaches Postgres / Redis / ClickHouse, sets up SSL, gives you a live URL.
4. 4. Point your Vercel frontend at the new backend. Update NEXT_PUBLIC_API_URL, redeploy the frontend, decommission the Vercel functions you no longer need.

Pricing comparison

Vercel Pro starts at $20/seat plus per-function and per-bandwidth fees that scale with traffic. PromptShip's backend + Postgres tier starts at $10/month, transparent and capped. No credits, no tokens, no per-request fees. During early access PromptShip is free.

Common questions