Author: 0xjacobzhao, IOSG
The cost of code is being driven down rapidly by AI, but "getting code into production" remains an expensive engineering problem.
With roughly 6 million deployments per day, more than half triggered by AI Agents, and AI SDK downloads of about 16 million per week—Vercel appears to have already secured the next ticket in the AI era. However, does the $9.3 billion financing valuation, at roughly 27.4x equity value/revenue, already price in this "AI deployment layer" victory?
Cloudflare is attacking from the flank, AWS defines the cost floor below it and the enterprise ceiling above it, and growing customers are peeling away the tech stack layer by layer. Is what Vercel monetizes actually a moat, or a layer of abstraction that can be priced down? This article provides evidence and boundaries for this question from four angles: business model, AI distribution, competitive structure, and post-growth economics.
Core Views
Business essence: mastering the "abstraction relationship," not "infrastructure": Vercel gives away open-source Next.js for free to capture developer mindshare, then monetizes the resulting compute, memory, and delivery consumption. It does not own the underlying cloud, database, or models; what it controls is the layer of connection between developers (or Agents) and infrastructure, and what it monetizes is the abstract value of "reducing the complexity of getting code into production."
AI's structural change: directionally correct, conversion economics unproven: AI lowers the cost of software production, and Vercel's daily deployments are about 6 million, with the share triggered by Agents rising from less than 3% to more than 50% within half a year. But this is Vercel's own denominator, not industry share; whether Agent projects can survive, pay, and accumulate gross margin still lacks public evidence.
Defensibility layering: first-mover lead, not an absolute moat: a decade of accumulated Web frameworks and deployment workflows is the core of revenue. New tools for Agents can be copied, while databases, models, and the underlying cloud all belong to partners, and the data assets with the highest customer stickiness remain outside the platform.
The real mechanism of competition: substitutes do not need to win migration, only to cap pricing power: Cloudflare and AWS only need to offer credible alternatives at renewal to compress Vercel's abstraction premium; as customers grow, they also tend to migrate always-on compute and data to PaaS or hyperscale clouds, which sets a ceiling on per-customer value expansion.
What Vercel Is: A Monetized Layer of Abstraction
Business Positioning
Vercel is a deployment and delivery platform for modern Web applications. Developers only need to connect a Git repository, and Vercel can automatically parse the code and derive the corresponding infrastructure topology, generate preview URLs, and carry production traffic through its edge network. The company mainly charges through seat fees, compute and memory resources, function invocation counts, build duration, and delivery traffic.
Vercel's strategic narrative is to build the "control plane for AI-generated software," controlling the entire path "from Prompt to Production." But in essence, what Vercel sells is not infrastructure, but the contractual relationship between developers and infrastructure.
▲ Figure 1 Business snapshot: company self-reported unless otherwise noted; valuation is a historical financing reference, not a currently tradable price
Why This Layer of Abstraction Is Valuable
▲ Figure 2 Traditional cloud exposes infrastructure primitives; Vercel packages common Web infrastructure behind opinionated defaults
Vercel is not just "a simpler cloud," but a layer of opinionated application deployment abstraction: it removes a specific set of composition decisions such as build, runtime, CDN, TLS, and routing, replacing them with defaults derived from application code. The exchange is bidirectional—fewer decisions and a faster path to launch, in exchange for less infrastructure control and flexibility. Traditional cloud makes the opposite trade-off, and is the right answer only for teams that genuinely need that control.
This layer of abstraction is most valuable to teams that "own application code but lack a platform engineering function to absorb these decisions." This is also why AI matters commercially, not just narratively: when AI lowers the cost of writing software, Vercel lowers the cost of getting software into production, and the population that "can write usable code but has no intention of assembling infrastructure" is growing faster than the population of platform engineers.
How Money Is Made, and What Is Not Revenue
Vercel is a usage business with a seat component, not a seat business with a usage component.
AI Gateway's monthly 20 trillion Token traffic and the third-party databases resold through Marketplace are both pass-through transaction flows collected and paid on behalf of others, with the vast majority of their value belonging to the underlying suppliers; Vercel does not mark up tokens. Counting these two items as its own turnover or addressable market would inflate it by an order of magnitude; their true strategic value lies in enhancing customer attachment and observability, not in contributing direct revenue.
Growth Path: Four Times "Giving Away Friction for Free"
Vercel's commercial evolution history is essentially a process of "offering products for free to eliminate friction," thereby anchoring usage monetization. Next.js was never a paid product and has always been self-hostable. What it brings is the largest public corpus of deployment examples in Web development, a default answer to "how should this be built," and a feedback loop that lets Vercel design both framework primitives and infrastructure.
What AI Changed: Migration of the Distribution Layer
Who Is Actually Choosing
▲ Figure 3 Agents are becoming a distribution channel—but "can integrate," "is chosen," and "becomes the default host" are three different things
In the era of AI writing code, the power to decide the deployment target is shifting:
Integrated build platforms (such as Lovable, Replit, Bolt): aimed at non-technical users, tightly binding creation and hosting. Vercel is not the default option here, but its own v0 constitutes its dedicated entry point.
General-purpose Coding Agents (such as Claude Code, Cursor, Codex): aimed at professional developers, remaining hosting-neutral. Developers and the Agent toolchains behind them form the choice, and Vercel concentrates resources on binding its own CLI, MCP Server, and skills as the preferred deployment option within such ecosystems.
Leveraging acquisition funnels embedded in Claude Code and Cursor, machine interfaces such as MCP/API, and an immutable preview loop, Vercel has established a first-mover advantage with a very high Agent first-attempt success rate; but such engineering tools are extremely easy for competitors such as Cloudflare to follow and replicate, and can only increase the probability of being chosen by default, not constitute an absolute moat.
From Activity to Economics
▲ Figure 4 Activity is visible and vendor self-reported; the economics of conversion is the due diligence question
There is a huge data gap between distribution through Agent tools and high-frequency deployment on one side, and conversion into durable economic returns on the other: on one hand, there is a lack of public evidence on whether deployed projects can survive as live production applications and whether they can convert into paying customers; on the other hand, it is also unproven whether ultimately billable resources can settle into high gross margin and long-term customer expansion.
In short, the surge in deployment volume is only upfront investment; whether it can convert into durable gross margin is the final result that still needs to be proven.
Customers and Control: Where It Wins, Where It Expands
Who Is Actually Using Vercel
▲ Figure 5 Analytical segmentation, not market share data: platform choice varies with technical depth, workload complexity, and organizational maturity
Non-technical builders: pursuing zero operational decisions and extremely fast launch, preferring all-in-one platforms such as Lovable and Replit that completely hide infrastructure; Vercel is not the default host here, but locks in the upstream entry point through its own v0.
AI-native builders: holding the code themselves but choosing to outsource infrastructure complexity, clustering on deployment-first platforms; this is Vercel's most core sweet spot and the fastest-growing customer group in its user funnel.
Professional developers: valuing Git workflows, preview loops, and deployment determinism, mainly landing on Vercel and its direct peers; as the commercial base, they continue to contribute stable recurring usage revenue.
Platform engineers: whose demands lie in always-on processes, state control, and high-utilization compute, tending to choose backend PaaS/BaaS such as Railway and Supabase; such platforms usually coexist with Vercel as complements rather than full replacements.Enterprise IT: Core demands are VPC isolation, security compliance, and cloud budget offsetting, led by hyperscale clouds and dedicated SRE teams; this constitutes Vercel's ceiling, but enterprises can still retain Vercel for the front-end web layer.
Below Vercel, integrated build platforms remove infrastructure decisions entirely; above it, platform teams increasingly want to take that decision back. Vercel's strongest position is in the middle—technically capable enough to own the code, but with no intention of owning infrastructure complexity.
Three Layers of Control
▲ Figure 6: An established web deployment kernel, plus an Agent expansion whose commercial outcome remains unproven
Vercel owns an extremely consolidated web deployment kernel (the Next.js framework, Git deployment workflows, and edge delivery network), which is the foundation of its current commercial success. For the AI era, although it has rapidly broadened its product line through AI SDK, AI Gateway, and a new Agent expansion layer (Sandbox, Services, BYOC, etc.), and draws traffic through v0 or external Coding Agents, a broadened product line does not equate to proven commercial control—the commercialization results of its Agent expansion layer remain to be validated by the market, and its underlying models and data assets remain highly dependent on external partners.
Likewise, Vercel resells AWS databases through its own console, monetizing the "connection relationship" rather than infrastructure; it also supports transactions via AWS Marketplace to offset existing cloud commitments, and does not mark up model tokens, in exchange for observability and ecosystem stickiness.
Competition and Ecosystem: How Substitutes Cap Pricing Power
▲ Figure 7: Vercel's competitive ecosystem: who is a substitute, who is a partner, and who is both
Cloudflare exerts direct product competition; AWS is the larger structural constraint, because it is simultaneously the substrate, the enterprise procurement channel, the owner of substitute services, and the platform that mature customers want more direct control over. A concise (analytical) framing: Cloudflare attacks Vercel from the flank; AWS defines the infrastructure floor below it and the enterprise ceiling above it.
▲ Figure 8: Direct products, partner integrations, and unproven expansions side by side: no single player covers all layers
No single player simultaneously owns creation, deployment, data, AI spend, and enterprise procurement. An "AI application control plane" as a prize that can be won on its own does not appear to exist, and the same applies to any competitor claiming to capture it.
Cloudflare, with its own network and Workers not charging egress fees, has a cost advantage in scenarios such as edge delivery, and does not need to migrate customers wholesale—merely providing a credible alternative at renewal is enough to cap Vercel's pricing premium; although its Workers still has shortcomings in compute and deployment experience, together with competitors such as CloudFront, Railway, and Supabase, it forms a ceiling that limits Vercel's pricing power and expansion space.
Economics: Is the Premium Worth It, and How Does It Unbundle as You Grow
Why Customers Are Willing to Pay a Premium for Abstraction
Vercel's raw resource costs are usually not the lowest, but its core selling point is reducing the total cost of ownership of "engineering time, operational complexity, and reliability risk." For small organizations lacking a platform operations team, trading a premium of a few hundred dollars per month for saved operations hours makes the math easier (the break-even point requires saving less than 7 hours of operations per month).
However, for large teams that already have mature cloud operations capabilities, the cost-effectiveness of this premium drops significantly, prompting them to shed baseline workloads as they scale.
From Abstraction to Infrastructure Ownership
▲ Figure 9: Illustrative operational profile—not a hard migration threshold
BUILD stage (extreme speed): pursuing ultra-fast launch and zero operational decisions, with applications and data fully hosted on Vercel.
SCALE stage (hybrid optimization): web and previews remain on Vercel, while backend services, queues, and data are gradually offloaded to PaaS/managed databases.
OWN stage (autonomous control): hyperscale cloud dominates, with Vercel retaining only the web application layer.
The saying "small companies use Vercel, large companies graduate to AWS" is overly simplistic; the reality is the unbundling of the tech stack and workload restructuring: as teams evolve through the Build (extreme speed), Scale (hybrid optimization), and Own (autonomous control) stages, they move always-on compute, data, and stateful services to PaaS or hyperscale clouds, but still keep web applications, preview environments, and deployment workflows on Vercel.
Risks and Market Space
Main Risks
Vercel's raw resource costs are usually not the lowest, but its core selling point is reducing the total cost of ownership of "engineering time, operational complexity, and reliability risk." For small organizations lacking a platform operations team, trading a premium of a few hundred dollars per month for saved operations hours makes the math easier (the break-even point requires saving less than 7 hours of operations per month).
However, for large teams that already have mature cloud operations capabilities, the cost-effectiveness of this premium drops significantly, prompting them to shed baseline workloads as they scale.
Market Space
The trillion-dollar cloud market figure is misleading and needs to be narrowed layer by layer:
$340 million in annualized revenue is roughly 3–4% of the addressable abstraction layer, leaving ample room for growth. What truly determines the outcome is retention, gross margin, pricing power, and entry valuation, not the size of the opportunity.
💡 Summary
Vercel's commercial essence lies in monetizing the abstract relationship between code and cloud, rather than owning the underlying infrastructure, and the vast majority of its current revenue still comes from the established web deployment kernel. AI has indeed brought it the right direction of exposure, and Agent-triggered deployments account for over 50% (this only represents Vercel's internal traffic structure), but there is no evidence yet that high-frequency deployment activity can ultimately translate into durable gross margin.
In terms of defensive moats, although the company has a first-mover advantage, Agent-oriented tools are extremely easy to follow and replicate, and core assets such as data, models, and the underlying cloud all remain outside the platform.
Facing competition, substitutes such as Cloudflare and AWS do not need to migrate customers entirely—merely offering a credible choice during renewal negotiations is enough to effectively cap its pricing power, while scaled-up growing customers are also more inclined to unbundle the tech stack to reclaim underlying control.