# Rush vs v0

v0 and Rush both have an API and both open pull requests. v0 is built for Vercel web apps; Rush is built for any task on any repository it can reach.

Facts checked 17 October 2026. Prices and limits move. Read the citations.

**The short answer.** Pick v0 for web UIs that publish to Vercel. Pick Rush for agent work on any GitHub repository, ending in a pull request, a report or files.

## The useful distinction

v0: Vercel's AI app builder. It generates full-stack web apps from prompts, pushes to GitHub working branches, publishes to Vercel through pull requests, and has an API and an MCP server.

An app builder owns the editor, the hosting and often the database. Rush owns none of those. It fits once the code lives in a GitHub repository and the next change should come back as a pull request.

## Buyer questions

| Question | Rush | v0 |
| --- | --- | --- |
| What runs | Claude Code, Codex or OpenCode, the vendors' own CLIs, or a saved agent built on one. | v0's own models (v0-mini, v0-pro, v0-max); Enterprise can add AI Gateway models. |
| Isolation | One E2B microVM per run with its own disk, memory, desktop and browser. It parks between turns and is removed on cancel or after 7 idle days. | Secure live previews; deploys to Vercel. |
| Result and pull request | A run on a repository works on its own branch and opens the pull request; a run whose checks fail ends needs_review, not completed. Reports and files come back as artifacts. | Creates a working branch for each change. Publish opens or reuses a pull request, merges it and waits for the production deploy; branch protection still applies. Fix Build and Fix CI in the branch menu. |
| MCP | Rush is an MCP server at api.prix.dev/mcp with 18 tools. A run also takes MCP servers by connection or inline. | Bring-your-own MCP servers for tools during generation, and a v0 MCP server at parity with the v0 API. |
| Team | Everyone in the org sees the same Projects and runs, with who started each. Automations start runs from GitHub events, schedules, webhooks and Linear. | Shared chats; Plus members have Builder access. Team members need access to the GitHub repository. RBAC on Enterprise. |
| Starting price | Free 5 agent-hours / month; Pro $20; Team $200 | Free with 7 messages a day; Plus $30 / user / month |
| Where it taps out | Three harnesses. Repositories through the GitHub App only. No self-host or customer VPC. A key runs 4 at once by default, up to 100. | Free is 7 messages a day. Generation pauses when credits run out. Deploys only to Vercel. Web apps are the target. |

## When each side wins

### Rush wins when

- The repository is not a Vercel web app, or the result is a report or files rather than a deploy.
- The agent is Claude Code, Codex or OpenCode, on your own model account.
- Runs keep a machine with a browser and a desktop, and park between turns.

### v0 wins when

- Preview deployments per working branch and one-click publish on Vercel.
- Design Mode and design systems for UI work.
- An embeddable React SDK for putting a builder inside your own product.

## Where Rush sits

v0's API builds apps; Rush's API does tasks. POST /o/{org}/sessions sends Claude Code, Codex or OpenCode into its own microVM, on a repository or none, and returns the pull request or the artifacts.

## Skip Rush if

- Rush runs three agents: Claude Code, Codex and OpenCode. It does not host an agent you wrote yourself.
- Repositories come through the Rush GitHub App. A GitLab or Bitbucket repository cannot be a run's repository yet.
- There is no self-hosted or customer-VPC deployment, and we do not publish a compliance report today.
- Compute is metered. Free includes 5 agent-hours a month and Pro 40, each with a weekly ceiling.
- You review the pull request. Rush does not merge for you.

## Questions people actually ask

### Does v0 have an API?

Yes. v0's docs say the v0 API gives your product v0's app-building agent, with code generation, live previews and deployment to Vercel, starting with v0.chats.create.

### Can I move from v0 to Rush?

There is nothing to migrate: v0 already makes the GitHub repository the source of truth. Install the Rush GitHub App on it and keep v0 for UI work.

### Does Rush need my own model account?

By default a run uses your own Claude or ChatGPT subscription or API key, and your provider bills the model calls. Rush meters the sandbox compute against your plan, and parked time is free.

## Keep reading

- [v0 alternatives](https://getrush.ai/compare/v0-alternatives.md)
- [v0 vs Lovable](https://getrush.ai/compare/v0-vs-lovable.md)
- [v0 vs Replit Agent](https://getrush.ai/compare/v0-vs-replit.md)

## Sources

1. Rush, "Rush product requirements", retrieved 2026-09-15. https://getrush.ai/cloud
2. Rush, "Rush pricing (live contract on getrush.ai)", retrieved 2026-09-15. https://getrush.ai/pricing
3. Rush, "Isolation, plainly", retrieved 2026-10-17. https://getrush.ai/docs/concepts/isolation
4. Rush, "Results and proof", retrieved 2026-10-17. https://getrush.ai/docs/concepts/results-and-proof
5. Rush, "Usage and billing", retrieved 2026-10-17. https://getrush.ai/docs/concepts/usage-and-billing
6. Rush, "Rush MCP server", retrieved 2026-10-17. https://getrush.ai/docs/concepts/mcp-server
7. Rush, "Automations", retrieved 2026-10-17. https://getrush.ai/docs/concepts/automations
8. Vercel, "Plans and Pricing", retrieved 2026-10-17. https://v0.app/pricing
9. Vercel, "Pricing (docs)", retrieved 2026-10-17. https://v0.app/docs/pricing
10. Vercel, "GitHub", retrieved 2026-10-17. https://v0.app/docs/github
11. Vercel, "Deployments", retrieved 2026-10-17. https://v0.app/docs/deployments
12. Vercel, "Teams", retrieved 2026-10-17. https://v0.app/docs/teams
13. Vercel, "MCP Integrations", retrieved 2026-10-17. https://v0.app/docs/MCP
14. Vercel, "Use v0 from an MCP Client", retrieved 2026-10-17. https://v0.app/docs/api/v2/guides/mcp-server
15. Vercel, "v0 API", retrieved 2026-10-17. https://v0.app/docs/api/v2
16. Vercel, "Create chat", retrieved 2026-10-17. https://v0.app/docs/api/v2/reference/chats/create-chat