Why Vercel v0 owns the Next.js scaffold market — Q2 share.

The deploy-funnel economics that determined the share concentration

The structural advantage Vercel built around v0 is not the scaffold quality at generation time — by any reasonable measure, the four platforms produce technically comparable Next.js scaffolds in the easy-to-medium complexity range — but the deploy funnel that v0 anchors to Vercel's own deployment infrastructure. A developer who generates a scaffold in v0 sees a one-click deployment to a Vercel production URL within the same UI session. A developer who generates a scaffold in Bolt, Lovable, or Replit Agent sees a deployment that requires either exporting the code to a separate repository and connecting it to a deployment platform or accepting the platform's own hosting (StackBlitz, Lovable's hosting layer, Replit's deployment surface). The friction differential between the in-platform Vercel deploy and the export-then-deploy alternative is the single largest factor in the share concentration v0 has achieved. The deploy-funnel data Vercel publishes shows that 78 per cent of v0-generated applications that reach production stay deployed on Vercel; only 11 per cent migrate to an alternative hosting platform within 90 days of generation. The remaining 11 per cent are abandoned before reaching sustained production.

The economic implication of the deploy-funnel retention is that each v0 application that reaches production produces ongoing Vercel hosting revenue for the lifetime of the application, which for the median scaffold-originated application is approximately 14 months before either substantial abandonment or migration to alternative infrastructure. The lifetime revenue per v0-generated production application that Vercel's investor data has implied — between $340 and $620 depending on the application's compute and edge-network usage profile — is the structural compounding that justifies v0's pricing strategy at the generation tier. Vercel's free tier for v0 is more permissive than the equivalent free tier any of the competing platforms offers, and the strategic logic is that the funnel economics work even at zero generation revenue if the resulting Vercel deploy retention holds at the present rate. The data through Q2 2026 supports the strategic logic. The competing platforms do not have the equivalent deploy funnel to anchor against, and their pricing strategies have had to recover more revenue at the generation tier to fund the engineering investment required to compete on scaffold quality.

Bolt's deploy-funnel economics tell a less favourable story. StackBlitz, the company behind Bolt, operates a WebContainer technology that runs the Bolt environment entirely in the browser. The technical achievement is meaningful — the WebContainer execution model is genuinely innovative — but the deploy funnel from a Bolt-generated application to production is more friction-heavy than v0's because the developer must either continue running in the StackBlitz hosting environment (which is less mature for production workloads than Vercel) or export to a separate deployment platform. The export-to-Vercel option is well-supported and a substantial portion of Bolt-generated applications that reach production do so via Vercel deployment, which counterintuitively benefits Vercel's broader Next.js share even when Vercel does not own the scaffold generation. The structural position is that Bolt's product strategy depends on either StackBlitz's hosting maturing to a level that competes with Vercel for production workloads or on the company accepting that a portion of its scaffold generation funnel will export to a competitor's platform. Neither option is straightforward.

Lovable's strategy has been more direct in its bet on owning the full funnel. The Stockholm team has invested in its own hosting and deployment layer with the explicit positioning that a Lovable user should not need to leave the platform from generation through production. The strategy is coherent but expensive — building deployment infrastructure that competes with Vercel and Netlify on the production workload tier is a capital-intensive proposition — and the share data through Q2 2026 suggests that the strategy has not produced the funnel-retention advantage that would justify the infrastructure investment. Lovable's deploy retention to its own hosting layer is approximately 41 per cent of generated applications, below Vercel's 78 per cent and meaningfully below the level required to amortise the infrastructure investment at the company's present generation volume. The strategic question for the Lovable team through 2026 H2 is whether the deploy retention improves materially or whether the infrastructure investment requires recalibration.

The Vercel AI SDK distribution effect that compounds the share advantage

The second structural advantage that v0's share has compounded around is the Vercel AI SDK, the open-source library that the Vercel developer experience team has positioned as the de facto interface for AI features in Next.js applications. The AI SDK's adoption trajectory through 2024, 2025, and into 2026 has produced a distribution surface that v0 leverages by default — applications that v0 generates with AI features use the Vercel AI SDK as the default integration layer, and developers who learn to build AI features through v0 implicitly learn to build them with the Vercel AI SDK. The downstream effect is that the developer's mental model for AI-feature integration in Next.js becomes Vercel-shaped, and the migration friction to a non-Vercel platform for AI-native applications becomes higher than the migration friction for non-AI applications.

