v0 Review 2026: Pricing, Git Workflow & Vercel Lock-in

Disclosure: CodeToolPilot may earn a commission if you buy through links on this page, at no extra cost to you. How we make money.

Last verified: October 12, 2026. This is an editorial research review — how we review. Prices and plans change often; confirm on the vendor’s site.

v0 is Vercel’s AI app builder. It started as a generator for React UI components and has grown into an agent that builds and edits full applications, runs them in a cloud sandbox and deploys them to Vercel. Since Vercel relaunched it in February 2026 as “the new v0”, its main audience has been product teams and engineers who want AI-built changes to flow through the same Git workflow as everything else.

For developers, the questions that matter are concrete. Where does the code live? How do changes reach production? Can you take the app off Vercel? And how do token-based credits translate into a monthly bill? This review answers those questions and looks at how v0 handles secrets and security for generated apps.

It is an editorial research review. It is based on v0’s documentation, pricing page and Vercel’s blog and security bulletins as of October 2026. We did not run hands-on tests.

Quick verdict

v0 has the most Git-native workflow of the major app builders. Each chat works on its own branch with its own preview deployment. Publishing merges a pull request and respects branch protections. You can also import existing GitHub repositories, so it is not limited to new projects. Vercel states plainly that it does not own the generated code. The trade-off is gravity toward Vercel: v0 accounts are Vercel accounts, publishing deploys to Vercel, and the default stack is Next.js with shadcn/ui. Token-based billing is transparent per model but hard to predict for a whole month.

Pro: Branch-per-chat workflow with preview deployments and PR-based publishing; v0 never pushes directly to main.
Pro: Imports existing GitHub repositories into a sandbox VM that detects Next.js, Vite and generic Node.js projects.
Pro: Published per-model token rates, with monthly credits that roll over for up to 65 days.
Pro: Secrets stay in Vercel environment variables, and v0 warns about client-exposed NEXT_PUBLIC_ variables.
Con: Publishing from v0 deploys only to Vercel; using another host means exporting the code.
Con: A strong bias toward Next.js, React, Tailwind CSS and shadcn/ui.
Con: Chat history and source files count as input tokens, so costs rise with context.
Con: Per-seat pricing, and training opt-out by default only from the $100 Business plan up.

Visit v0

What is v0?

v0 is built and run by Vercel and now lives at v0.app. Vercel’s FAQ says it uses “Next.js, React, TypeScript, Tailwind CSS, and shadcn/ui,” with particular expertise in Next.js. The February 2026 relaunch added a Git panel, a sandbox-based runtime that can import any GitHub repository, and secure connections to data sources such as Snowflake and AWS databases. In August 2026, Vercel made the v0 API generally available. It offers headless, programmatic access to the same app-building agent.

On ownership, the FAQ says “Vercel doesn’t own the code generated based on your queries and prompts.” It also warns that output may resemble other users’ output or third-party IP, and that evaluating it is your responsibility.

Key features

Branch-per-chat Git workflow

When you connect GitHub, v0 creates a private repository, and that repository “becomes the source of truth for your project’s code.” Each chat starts from a base branch. On its first change, v0 creates a working branch with its own preview deployment. Publishing creates or reuses a pull request, merges it and waits for the production deployment. If branch protections or required reviews block the merge, v0 leaves the pull request open for humans to finish. A Pull Changes option brings in new commits from the base branch.

Sandbox runtime and repository import

Each chat that needs one gets a Vercel Sandbox, a lightweight VM with a full Node.js environment. It detects Next.js, Vite and generic Node.js projects, supports pnpm, npm, yarn and bun, and has a terminal. A sandbox can run for at most 24 hours, and its network policy defaults to allow-all unless a team owner changes it. Importing an existing repository makes v0 usable on real codebases, not only greenfield prototypes.

Models and token-based credits

Usage is metered in tokens and converted into credits at per-model rates. Per million tokens, v0 Mini costs $0.20 for input and $1.20 for output, v0 Pro costs $2 and $10, and v0 Max costs $5 and $25. A faster Max variant costs $10 and $50. Chat history, source files and Vercel-specific context count as input, so long-running chats on large projects use more credits.

Design Mode, design systems and Figma

Design Mode, available on every plan, lets you adjust the interface visually. Design Systems 2.0 lets you import your own design system from GitHub repositories, Figma frames, docs or package archives. v0 builds a starter app for you to approve, then saves the design system as a skill it applies in future chats. On paid team plans, owners can set a team default. This is where v0’s UI-generation roots still show.

