Migrate from Vercel
Move a Vercel project to Doable in one wizard
Outgrowing Vercel's pricing, edge runtime quirks, or vendor lock? Point Doable at the same GitHub repo. Same auto-deploy-on-push, same HTTPS-by-default, same Next.js / Vite / Astro support — running on managed cloud or a Hetzner / DigitalOcean / Vultr / Linode box you own.
From Vercel to Doable in three steps
- 1
Don't export — just point Doable at the same repo
Your Vercel project is already on GitHub. Install the Doable GitHub App, pick the same repo in the wizard, and Doable starts deploying from it. You can keep Vercel deploying in parallel during the migration.
- 2
Re-create env vars in Doable
Doable's CLI auto-detects a local .env and offers to sync missing keys before the first deploy. Or paste them into the project settings. Encrypted at rest; never visible after save.
- 3
Swap DNS when you're ready
Doable gives you a free .doable.do subdomain for testing on Doable Cloud. When the new deploy looks good, move your domain's DNS to point at Doable using the generated records. Cut Vercel off after.
The new-project wizard at /projects/new walks you through this end-to-end with a step-by-step guide for Vercel.
Why deploy Vercel projects through Doable
Predictable pricing
Doable Cloud's hobby tier is free; paid tiers are flat monthly, no per-request billing. BYO on a $5-$20/mo VPS handles most production workloads with no usage surprises ever.
BYO server is first-class
Vercel doesn't deploy to your own infra. Doable does — provision a Hetzner / DigitalOcean / Vultr / Linode box from inside the wizard, or attach an existing one with `doable server add`.
Real Docker image, not Lambda
Doable runs your code in real containers, not serverless functions. No 10-second timeouts, no cold starts, no "this works locally but not on Vercel" surprises. Long-running tasks, WebSockets, SSE — all just work.
Open MCP + CLI surface
Every Doable action has a CLI command and an MCP tool. Claude Code, Cursor, and Codex can deploy, debug, and fix from inside your editor — no Vercel-specific tooling required.
FAQ
Can I keep Vercel running while I migrate?
Yes. Both deploy from the same GitHub repo independently. Vercel keeps serving your primary domain until you flip DNS to Doable. Most teams run them in parallel for a week, validate, then cut over.
Will my Next.js App Router project work on Doable?
Yes. App Router, Server Components, Server Actions, middleware, ISR — all supported. Edge runtime functions deploy as standard Node (same code, no edge constraints).
What about Vercel Postgres / KV / Blob?
Migrate to Doable's addons (Postgres / Redis / object storage) with `doable addon migrate` — provisions + dumps + loads + atomic env var swap in one call. Or keep using Vercel's storage via its external connection string.
What about Vercel-specific things like Speed Insights / Web Analytics?
Doable has its own built-in analytics dashboard (Traefik-driven, per-project traffic / latency / status code breakdowns) — no per-request analytics billing. Vercel Speed Insights would need to be replaced with an external service (Plausible / Sentry / etc.) or removed.
Free hobby tier. Or try with any GitHub URL without signing up.