StackBlitz Bolt vs v0 by Vercel (2026)

Connectors run on MCP with eight shipping built in, Notion, Linear, GitHub, Miro, Sentry, Context7, Granola and Jira, authenticated by API key or sign-in, and any tool with a remote MCP server can be added as a custom connector. Each connector's individual actions of read, create, edit and delete can be toggled for granular access control.

First party integrations cover Figma and Google Stitch for design, GitHub for version control with organization access controls, Netlify and built-in Bolt hosting for deployment, Stripe for payments, Supabase and Bolt Database for data, Expo for mobile app store publishing, and Google SSO for authentication, plus a project import path from Lovable.

Sourcebolt.new Connectors announcement and support.bolt.new integrations sectionread 2026-08-31

GitHub integration covers repository import, sync, branch creation and pull requests directly from chat, with environment variable import and one-click deployment to Vercel. Database and data platform connections include Supabase, Snowflake and Amazon services, designs import from Figma, and generation draws on the shadcn component registry, screenshots and attachments.

Vercel Connect adds scoped integrations for Slack, GitHub, Snowflake, Salesforce, Notion and Linear with any other service addable via OAuth or API, spanning chat, source control, data warehouse, CRM, documents and ticketing. The Platform API wraps the whole lifecycle for embedding into external tools, bots and pipelines.

SourceShip 2026 announcement 2026-06-17 and vercel.com/blog/build-your-own-ai-app-builder-with-the-v0-platform-api; businesswire.com/news/home/20260617093685/en/vercel-brings-new-agent-framework-full-stack-capabilities-and-enterprise-controls-to-its-agentic-infrastructure-platformread 2026-08-30

A project moves from prompt through to published app, with Code View exposing the generated files for direct editing. Plan Mode separates planning from code generation as an explicit phase. Skills apply reusable rules and workflows during planning or building, and a Prompt Library saves prompts for reuse alongside built-in prompts for common tasks.

Project context can be actively managed to control the context window, chat tools allow selecting UI elements, tagging files and queueing prompts, and backups and version history allow restoring an earlier point. Generation runs across multiple files inside an in-browser Node runtime with package installation and a live dev server.

Sourcesupport.bolt.new project-lifecycle, plan-mode, skills, prompt-library, code-view, chat-tools and manage-context pagesread 2026-08-31

Work in v0 is delegated to subagents, which draw on v0 credits along with other supporting agent work even when a ChatGPT plan covers the main responses. Its sandboxes ship pre-installed coding agents such as Claude Code that run inside the project, routed through the AI Gateway under the team's model rules. Within a chat the agent plans, generates, runs a live dev server, opens branches and pull requests and deploys.

Sourcev0.app/docs (ChatGPT plan, pre-installed agents, agentic features)read 2026-09-29

Users start work in the chatbox of the web application, with chat tools for selecting UI elements, tagging files and queueing prompts. Projects can start from a blank prompt, uploaded files, a Figma or Google Stitch design, or a team template, or be imported from Lovable, and each of these starts a build by hand. Collaborators can be invited to work on a project in real time. There is no scheduled, recurring, webhook or event driven trigger for starting a build.

Sourcesupport.bolt.new llms.txt index, chat-tools, start-project and collaborate pagesread 2026-08-31

Users reach v0 through the v0.app web application and its in-browser editor, and programmatically through the Platform API. Vercel positions the API for embedding app generation into external tools, bots, command line tools, customer systems and custom agents, with sync, async and streaming execution as separate endpoints for interactive UIs or background pipelines, and chats can start from a GitHub repository, which Vercel presents as a sign it wants v0 in CI/CD. There is no event trigger, scheduled run or inbound chat or ticketing channel.

Sourcevercel.com/blog/build-your-own-ai-app-builder-with-the-v0-platform-api and the v0 Platform API v2 betaread 2026-08-30