Integrations, MCP and the v0 API

v0 can install Vercel Marketplace integrations such as Neon, Supabase and Upstash, and connect to MCP servers. Integration environment variables are added to the linked Vercel project. The v0 API creates chats from prompts, streams progress and returns a preview running in a Vercel Sandbox, which lets platform teams embed v0 in their own tools.

Team features

Plus and Business seats each include $30 in monthly credits. A Shared Credit Pool kicks in once a member’s own credits run out. Teams can share chats and publish team-only templates. Enterprise adds role-based access with Builder, Creator and Viewer roles, plus SAML SSO and audit logs. Viewers don’t count as paid seats.

Who should use v0

v0 suits teams already on Vercel and Next.js. It works well for engineering leads who want AI-generated changes to go through branches, previews and pull requests, and for platform teams that want to embed app generation through the v0 API.

Who should skip it

Skip v0 if you host on AWS, Google Cloud or your own infrastructure and want one-click deploys there, or if you build with Python, Ruby or JVM back ends. It is also a weak fit for solo builders who want a cheap flat-rate plan, given the 7-message Free tier and $30 per-seat Plus plan.

Strengths and limitations

Strengths

The Git integration fits how engineering teams already work. AI changes arrive as branches with preview URLs and pull requests, existing CI and branch protections still apply, and required reviews stay with humans in GitHub. That makes v0 one of the few app builders where a tech lead can let designers and product managers ship small changes without bypassing review.

Secrets handling is sensible for generated code. Environment variables come from the connected Vercel project. Sensitive variables are not available to v0 previews. And v0 warns when a key is about to be exposed through a NEXT_PUBLIC_ prefix, a common mistake in AI-generated Next.js code. The published per-model token rates also let teams switch to a cheaper model for routine edits.

Limitations

v0 is designed around Vercel. Publishing creates a Vercel project and deploys there, and custom domains come from your Vercel team. The FAQ confirms you can export code and deploy elsewhere, but environment variables, previews and deployments work best with a Vercel project. Teams on other clouds will lose much of what makes v0 attractive.

Framework freedom is limited. The sandbox can run Vite and Node.js projects, but v0’s generation is tuned for Next.js with shadcn/ui. Billing is also less predictable than a flat plan. Context counts as input tokens, and some users have publicly reported spending credits much faster than expected after the move to token billing.

Platform security deserves attention too. In April 2026, Vercel disclosed that an attacker who got in through a compromised third-party AI tool had decrypted some customers’ non-sensitive environment variables. The bulletin does not mention v0. Still, because v0 stores app secrets as Vercel environment variables, follow Vercel’s advice: mark secrets as sensitive, rotate exposed keys and enable MFA. Data-use defaults matter as well. Only Business and Enterprise list training opt-out by default.

Pricing (as of October 2026)

Plan	Price	What you get
Free	$0	7 messages per day; $5 in one-time credits for new users; deploy to Vercel, Design Mode and GitHub sync
Plus	$30 per user/month	$30 monthly credits per user plus $2 in free daily credits on login; all models; shared team credit purchases; centralized billing on vercel.com; chat sharing
Business	$100 per user/month	Everything in Plus (same $30 monthly credits per user), with training opt-out by default
Enterprise	Custom	Data never used for training, SAML SSO, role-based access control, priority access and support SLAs

The older $20 Premium plan is being phased out and is closed to new users. Unused monthly credits roll over and expire after 65 days, and purchased credits expire one year after purchase. The v0 docs also note that a Vercel Pro subscription does not add v0 features, and that Vercel project and deployment limits can affect v0 use. Confirm current plans and model rates on v0’s pricing page.

See v0 pricing

Prices verified on October 12, 2026 against the official v0 pricing page. Plans change often — confirm on the vendor’s page before you buy.

Use cases

v0 works best for teams that already deploy on Vercel and want AI-generated changes to follow their normal Git review. These scenarios follow v0’s documentation, and each one notes the caveat a developer should weigh.

Letting designers and PMs ship UI changes through review

A tech lead can give designers and product managers access to a connected repository in v0, where each chat works on its own branch with a preview deployment and publishing goes through a pull request. If branch protections or required reviews block the merge, v0 leaves the pull request open for a developer to finish. This keeps CI and human review in place, but it assumes the app is deployed through a Vercel project.

Adding features to an existing codebase