The npm download data for the ai package — the Vercel AI SDK's canonical distribution — reflects the compounding. Weekly downloads on the package rose from approximately 1.1 million in May 2025 to approximately 4.3 million in May 2026, a 3.9× increase that outpaces the broader Next.js adoption trajectory. The growth is concentrated in two segments: applications generated through v0 that use the AI SDK as the default integration, and applications built independently by developers who have adopted the AI SDK as the canonical Next.js AI integration library after using it on v0-generated applications. The two segments compound one another — the v0 generation drives initial AI SDK adoption, which drives broader developer comfort with the AI SDK, which drives adoption on non-v0 projects, which strengthens the AI SDK's positioning as the Next.js AI standard. The flywheel is the structural advantage Vercel has built that the competing scaffold platforms cannot replicate by improving their scaffold generation alone.

The named Series B and above users that the AI SDK has accumulated provide qualitative evidence of the distribution position. Perplexity, the AI search company, uses the Vercel AI SDK as the primary streaming and tool-calling layer in its production application. Notion's AI features, which the company has been expanding through 2025 and 2026, lean substantially on the AI SDK for streaming responses and tool integration. Cohere's consumer-facing demo applications use the AI SDK. Linear's recently launched AI features use the AI SDK. The pattern is that the AI SDK has accumulated the distribution position that LangChain Inc. has positioned LangGraph to take in the Python ecosystem; the Vercel SDK is the JavaScript and TypeScript orchestration layer that production AI applications default to. The distribution position predates v0 and was built deliberately by the Vercel developer experience team through 2024, but v0 has been the channel that has compounded the distribution position in 2025 and 2026.

The competing scaffold platforms face an integration choice that none of them has resolved cleanly. Bolt, Lovable, and Replit Agent can either use the Vercel AI SDK as the default integration layer in the applications they generate — which strengthens Vercel's distribution position even as it serves the immediate need to produce a working AI feature — or they can use an alternative integration layer that the developer is less familiar with and that the broader Next.js community has less momentum behind. Bolt has effectively adopted the Vercel AI SDK as its default integration; Lovable uses a mix of the Vercel AI SDK and a custom layer; Replit Agent uses its own integration that is less compatible with the broader Next.js ecosystem. None of these choices is optimal for the competitive position, because the alternative-integration approach loses the developer-mental-model compatibility, and the Vercel-AI-SDK approach strengthens Vercel's broader position. The competing platforms are locked into a strategic choice that compounds Vercel's advantage in either direction.

Bolt, Lovable, Replit Agent: the competitive positions

Bolt's competitive position is the most technically interesting of the three. The WebContainer technology that powers Bolt is a substantive engineering achievement — running a Node.js environment entirely in the browser, with file system, package manager, and terminal emulation — and the developer experience the technology enables for scaffold generation is genuinely strong on the easy-to-medium complexity tier. Eric Simons, StackBlitz's CEO, has been explicit in public communication that the WebContainer is the company's foundational asset and that Bolt is the consumer-facing product that demonstrates the technology. The strategic question is whether the WebContainer's technical advantage compounds into a deploy funnel that competes with Vercel's, or whether Bolt remains a scaffold tool whose generated applications predominantly migrate to Vercel for production. The Q2 2026 data suggests the latter, but the data through Q4 2026 will be more diagnostic because StackBlitz has indicated that the company plans to invest more meaningfully in production hosting capabilities through H2 2026.

Lovable's competitive position is the most economically exposed. The Stockholm team has built a comprehensive product surface that covers generation, iteration, and deployment, with the explicit strategic position that the full funnel inside Lovable is the company's competitive moat. The product is mature and the developer experience is genuinely polished — Lovable's Q1 2026 Net Promoter Score among active users was 71, the highest among the four scaffold platforms in the segment. The economic exposure is that the Lovable hosting layer competes directly with Vercel and Netlify on the production workload tier, and the infrastructure investment to maintain that competition at scale is substantial. The Series A funding the company raised in early 2025 provides runway for the strategic experiment, but the funnel-retention data through Q2 2026 — 41 per cent retention to Lovable hosting — suggests that the strategy has not yet produced the economic compounding the team had projected. The Q3 2026 fundraising cycle that Lovable has signalled will be the data point that resolves whether the strategy continues or recalibrates.

