doable.do

Doable for v0

Deploy your v0 project anywhere, not just Vercel

v0 is brilliant for generating UI. Doable handles the part after: deploy your v0 project on managed cloud OR a Hetzner / DigitalOcean / Vultr / Linode VPS you provision in the same wizard. Same project, your infra, real production hosting.

From v0 to Doable in three steps

  1. 1

    In v0: kebab menu → Push to GitHub

    v0 creates a GitHub repo with your project. Subsequent v0 edits commit to the same repo.

  2. 2

    In Doable: New project → GitHub → pick the repo

    Tag it 'Imported from v0' in the wizard. Doable detects Next.js automatically; pick a runtime override if you've changed the stack.

  3. 3

    Live URL outside Vercel

    Deploy to Doable Cloud or a BYO server. Every v0-driven push to GitHub triggers a Doable build; your live URL is on doable.do (or your custom domain), not vercel.app.

The new-project wizard at /projects/new walks you through this end-to-end with a step-by-step guide for v0.

Why deploy v0 projects through Doable

Not Vercel

v0 nudges you toward Vercel. Doable runs the same project on infra you choose — managed cloud or any VPS — with predictable pricing, no per-invocation function billing, no usage-based surprises.

BYO VPS in one click

Provision Hetzner, DigitalOcean, Vultr, or Linode from inside Doable's wizard. cloud-init installs the agent + default hardening (UFW, fail2ban, swap, sysctl) on first boot.

Real Docker image, zero lock-in

Doable builds a real container image. Outgrow us? `docker pull` and run it anywhere — the same image works on AWS ECS, Fly.io, or a raw VPS with `docker run`.

Database addons + env vars

One-click Postgres / Redis / MongoDB on your own infra. Encrypted env vars, never visible after save. Production-ready before the v0 export hits Vercel's free tier limits.

FAQ

Does v0's "Push to Vercel" button still work if I deploy on Doable?

Yes — they're independent. You can keep deploying to Vercel from v0 AND deploy to Doable from the same GitHub repo. Most users pick one as primary and use the other for previews.

My v0 project uses Next.js App Router — does Doable run that?

Yes. Doable's Next.js runtime supports App Router, Server Components, Server Actions, middleware, and ISR. Edge runtime functions deploy as standard Node functions (with the same code).

What about Vercel-only features like Vercel KV or Vercel Postgres?

Swap them for Doable's native addon Postgres / Redis — one CLI call: `doable addon attach postgres`. Or keep using Vercel KV via its external connection string in an env var.

Is this just a Vercel clone?

No. Doable Cloud is managed hosting like Vercel, but BYO is the differentiator: the same Doable interface deploys to a VPS you own, with the same auto-build, auto-HTTPS, auto-domain flow. No other PaaS gives you that without two completely separate workflows.

Start a project from v0

Free hobby tier. Or try with any GitHub URL without signing up.