The customer's design system becomes a stored object Bolt builds from. Customers can add a design system so projects build using the company's UI guidelines and components, view and manage the generated system, start a project so Bolt builds with their real components from the first prompt, and keep the design system in sync when its sources change, with best practices guidance alongside.

The design system, built from the customer's own material, persists between runs. Knowledge is separately a managed object at account, workspace and project scope, with project knowledge set in project settings and shared knowledge held at workspace level. Files and images attach to a project as per-request context, and MCP connectors supply context from external tools and data.

Sourcesupport.bolt.new design system section including the sync page, account, workspace and project settings, upload files and connect-mcp pagesread 2026-08-31

Generation is grounded in context the customer supplies. A chat can start from a prompt, source code, a GitHub repository or a ZIP archive, and v0 can import an existing repository with its environment variables and work on it as well as creating new projects. Designs import from Figma, screenshots and attachments are accepted as multimodal input, and the shadcn component registry and design system conventions shape the structure of the output. There is no codebase index, retrieval layer, dependency graph or reasoning across files.

Sourcevercel.com/blog/build-your-own-ai-app-builder-with-the-v0-platform-api and vercel.com/blog/introducing-the-new-v0read 2026-08-30

Projects persist and can be viewed, organized and maintained over time. Backups, restore and version history allow returning a project to a previous point and are managed from the chat. Project knowledge, design systems and saved prompts persist as project and workspace configuration. Bolt advises actively managing project context and keeping it small for performance. Customers author Skills and Prompt Library entries, and the agent does not update them. Switching agents manually clears chat history.

Sourcesupport.bolt.new projects-files, rollback-backup, manage-context, skills and prompt-library pagesread 2026-08-31

Team Memories sit beside team skills in the workspace. Members with edit access, or only owners and selected members when an owner restricts it, create, edit and delete team memories that everyone on the team can view and use. Chats and projects persist and resume, and the agent keeps context of earlier actions within a conversation. The agent writes no memory of its own that lasts beyond the conversation.

Sourcev0.app/docs (team skills and Team Memories and Skills settings)read 2026-09-29

Plan Mode is an optional chat mode in which Bolt plans and answers questions without changing code, ending with quick actions such as Implement this plan that switch to Build Mode. The user chooses whether to use it, and Build Mode applies changes directly with no approval step. Connector actions can each be toggled, team admins control member roles, publishing, integrations and data exports, GitHub organization admins control which repositories Bolt can reach, and generation carries security constraints in its system prompts.

Sourcesupport.bolt.new plan-mode and team-settings pages, bolt.new/platform/securityread 2026-09-29

v0's terminal permission layer has three modes that persist across chats. In Ask mode the customer's allow, ask and deny rules apply, and v0 asks for confirmation on anything marked ask or unmatched. Auto, the default, runs a built-in allow list of read-only commands and asks before others it judges need it. Full skips the checks. MCP tool calls follow the same Ask, Auto or Full mode and Agent Permissions rules, which decide whether a call runs, asks for confirmation or is blocked. Work then lands as Git branches and pull requests with preview deployments.

Sourcev0.app/docs (Permission modes; MCP availability and approval)read 2026-09-29

Bolt is SOC 2 Type 2 certified and compliant with GDPR and CCPA, with audit reports and policies on a trust profile at trust.bolt.new, AES-256 encryption at rest and TLS 1.2 or higher in transit, continuous scanning and intrusion detection watched by a 24/7 security operations team, and annual independent penetration tests with report summaries on request.

Enterprise and Team customers under an MSA or DPA are excluded from model training. Teams adds team level access management and granular admin controls with user provisioning, and Enterprise adds SSO and audit logs. Team settings restrict roles, publishing, integrations and data exports to admins.

Sourcebolt.new/platform/security, bolt.new/pricing and support.bolt.new team-settingsread 2026-09-29

