PromptShip
Migration guide

Migrate from Vercel to PromptShip

Vercel now supports multi-service deployments, WebSockets in Functions, function execution up to 30 minutes, and Marketplace storage with unified billing. Move when you want a different operating model: persistent services, managed database resources, named environment-scoped agent identity, human approval for agent-initiated production writes, and an attributable action trail.

Why teams move

  • A persistent runtime model. Vercel Functions can run for up to 30 minutes. PromptShip services stay running for workloads whose lifecycle should not be tied to a function invocation.
  • Long-lived WebSocket services. Vercel Functions support WebSockets in public beta, with connections bound to the function's maximum duration. PromptShip runs WebSockets on the same persistent service as the rest of your backend.
  • Workers as ordinary processes. Run workers and cron beside your application instead of shaping persistent work around separate function and queue primitives.
  • One workflow for agents and infrastructure. Agent identity, environment-scoped tokens, production approval gates, and action attribution share the same operational surface.
  • Flat resource tiers instead of metered compute usage.

Move all of it, or start with one persistent service

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 and point its API requests at a PromptShip app. Move real-time services, workers, long jobs, or databases when you want them in PromptShip's persistent runtime and agent workflow.

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.

PromptShipVercel
Multi-service app deployments✓Vercel Services
WebSocket connectionsPersistent serviceFunctions (public beta)
Long-running executionPersistent serviceFunctions up to 30 min
Database provisioningManaged resources via MCPMarketplace integrations
Database billingPromptShip resource tiersUnified Vercel billing
Agent identity and action attributionAgent, token, task, environmentTeam activity log
Agent-operation controlsScoped tokens + write approvalsApproved agent actions
Compute pricing modelFlat resource tiersMetered usage
Deploy a standard container image✓Vercel Services
Edge functions / ISR at POPs✕✓

Static assets on PromptShip are CDN-cached globally with Cloudflare in front. Vercel remains a strong choice when you need code at edge POPs or depend heavily on Next.js ISR. PromptShip is the alternative when a persistent runtime and agent-operated infrastructure workflow matter more.

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 combines plan charges with metered infrastructure usage, while Marketplace storage can appear on the unified Vercel bill. PromptShip uses transparent resource tiers with no credits, tokens, or per-request fees. During early access PromptShip is free.

Common questions

Do I have to leave Vercel entirely?

No. You can move the whole app, or keep the frontend on Vercel and move the services that benefit from a persistent runtime and PromptShip's agent workflow. Both work.

Will my Next.js app still work?

Yes. PromptShip runs Next.js SSR and static sites the same way it runs your backend services. You can run the full Next.js app on PromptShip, or leave it on Vercel and only point its API requests at a PromptShip app.

Can I keep my existing database?

Yes. Attach a managed Postgres / Redis / ClickHouse on PromptShip, or keep pointing at Supabase, Neon, Upstash, or whatever you're already on. Your call.

Is PromptShip a wrapper around Cloud Run?

No. PromptShip operates its own platform. Your app builds into a standard Docker image and runs on PromptShip's managed runtime, not Cloud Run, not Vercel, not Render. If you ever leave, your Docker image runs anywhere Docker runs.

Get started

Move from Vercel to PromptShip

Free during early access. Move the whole app, or start with one persistent service.

[ Join the waitlist ]

Already have access? Install the MCP

$ claude mcp add --transport http promptship https://mcp.promptship.dev/mcp