Replit Agent's competitive position is the most strategically complicated. Amjad Masad's repositioning of Replit through 2025 — from a learning-and-collaboration platform to an AI-native build-and-deploy platform — has produced a product that competes in the scaffold market but that is also competing in the broader integrated-development-environment market that has its own distinct dynamics. The Q2 2026 share data shows Replit Agent at approximately 6 per cent of the Next.js scaffold market, which understates the platform's broader importance because Replit Agent's scaffold capabilities extend beyond Next.js into other application types where Replit's traditional strength applies. The strategic position is that Replit Agent's Next.js scaffold share is a narrow slice of the company's overall product surface, and the Q3 and Q4 2026 product roadmap that Masad has indicated will emphasise broader application types and deeper IDE integration rather than competing more aggressively for Next.js scaffold share specifically. The position is rational given the company's broader competitive context, but it cedes the specific Next.js scaffold segment to v0 in a way that the share data captures.

The fourth competitive position worth noting is the residual segment — direct Next.js create-app usage that does not pass through any AI-native scaffold platform. The residual share has fallen from approximately 47 per cent of new Next.js applications in May 2025 to approximately 8 per cent in May 2026, which is the structural finding that the AI-native scaffold market has produced. The developers who would have run npx create-next-app in 2024 are now predominantly generating their initial scaffold through v0, Bolt, Lovable, or Replit Agent. The shift represents an absorption of the entry-level scaffold workflow by AI-native platforms, and the implications for the broader Next.js community are substantial. The Next.js community's centre of gravity has moved partly toward the platforms that generate Next.js applications, and the platform that has captured the largest share of that generation — v0 — has gained corresponding influence on the Next.js ecosystem's direction.

The Series-B-and-above enterprise users that anchor the v0 share

The qualitative anchor for v0's share concentration is the set of named Series B and above users whose adoption signals to the broader market that v0 is the production-credible choice. The pattern is consistent with how enterprise tooling segments typically consolidate: the platforms that capture a small number of named, credible users early in the segment's maturation produce the social proof that the broader market relies on for its own selection decisions. Vercel's published case study set through Q1 and Q2 2026 includes named users in three categories that the company emphasises in its enterprise sales motion: AI-native consumer companies, B2B SaaS companies with significant front-end engineering investment, and enterprise marketing teams whose adoption of v0 represents a different buyer persona than the engineering-led adoption pattern.

The AI-native consumer category includes Perplexity, which has used v0 to scaffold several of its consumer-facing surfaces; Cohere, which has used v0 for its consumer demo applications; and a longer list of smaller AI-native companies whose product surfaces have been scaffolded through v0. The pattern in this category is that the developers building these companies are the developers who would have been earliest to adopt v0 in any case — they overlap substantially with the developer community that the Vercel developer experience team has built relationships with through 2023 and 2024 — and the adoption is a natural extension of the existing developer relationship rather than a substantive procurement decision. The strategic value is that the adoption pattern produces visible product surfaces that subsequent prospects can examine when evaluating v0 for their own use.

The B2B SaaS category is where the enterprise procurement dynamic has been most consequential. Notion, Linear, and several other Series C and above B2B SaaS companies have adopted v0 for specific internal use cases — marketing landing pages, internal tool prototyping, customer success dashboards — rather than for the core product engineering work. The pattern in this category is that v0 is being used as a productivity multiplier for the segment of the company's work that does not require deep customisation or production-critical engineering, and the buyer is increasingly the marketing or product operations function rather than the engineering function. The expansion into non-engineering buyers is the strategic development that Vercel's go-to-market team has been pursuing through 2025 and 2026, and the Q2 2026 share concentration suggests the strategy is working at a substantial scale.

The enterprise marketing category is the buyer persona that none of the competing scaffold platforms has produced a comparable foothold in. Vercel's go-to-market team has invested in selling v0 directly to marketing teams at large enterprises — financial services, retail, industrial — for use cases that previously would have required either a marketing-technology vendor purchase or a dedicated engineering team to support. The adoption pattern at this tier is slower than the AI-native or B2B SaaS adoption, because enterprise marketing procurement processes are longer and more compliance-heavy, but the Q2 2026 enterprise contract pipeline that Vercel has indicated represents a meaningful future revenue stream that the present share data does not yet fully reflect. The strategic positioning is that v0 is becoming a tool that produces value across the engineering and marketing boundary, and the buyer persona expansion is the dimension of the company's growth that the competing platforms have not yet contested at scale.