Vercel holds a SOC 2 Type 2 attestation for Security, Confidentiality and Availability, and v0 is in the scope of that report, with details at security.vercel.com. Its controls include SAML SSO on Enterprise, directory sync groups (for example Okta SCIM) mapped to Access Groups, v0 roles separate from Vercel deployment roles, team-owner control over who may edit team memories and skills, owner acceptance before custom models can be used, pre-installed agents disabled by default on Enterprise, and data opt-out on Business and Enterprise.

Sourcev0.app/docs (security and enterprise sections)read 2026-09-29

Backups, restore and version history let a project be returned to a previous point, managed from the chat. GitHub integration syncs commits automatically and works across branches, providing an external record of changes. Hosting analytics show engagement with a published project, and database logs are available for the generated app's database. Team settings include data exports. There is no agent level run trace or tool call record, and troubleshooting relies on issue specific guidance rather than inspecting a run.

Sourcesupport.bolt.new rollback-backup, git, hosting analytics, database logs, team-settings and llms.txt indexread 2026-08-31

Vercel Connect carries full audit trails for each agent session's scoped token use, enterprise tiers offer audit logs and advanced analytics, and Vercel Agent correlates incidents to the deployment that caused them using traffic, traces and alerts. On the v0 surface, Git branches and pull requests plus preview deployments give a durable record of what was generated and shipped, and chats persist for review. These record credential use, deployments and code changes, not a step by step trace of the agent's own reasoning, and v0 keeps no replayable session record.

SourceShip 2026 announcement 2026-06-17 and vercel.com/blog/introducing-the-new-v0; businesswire.com/news/home/20260617093685/en/vercel-brings-new-agent-framework-full-stack-capabilities-and-enterprise-controls-to-its-agentic-infrastructure-platformread 2026-08-30

BYOK deployment lets a customer run Bolt inside its own AWS or Azure tenant with full infrastructure isolation and no shared compute, meeting HIPAA, FedRAMP and SOC 2 requirements. Development executes client-side in an isolated WebContainer in the browser. Bolt Cloud hosts published projects at bolt.host or a connected domain, Netlify and Expo are alternative targets, GitHub sync exports the full codebase, and the bolt.diy fork runs locally.

Sourcebolt.new/platform/security, support.bolt.new hosting and git pagesread 2026-09-29

As a hosted service, v0 runs on Vercel's cloud. Generated code exports in full to a local machine or GitHub and deploys to Vercel, Business and Enterprise add data opt-out, and agent traffic stays with providers on Vercel's subprocessor list. There is no region list, customer environment or region selection for v0 itself. Vercel for Enterprise Apps and Agents can deploy inside a customer's own AWS account, but that covers the apps and agents customers deploy, and v0 generation is not said to run there.

Sourcev0.app/docs and vercel.com/blog/vercel-for-enterprise-apps-and-agentsread 2026-09-29

A Templates catalog at bolt.new/resources/templates offers working templates filterable by category (websites, apps, portfolio, SaaS, blog, internal tools, editorial, ecommerce, travel, finance, real estate), each named, previewable and opened in Bolt with one click, among them a retail dashboard, a pooled analytics dashboard, a personal finance tracker, a SaaS landing page and dashboard, and a social media posting and analytics platform. Team templates skip repetitive project setup, the Prompt Library supplies built-in prompts, and skills add reusable rules and workflows.

Sourcebolt.new/resources/templates, support.bolt.new team-templates, prompt-library and skillsread 2026-09-29

Generation draws on the shadcn component registry as a library of reusable, accessible React components, with design systems and project templates providing repeatable starting points, and the Platform API supports bring-your-own-context so teams can supply their own registries and conventions. Imported Figma designs act as further reusable inputs. v0 itself has no library of prebuilt agents, skills catalog, agent gallery or marketplace.

Sourcevercel.com/blog/introducing-the-new-v0 and vercel.com/blog/build-your-own-ai-app-builder-with-the-v0-platform-apiread 2026-08-30

The customer can pick the model in one of Bolt's three agents. In Bolt Forge the customer selects among open-source models from several makers, GLM 5.3 and GLM 5.3 Flash, Kimi K3 and DeepSeek v4 Pro, with new open models added as released. The Standard and Max agents run on proprietary models with model selection handled behind the scenes.

