Lovable vs v0 by Vercel (2026)

Connectors sit in a single catalog, with Lovable handling authentication, credentials and requests. There are three connection types, app connectors, chat connectors and app user connectors, where each person using the published app connects their own account, and each connector's page says which types it supports.

About ninety integrations have their own pages, spanning Salesforce, HubSpot, Pipedrive and Zoho CRM, Snowflake, BigQuery, Databricks, Redshift, ClickHouse and Microsoft Fabric, Shopify, WooCommerce, PrestaShop and Lightspeed, Stripe, Chargebee, QuickBooks and Xero, Slack, Twilio, Telegram and Resend, Workday and Ashby, Aikido and Wiz, Notion, Airtable and Contentful, and AWS S3. An any API route, a create connector path, custom MCP servers and MCP registries cover anything not listed.

Sourcedocs.lovable.dev integrations introduction, app-connectors, chat-connectors, app-user-connectors, any-api, create-connector and integration catalogread 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

Build mode, formerly Agent mode, works on its own and takes a task end to end. It understands intent, explores the codebase for context, applies changes across files and resolves issues during development, with visible tasks showing progress and results reviewed before moving on.

Plan mode handles decisions, and the user can switch between the two at any time. Subagents are a separate feature, and cross project referencing lets one project draw on another. Skills apply reusable instructions, code mode and the project editor expose generated files for direct editing, and drafts and project history support iteration.

Sourcedocs.lovable.dev agent-mode, plan-mode, subagents, cross-project-referencing, skills, code-mode, projects/editor, drafts and projects/history 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

Lovable can check a project on a schedule, daily or weekly at a chosen time and optionally only after a minimum number of edits, reviewing the app code for broken functionality and recent visitor errors, then alerting by email and listing findings to fix in the project chat. So the builder agent wakes on a schedule without anyone asking. Other routes in are the web chat, a Slack app, mobile and desktop apps, a Telegram route, the Lovable API and the Lovable MCP server. Monitoring is in beta, on Pro, Business and Enterprise.

Sourcedocs.lovable.dev project-monitoring page and llms.txt indexread 2026-09-29

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

Knowledge holds persistent instructions and context for the agent, defined once and always included, at two levels. Workspace knowledge holds shared rules across all projects, such as coding standards, preferred libraries and naming conventions, and project knowledge holds the app's purpose, database schema, architecture decisions and domain terminology. Workspace knowledge is a text field, unlike Skills, which load on demand.

Project and workspace knowledge plus the customer's code and components are the main context sources, and Lovable does not describe reading instruction files from the repository or from outside sources. Design systems are Lovable projects that export reusable components, colors, fonts and styling rules, which other projects connect to and inherit, with immediate propagation, an order of precedence across several connected systems, and no versioning. Cross project referencing and about ninety integrations supply more material for each request.

Sourcedocs.lovable.dev features/knowledge, design systems FAQ and knowledge context-sources FAQread 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 are durable objects with a history page recording changes, drafts keep unfinished work, and project chat persists. A Knowledge feature holds project configuration, and cross project referencing lets one project draw on another. Build mode explores the codebase for context on each task instead of carrying learning between tasks, and skills apply reusable instructions the customer writes, which the agent does not update.

Sourcedocs.lovable.dev projects/history, drafts, projects/chat, knowledge, cross-project-referencing, agent-mode and skills 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 investigates the project and writes a plan the user reviews, edits and approves before any code is written, and Lovable says Plan mode never modifies code. It is one of three modes the user picks, and Build mode applies changes directly, so the approval sits in an optional mode, not in the build path. Project monitoring findings are fixed only when the user asks. Workspace admin controls, integration admin controls, groups and project visibility settings limit who can do what.

Sourcedocs.lovable.dev plan-mode and project-monitoring pagesread 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

Platform controls include a trust center, SAML single sign on, SCIM provisioning, two factor authentication, workspace identity and identity reuse, groups and people access controls, integration admin controls, project visibility settings and Enterprise audit logs.

Enterprise materials describe centralized identity, granular access controls and security oversight across the workspace. Business tier has a data opt out setting, and secrets and build secrets are kept separate from generated code.

