Vercel vs Netlify in 2026: Which One Actually Hosts Your Vibe-Coded App?

The short answer

If your app makes money — even $5 a month, even donations — Vercel's free Hobby plan is not an option: its fair-use policy restricts Hobby to non-commercial personal use, and commercial usage requires Pro at $20 per seat. Netlify publishes no equivalent prohibition, so a small paid app can genuinely start on its free tier; the catch is credits, which a vibe-coded project burns fast. For a Next.js app with real traffic, Vercel Pro is the smoothest path and Netlify Pro is the same $20 with a different failure mode. And if your app is mostly static, Cloudflare undercuts both by not billing bandwidth at all.

That's the practical ranking. What follows is why the 2023-era comparison you've read elsewhere no longer applies: both platforms replaced their pricing models this year, and the AI builders quietly stopped defaulting to either of them.

Both pricing models changed in 2026

Vercel now meters compute on three axes instead of GB-hours: Active CPU (from $0.128/hour), Provisioned Memory (from $0.0106/GB-hour), and Function Invocations ($0.60 per million), on top of data transfer and edge requests. It's called Active CPU pricing for Fluid compute, it's the default on every plan, and the pitch is that idle time in a serverless function stops costing you full price. Pro is $20 per developer seat and includes $20 of usage credit; viewer seats are free.

Netlify went further and replaced bandwidth and build minutes entirely with credits. Free gives 300 credits a month, Personal $9 gives 1,000, Pro $20 gives 3,000, with add-on packs beyond that. The prices that matter: a production deploy costs 15 credits, bandwidth 20 credits per GB, compute 10 credits per GB-hour, web requests 2 credits per 10,000 — and deploy previews cost nothing. Netlify's stated reason for the change is a developer base iterating "at machine speed," which is a polite way of describing what AI coding did to their build volume.

The free tiers: two different walls

Vercel's Hobby plan is generous on paper — 100 GB of data transfer, a million function invocations, a million edge requests, 4 CPU-hours, 200 projects. Then you read the fair-use guidelines, which state that Hobby teams are "restricted to non-commercial personal use only" and that all commercial usage requires Pro or Enterprise. Their own definition of commercial is wide: processing payments, advertising a product, being paid to build the site, affiliate links as the primary purpose, ads — and donations count. A solo founder charging for the app they vibe-coded is out of policy from the first customer. Hobby also has no spend management, only hard caps that lock the feature for 30 days when exceeded.

Netlify's wall is arithmetic instead of policy. 300 free credits at 15 credits per production deploy works out to about 20 production deploys a month at zero traffic — that's our division, not Netlify's published figure — or roughly 15 GB of bandwidth if you spend it all there. When credits run out on the free plan, projects pause and visitors see a "Site not available" page. That's the important difference in kind: Netlify's free tier stops, Vercel's paid tiers keep spending. Auto-recharge is off by default and free plans can't buy credits, so the free-tier failure mode is downtime, never a bill.

Where AI builders actually deploy (this changed too)

The received wisdom — "Bolt deploys to Netlify" — is 2024 information. Today Bolt.new publishes to Bolt hosting by default, with Netlify as an opt-in requiring your own account. Lovable hosts published apps on its own infrastructure, HTTPS included, with no in-app Vercel or Netlify button; the Netlify route runs through GitHub. Replit uses its own Deployments. Only v0 still deploys straight to Vercel — and that's because Vercel owns it.

So the real decision point moved: you choose a host when you export the code to your own repository, need a custom domain and real traffic, or when the builder's own hosting bill stops making sense. Worth knowing for context: the Bolt-Netlify partnership was real and enormous while it lasted — the two companies announced a million AI-generated sites deployed in five months (November 2024 to March 2025). That volume is exactly why Netlify repriced around credits and built agent tooling.

"Next.js only really works on Vercel" — not anymore

This was true enough to repeat for years; the docs no longer support it. Netlify runs Next.js through the OpenNext adapter and lists full support for the App Router, SSR, SSG, ISR, React Server Components, Server Actions, streaming, Route Handlers, image optimization, Draft Mode, Turbopack, Cache Components, and Partial Prerendering. Since most AI builders generate Next.js, that matters directly.

The real gaps are narrower and worth knowing: pages configured for the edge runtime run in your functions region under Node instead of at the edge, so you lose edge locality; middleware runs as Edge Functions with different header and redirect evaluation order; rewrites can't point at files in the public directory. If your app is a normal CRUD SaaS, none of those will surface. If you built something latency-sensitive at the edge, Vercel keeps that advantage.

Bill shock: the story worth telling honestly

The canonical Vercel horror story is Cara, an artist social app that went viral in June 2024 — 40,000 to 650,000 users in a week, peaking at 56 million function invocations in a day. The founder wrote publicly that going viral brought "a $100k bill from one of our service providers for 1 week of traffic." We're stating it exactly that loosely on purpose: the widely-quoted precise figure and the claim that it was waived don't hold up to checking, so treat the round number as the founder's own and the outcome as unreported.

What matters more is the control you get today. Vercel's Spend Management lets Pro and Enterprise teams set a dollar limit with alerts at 50/75/100% and an optional auto-pause — but the docs are candid that usage is checked "every few minutes," so projects can keep accruing after you cross the line, pausing is opt-in, and unpausing is manual per project. Hobby has no spend management at all. Netlify's structure makes the runaway scenario unlikely rather than survivable: free plans hard-stop, and auto-recharge is off unless you turn it on. Different philosophies — one lets you scale through a spike and bills you, the other takes you offline and doesn't.

Netlify's 2026 pitch: hosting for agents

Worth a section because it's genuinely differentiated. Netlify shipped Agent Runners — you run Claude Code, Codex, or Gemini from the Netlify dashboard with your project context, build settings, and deploy pipeline already wired — plus an AI Gateway that lets you call models without your own API keys, metered at 180 credits per $1 of model usage, and an official MCP server so agents can create projects and deploy through natural language.

Vercel's 2026 answer is broader-platform rather than agent-first: Dockerfile support and a container registry, first-class backend frameworks (FastAPI, Flask, Express, Hono, MCP servers), Vercel Services for microservices, an AI SDK release, and Vercel Agent in public beta that investigates production alerts and opens fix PRs. Read the two roadmaps together and the positioning is clear — Netlify wants to be where your agent works; Vercel wants to be where your whole backend lives.

The cheaper options nobody mentions

For a mostly-static vibe-coded app, Cloudflare is the honest answer: the free tier covers 100,000 requests a day with unlimited static asset serving, the paid plan starts at $5 a month, and bandwidth simply isn't a billable axis — which removes the entire viral-traffic failure mode. Railway starts at $5 a month with per-second metering and $0.05/GB egress if you want a container rather than a function. Render's free tier gives 5 GB of bandwidth, with Pro at $25. None of these have Vercel's Next.js polish; all of them are harder to accidentally overspend on.

The verdict

Paid app on a budget: Netlify Free is the only one of the two whose terms you're not breaking, and the credit ceiling is a downtime risk rather than a bill. Serious Next.js app with traffic: Vercel Pro at $20 — the platform is built around the framework, and you get spend management, which Hobby lacks. Redeploying constantly while iterating with an AI: watch credits on Netlify, where each production deploy costs 15 of them, and let deploy previews (free) absorb the churn. Mostly static: Cloudflare, and stop thinking about bandwidth. Whichever you pick, do the one thing both platforms make optional and neither makes automatic — set a spend limit or a credit alert the day you deploy, before traffic makes it interesting.