Forge is included with every individual Pro plan and offered through a $9 Lite plan by waitlist. It is not available on Teams or Enterprise. It is a research preview for a limited period, and Bolt has not said whether it continues after that. The open-source bolt.diy fork supports customer API keys across OpenAI, Anthropic, Ollama, Gemini and LMStudio.

Sourcesupport.bolt.new bolt-forge and agents pagesread 2026-09-29

A model picker in the chat composer lets users choose v0's own models or add custom models from the Vercel AI Gateway catalog, searched by model or provider, with reasoning effort and fast mode per model. On Enterprise, custom models unlock once a team owner allows them. Users can also connect a ChatGPT Plus or Pro plan to cover eligible responses from OpenAI models.

Sourcev0.app/docs (Choose a model, Add custom models, Enterprise model access)read 2026-09-29

There is no API, SDK or first party MCP server for driving Bolt itself, and the API reference section has been removed from the documentation. Bolt does offer two way GitHub integration that backs up a project and syncs commits across branches with full codebase export, MCP connectors through which Bolt calls out, and the open-source bolt.diy fork maintained by StackBlitz Labs, which customers can modify and run locally.

Sourcesupport.bolt.new llms.txt, git and connect-mcp pagesread 2026-09-29

The v0 Platform API gives programmatic access to the app generation pipeline through RESTful endpoints and a TypeScript SDK, covering creation and management of chats and projects.

The v2 public beta exposes the full app-building agent, not just a code endpoint, with VM-backed chats startable from a prompt, a GitHub repository or a ZIP archive, live dev server previews, follow-up messages, integrations and programmatic deployment to Vercel, and three execution modes offered as separate sync, async and streaming endpoints.

Vercel describes third parties building their own app builders, bots, command line tools and agents on it, and positions it for CI/CD pipelines. There is no MCP server.

Sourcevercel.com/changelog/v0-platform-api-now-in-beta and vercel.com/blog/build-your-own-ai-app-builder-with-the-v0-platform-apiread 2026-08-30

A project security check finds and fixes security problems in a generated project. A live preview renders the running application during development, backups and restore return a project to an earlier point, and GitHub branch support isolates changes. Dedicated troubleshooting pages cover Bolt issues, preview issues, publish issues, integrations issues and login issues. Token efficiency and context management guidance address build cost and reliability. There is no test generation, regression suite, scoring or evaluation comparing builds.

Sourcesupport.bolt.new security, rollback-backup, troubleshooting section, maximizing-token-efficiency and llms.txt indexread 2026-08-31

v0 generates code and runs it in a sandbox with live previews and a real dev server, so a person can see the application working before shipping, but there is no test generation, test execution, assertion, static analysis, evaluation harness or code quality engine. Evaluation is built into Vercel's separate eve agent framework, and Vercel Agent investigates production incidents, but neither is exposed through v0.

Sourcevercel.com/blog/introducing-the-new-v0 and v0.appread 2026-08-30

Bolt executes builds in StackBlitz WebContainers, a Node runtime with filesystem, package manager and dev server running client-side in the browser tab. The live preview renders the application the agent has generated for human inspection. External systems are reached through MCP connectors and API integrations. There is no browser navigation, form filling, screen control or computer use.

Sourcesupport.bolt.new intro-bolt, preview-issues, connect-mcp pages and llms.txt indexread 2026-08-31

Execution runs through programmatic surfaces throughout, namely a full-stack sandbox and, since v2, VM-backed chats running a real dev server with file operations, server actions and database connections, the GitHub API for branches and pull requests, and Vercel deployment APIs. Live previews render the generated application for a person to look at, not for the agent to operate. There is no browser control, screenshot capture, visual verification or way to operate software without a programmatic interface.

Sourcevercel.com/blog/introducing-the-new-v0 and the v0 Platform API v2 betaread 2026-08-30