Security scanning of the generated app is separate, through a security center, security insights, sensitive data scanning and Aikido and Wiz integrations.

Sourcedocs.lovable.dev trust-center, saml-sso, business/sso, business/scim, two-factor-authentication, workspace-identity, groups, people, admin-controls, business/data-opt-out and secrets pagesread 2026-08-31

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

Enterprise audit logs record actions taken by workspace members and which client each came from (Web, Desktop, iOS or Android), filterable by client or by member, with earlier entries marked Unknown. Dedicated pages cover project monitoring, logs, project usage, analytics and security insights. Build mode shows tasks as work proceeds, and project history records changes to a project. Audit logs are listed among Enterprise workspace capabilities, alongside security oversight across the workspace.

Sourcedocs.lovable.dev audit-logs, project-monitoring, logs, project-usage, analytics and security-insights pages, changelog and lovable-for-enterpriseread 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

A default hosting region is set in Settings, under Security and compliance, Privacy and security, choosing Americas, Europe or Asia Pacific. On Business and Enterprise workspaces, admins can require a default region for every new project, after which members cannot choose a different one, and existing projects keep their original region.

Country regions including Germany, Japan and United States East are available on Enterprise by request, and Enterprise materials list regional code hosting. Lovable Cloud hosts apps with custom, verified and transferable domains, and two way GitHub sync and external deployment guidance let the app be hosted elsewhere.

Sourcedocs.lovable.dev privacy-and-security-settings, cloud, hosting, custom-domain, github and external-deployment-hosting pages, lovable-for-enterpriseread 2026-08-31

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

Business tier includes design templates, alongside a managed registry, a remix path for starting from an existing project, a prompting library, skills with reusable instructions, and design systems supplying customer components. Video tutorials and an idea to app guide cover getting started. There is no catalog of finished apps published by Lovable.

Sourcedocs.lovable.dev business/design-templates, managed-registry, projects/remix, prompting-library, skills and design-systems pagesread 2026-08-31

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 builder has no model selection, model picker, bring your own key or provider setting, including in advanced settings, workspace admin settings and account settings. The model related integrations, Fireworks, Replicate, Perplexity and Gemini Enterprise, and an AI feature among the Cloud backend pages give model access to the app being built, not a choice over the model that powers Lovable.

Sourcedocs.lovable.dev sitemap inventory, advanced-settings, workspace-admin-settings, lovable-account-settings and features/ai pagesread 2026-08-31

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

Lovable has its own API and MCP server. Agent integrations turn a published Lovable app into an MCP server that ChatGPT, Claude and other assistants can use, with configurable tools, sign in, permissions and access. Custom MCP servers, MCP registries, a create connector path and an any API route cover other services. Two way Git sync with GitHub and GitLab, including self managed and dedicated GitLab, exports the full codebase, and desktop, mobile and Slack surfaces extend access to the platform.

Sourcedocs.lovable.dev lovable-api, lovable-mcp-server, agent-integrations, custom-mcp, mcp-registries, create-connector, any-api and git-sync-overview pagesread 2026-08-31

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

Browser testing has the platform use the customer's app in a real browser running in a virtual environment, clicking buttons, filling forms, navigating pages and checking real user behavior with screenshots across screen sizes. It returns a verdict.

A Details view shows the steps taken and summarizes what worked and what did not, and the pattern is reproduce, fix, then verify. Where test and live environments are turned on, it runs against the project preview in the test environment, so the check happens before the change reaches anyone. The check is Lovable's own, run against the customer's app before release.

Sourcedocs.lovable.dev browser-testing page and test-and-live-environments documentationread 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

Browser testing and the preview toolbar run and display the app the agent has built, which checks the agent's own output, not third party software. Firecrawl and Apify integrations retrieve web content over HTTP, which is scraping, not computer use. All outside actions run through connectors, the any API route, custom MCP servers or MCP registries, all programmatic interfaces. There is no browser navigation, form filling, screen control or computer use.

Sourcedocs.lovable.dev browser-testing, preview-toolbar, projects/preview, firecrawl and apify pages plus sitemap inventoryread 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