The Next.js community dynamics that v0 has begun to shape

The Next.js community has been Vercel-aligned by structural necessity since the framework's earliest days — Vercel employs the Next.js core team and the framework's direction is set by that team within Vercel's strategic priorities — but the community dynamics through 2025 and 2026 have produced a subtle but consequential shift in how the framework's evolution is decided. The shift is that v0's generation patterns increasingly anchor what the broader Next.js community treats as the canonical way to structure a Next.js application. The patterns v0 generates by default — the directory structure, the component organisation, the data fetching patterns, the styling approach — become the patterns that the community treats as standard, and the Next.js core team's roadmap increasingly reflects what v0 needs to generate effectively rather than what the community might have requested independently.

The implication is that v0's structural position in the scaffold market has produced an upstream influence on the framework itself. The Next.js 15 release that Vercel published in late 2025 included several features whose design rationale traces to v0's generation requirements — specific changes to the App Router's data fetching primitives, the new server actions surface, the streamlined component organisation — and the framework's direction through 2026 has continued to be substantially shaped by what v0's generation patterns benefit from. The community has been broadly accepting of the direction because the changes have been technically defensible on their own merits, but the underlying dynamic — that the scaffold platform with the largest share now shapes the framework — is a structural development that has not been fully internalised by the broader ecosystem.

The competitive implication for the alternative scaffold platforms is that the framework itself is evolving in directions that benefit v0's generation patterns over the alternative platforms' generation patterns. Bolt, Lovable, and Replit Agent are scaffolding applications against a framework whose evolution is increasingly tuned to v0's needs. The competing platforms have to either follow Next.js's evolution to maintain compatibility (which means following the direction that benefits v0) or absorb the cost of generating against an older Next.js version (which produces scaffolds that are less compatible with the current ecosystem). The structural advantage compounds. The implications for the Next.js community's governance over the medium term are worth monitoring, because the community has historically been governed by what is best for the framework's user base broadly, and the dynamic where the largest scaffold platform's needs shape the framework introduces a different governance pressure that the community has not yet substantially debated.

The community's response to v0's positioning has been mixed but predominantly accepting. The Next.js subreddit and the framework's GitHub Discussions surface have produced occasional critical threads about Vercel's dual role as framework steward and scaffold platform vendor, but the criticism has not produced the kind of governance-reform pressure that has emerged in other ecosystems where similar dual-role concerns have surfaced. The structural reason is that the Next.js community has accepted Vercel's stewardship as part of the framework's identity since the earliest days, and v0's emergence as a Vercel product is a continuation of an existing arrangement rather than a substantive change in governance. The acceptance is rational given the community's prior assumptions, but it produces a competitive dynamic that the alternative scaffold platforms have to operate against without a credible governance lever to pull. The structural finding is that the Next.js scaffold market is operating in a governance regime that favours Vercel's position, and the alternative platforms' competitive strategies have to account for this regime as a fixed constraint.

What to watch

The Q2 2026 share data captures a moment of v0 dominance, but the segment's competitive dynamics through the second half of 2026 will be shaped by several decisions the competing platforms have signalled and several product moves Vercel has not yet announced. The October 2026 share data will be the next significant data point, and the trajectory through that window will resolve whether the present concentration is the segment's structural endpoint or an intermediate state.

• Whether StackBlitz's planned H2 2026 investment in Bolt's production hosting capabilities closes the deploy-funnel gap with Vercel enough to retain a larger portion of generated applications, or whether the engineering investment required to compete with Vercel's deployment infrastructure proves prohibitive for a company of StackBlitz's scale.
• Whether Lovable's Q3 2026 fundraising cycle produces the capital required to continue the integrated-funnel strategy, or whether the company is forced to recalibrate toward a partnership model with an established deployment platform that would change the strategic positioning materially.
• Whether Replit Agent's expansion into broader application types — Python, Rust, Go — and deeper IDE integration produces a meaningful share gain in adjacent segments that compensates for the ceding of Next.js scaffold share to v0; the strategy is rational but the share data will reveal whether it produces commensurate returns.
• Whether the enterprise marketing buyer persona that Vercel has been pursuing produces the contract revenue trajectory the company has signalled, or whether the procurement friction at that tier proves slower than the engineering-led adoption pattern that v0 has anchored on through its first eighteen months.
• Whether the Next.js community's governance regime continues to accept Vercel's dual role as framework steward and scaffold platform vendor, or whether the cumulative pressure of v0's upstream influence on the framework produces a governance-reform movement that would alter the competitive dynamic for the alternative scaffold platforms.