v0 can import an existing GitHub repository into a Vercel Sandbox that detects Next.js, Vite and generic Node.js projects, so it is not limited to greenfield prototypes. A developer can use it for a well-scoped feature and use Pull Changes to bring in new commits from the base branch as the team moves on. Sandboxes run for at most 24 hours, and their network policy defaults to allow-all unless a team owner changes it, so security-conscious teams should review that setting first.

Building on a company design system

Front-end teams can import their design system from GitHub repositories, Figma frames, docs or package archives with Design Systems 2.0, and v0 saves it as a skill it applies in future chats. On paid team plans, owners can set it as the team default so new apps start on-brand. In our assessment, a design system built on a very different stack will need more correction, since v0’s generation is tuned for React, Tailwind CSS and shadcn/ui.

Embedding app generation in an internal platform

Platform teams can use the v0 API, generally available since August 2026, to create chats from prompts, stream progress and get back a preview running in a Vercel Sandbox. That makes it possible to offer a “describe the tool you need” flow inside an existing developer portal. Usage is metered in tokens at per-model rates, and chat history and source files count as input, so estimate costs before opening it to a wide audience.

Data-backed internal dashboards

Teams can install Vercel Marketplace integrations such as Neon, Supabase or Upstash from v0, or use the secure connections to sources like Snowflake and AWS databases added in the February 2026 relaunch. Integration environment variables land in the linked Vercel project, and sensitive variables are not available to v0 previews. Vercel’s April 2026 security bulletin, which does not mention v0, reported that some customers’ non-sensitive environment variables were decrypted, so mark secrets as sensitive and rotate any exposed keys.

Alternatives

Bolt.new: two-way GitHub sync with its own hosting and database, plus a Netlify option.
Lovable: a full-stack builder with a built-in Supabase-based backend and Git sync on every plan.
Replit: a general-purpose cloud workspace and agent with many languages and several deployment types.
Cursor: for developers who prefer AI assistance inside their own editor and repository.

Final verdict

v0 is the most engineering-friendly app builder for teams that already deploy Next.js on Vercel. Branches, previews and pull requests keep AI-generated code inside normal review, and Vercel clearly disclaims ownership of the output. If you are not on Vercel, or you need a different stack or a predictable flat bill, its advantages shrink quickly.

Try v0

FAQ

Is v0 free?

Yes, within limits. The Free plan allows 7 messages per day, gives new users one-time credits, and includes deploying to Vercel, Design Mode and GitHub sync. Paid plans are priced per seat and add monthly credits and access to all models. Check v0’s pricing page for current plans and per-model token rates.

Can I deploy a v0 app outside Vercel?

Yes, but not from v0 itself. Publishing from v0 creates a Vercel project and deploys there, while v0’s FAQ says you can still export the code and deploy elsewhere. Environment variables, previews and deployments work best with a Vercel project, so teams on other clouds lose much of v0’s workflow.

Who owns the code v0 generates?

v0’s FAQ says “Vercel doesn’t own the code generated based on your queries and prompts.” It also warns that output may resemble other users’ output or third-party IP and may contain bugs, and that evaluating it is your responsibility. As guidance, put generated code through the same license and security review as any outside contribution.

Does v0 only work with Next.js?

No, but it is tuned for it. v0’s FAQ says v0 uses Next.js, React, TypeScript, Tailwind CSS and shadcn/ui, while the sandbox can also detect and run Vite and generic Node.js projects with pnpm, npm, yarn or bun. It is not built for Python, Ruby or JVM back ends; for those, Replit supports many more languages.

Does v0 use my code to train AI models?

It can, depending on your plan and settings. v0’s FAQ says prompts and content may be used to improve its models, except Enterprise content and content from customers who have opted out of model training in their Vercel settings, and Vercel’s AI policy says the opt-out can be changed at any time in Team Settings. The v0 pricing page lists training opt-out by default on Business and says Enterprise data is never used for training, so Free and Plus users should check their team setting.

v0 vs Bolt.new or Lovable: which is best for developers?

v0 has the most Git-native workflow of the three, with a branch, preview and pull request per chat, but it publishes only to Vercel and leans heavily on Next.js. Bolt.new offers two-way GitHub sync with its own hosting and a Netlify option, and Lovable bundles a managed backend with database, auth, storage and functions, plus Git sync on every plan. In our assessment, v0 is the natural pick for teams already on Vercel, while Bolt.new and Lovable suit teams that want hosting and a database bundled in.

v0 Review (2026): Is Vercel’s AI App Builder Right for Your Team?