Do you actually own your v0 site?

The short answer

Yes, more completely than with most builders, because v0 doesn’t hold the site itself. A v0 account is a Vercel account, and the first time a v0 chat deploys, it creates an ordinary Vercel project in your own team or personal scope: the hosting, the domains, the environment variables and the rollbacks are yours from the first day. The code goes to a GitHub repository under whichever account or organization you choose, where v0 works on branches and merges pull requests rather than editing your main branch. Vercel’s documentation says it doesn’t own the code generated from your prompts. What’s left to check is who owns the Vercel team, which Marketplace integrations are billed through it, and whether the repository, not the chat, is the thing everything deploys from.

A v0 project with GitHub connected treats the repository as the source of truth for the code, and the Vercel project it deploys to is a standard Vercel project that can also deploy straight from that repository. That makes both the code and the hosting yours. It does not, by itself, move any database or storage the project added through the Vercel Marketplace, which belong to the Vercel team and are billed there.

What you should own

What v0 and Vercel control by default

• The Vercel project is created automatically on first deploy, in your scope. Custom domains, build settings and rollbacks are managed in the Vercel dashboard, not in v0.
• The repository is created when you connect GitHub, under the Git Scope you pick. Without GitHub, v0 deploys the chat’s code directly to the Vercel project, and the chat’s sandbox is temporary working space, not a backup.
• Environment variables live on the Vercel project. v0’s preview can only read the Development environment, so production secrets never reach it. Production values added through Vercel’s tooling are sensitive by default, meaning they can’t be read back; keep your own list of what each is.
• Integrations are provisioned through the Vercel Marketplace into your team, with billing through Vercel. Old “Vercel Postgres” databases became Neon in December 2024.
• Plans. v0 is Free, Plus or Business (Premium is being sunset). A v0 team plan can require a Vercel Pro subscription as well, and downgrading a Vercel team to Hobby removes its other members.

How to make the site portable

1. Connect GitHub from the project menu, Settings, GitHub, choosing your own account or organization as the Git Scope. Check the repository owner afterwards.
2. Confirm the Vercel project is in a team you own. Click “Inspect on Vercel” from a deployment. If a freelancer built it in their team, v0 can transfer the chat and its Vercel project to another scope, or Vercel can transfer the project alone; both require the current team owner to act.
3. Check that Git deploys. The Vercel project and v0 share the same repository connection, so a commit to the production branch should deploy on its own. Make one outside v0 and watch it.
4. List the environment variables on the Vercel project, and note which came from integrations.
5. Note each integration’s export path: a Neon database dumps and restores like any Postgres; Supabase has its usual exports; Blob files list and download through the SDK.

That’s most of it. Leaving Vercel as well is an ordinary host move from the same repository; the details are in moving a v0 site to GitHub and your own hosting.

What may not move automatically

• Integrations, on a project transfer. Moving a Vercel project between teams carries deployments, variables and domains but not Marketplace integrations, which must be moved separately and need the same integration installed on the destination team first.
• Vercel Connect credentials, which are short-lived tokens that never appear as environment variables.
• Marketplace billing, which stays with Vercel. Resources can be moved between your own Vercel teams; whether one can be moved out to the provider’s own account isn’t documented, so plan on an export and re-import if you ever leave Vercel entirely.
• The chat. The conversation and sandbox aren’t part of the site; the repository is.

What happens if you stop using v0

What the documentation says, and only that; the cancellation guide compares all four builders.

• Cancelling a v0 plan moves the account to Free at the end of the billing period. Purchased credits remain but need an active paid plan to use.
• The repository and the Vercel project are ordinary GitHub and Vercel resources; nothing in v0’s documentation says they’re removed when a v0 plan lapses, and there’s no documented v0-side disconnect because none is needed.
• Deleting the connected GitHub repository may make the code unrecoverable, because v0 treats it as the source of truth.
• Vercel Hobby is restricted to personal, non-commercial use and can’t deploy from a private repository in a GitHub organization.

v0’s pricing page lists GitHub sync and deploying to Vercel on the Free plan, so neither is lost when a paid plan ends. What we could not verify: what happens to the Vercel deployment itself is governed by the Vercel plan rather than by v0, and v0’s documentation says nothing about it beyond that.

Ownership checklist

The real test

For a v0 site with GitHub connected in your scope and the Vercel project in your team, yes, today: it’s a Next.js repository deploying to a Vercel project, which is the most ordinary setup on the web. Any tool can work on it; v0 itself keeps working alongside them. The portability test covers the remaining layers.

Sources

The rules and product behaviour described above were checked against these pages when the guide was last updated. If something here has changed, these are the places to look.

• FAQs: code ownership and the new v0 · v0
• GitHub · v0
• Import from GitHub · v0
• Vercel integration · v0
• Deployments · v0
• Custom domains · v0
• Databases and integrations · v0
• Vercel Connect · v0
• Sandbox · v0
• Teams · v0
• Pricing · v0
• vercel env · Vercel CLI
• Account · v0
• Changelog · v0
• Transferring projects · Vercel
• Product integrations · Vercel
• Vercel Postgres FAQ · Vercel
• Hobby plan · Vercel
• Deploying Git repositories with Vercel · Vercel