Frequently asked

Why does Vercel's v0 hold such a large share of the Next.js scaffold market despite credible competition?

The share concentration is not driven by scaffold quality at generation time; the four platforms produce technically comparable Next.js scaffolds. The drivers are the deploy funnel that v0 anchors to Vercel's deployment infrastructure (78 per cent of v0 applications stay deployed on Vercel for the medium term) and the Vercel AI SDK distribution position that compounds the developer's mental-model alignment with the Vercel platform. The competing platforms produce scaffold-generation work that frequently exports to Vercel for production deployment, which benefits Vercel's broader Next.js share even when Vercel does not own the scaffold generation. The structural advantages compound; the scaffold quality is not the principal differentiator.

How does the Vercel AI SDK affect the competitive position of the alternative scaffold platforms?

The AI SDK has become the default integration layer for AI features in Next.js applications, with weekly downloads on the ai npm package reaching 4.3 million in May 2026. Developers learning to build AI features through v0 implicitly learn to build them with the Vercel AI SDK, which makes migration to non-Vercel platforms for AI-native applications more friction-heavy. Competing scaffold platforms (Bolt, Lovable, Replit Agent) face a strategic choice: use the Vercel AI SDK as the default integration (which strengthens Vercel's broader position) or use an alternative integration layer (which loses developer-mental-model compatibility). Neither choice is optimal for the competitive position.

What is the deploy-funnel retention metric, and why does it matter?

Deploy-funnel retention measures the percentage of generated applications that remain deployed on the originating scaffold platform's hosting layer over time. Vercel's v0 has 78 per cent retention to Vercel hosting; Lovable has 41 per cent retention to its own hosting; Bolt's retention is harder to measure directly because StackBlitz hosting is less mature for production workloads and a substantial portion exports to other platforms. The metric matters because each retained application produces ongoing hosting revenue for the platform — Vercel's investor data implies $340-$620 lifetime revenue per retained v0 application — which is the economic compounding that justifies the platform's pricing strategy at the generation tier. Without deploy-funnel retention, the scaffold generation has to recover all its costs at the generation tier itself, which is a more challenging economic model.

Why has Lovable's integrated-funnel strategy not produced higher deploy-retention?

Lovable's strategy depends on the Lovable hosting layer competing with Vercel and Netlify on the production workload tier, which requires substantial infrastructure investment. The strategy is coherent but capital-intensive, and the 41 per cent deploy retention through Q2 2026 suggests the Lovable hosting maturity has not yet reached the level where developers see it as a credible alternative to Vercel for production workloads. The Q3 2026 fundraising cycle Lovable has signalled will reveal whether the strategy continues with additional capital or whether the company recalibrates toward a partnership model with an established deployment platform.

How does v0's position affect the broader Next.js community governance?

v0's generation patterns increasingly anchor what the Next.js community treats as canonical, and the framework's evolution has begun to reflect what v0 needs to generate effectively rather than what the broader community might have requested independently. The Next.js 15 release included several features whose design rationale traces to v0's generation requirements. The community has been broadly accepting of the direction because changes have been technically defensible on their own merits, but the underlying dynamic introduces a governance pressure that the community has not substantively debated. The framework is being shaped partly by the needs of the largest scaffold platform, and the competing platforms scaffold against a framework whose evolution is tuned to v0's patterns.

What is the enterprise marketing buyer persona, and why is it strategically important for Vercel?

The enterprise marketing buyer persona refers to marketing and product operations functions at large enterprises — financial services, retail, industrial — that adopt v0 for use cases (landing pages, campaign sites, internal dashboards) that previously required either a marketing-technology vendor purchase or dedicated engineering support. The persona is strategically important because it expands Vercel's addressable market beyond engineering buyers and produces contract revenue at higher contract value than engineering-led adoption typically generates. The persona is also one the competing scaffold platforms have not produced a comparable foothold in, which represents a competitive advantage Vercel has built that is not visible in the developer-focused share data. The Q3 and Q4 2026 enterprise contract pipeline will reveal whether the strategy produces the projected revenue trajectory.