TL;DR — In 2026 the right host for an AI-built app depends on what built it. Lovable apps deploy by default to Lovable's hosting (Fly.io infrastructure underneath) at $25/mo and up; export to GitHub and you can move to anywhere. v0 generates Next.js components that deploy cleanest on Vercel ($20/mo per user). Bolt.new artifacts ship to WebContainers in-browser first and StackBlitz hosting after; you usually still want Vercel or Netlify for the production version. For everything else — Astro, SvelteKit, vanilla Jamstack — pick by what your team already uses: Vercel for Next.js teams, Cloudflare Pages for cost-and-edge-network value, Netlify for Jamstack purism. The honest break-even: Cloudflare Pages' free tier covers more than 80% of personal projects; Vercel Pro starts to matter at 100k+ MAU; Netlify is rarely the cheapest but is rarely the wrong call.
The honest comparison at the spec level
- Free tier bandwidth: Vercel 100GB/mo (Hobby), Netlify 100GB/mo (Free), Cloudflare Pages unlimited bandwidth on Free
- Paid tier floor: Vercel Pro $20/user/mo, Netlify Pro $19/user/mo, Cloudflare Pages $5/mo (Workers paid tier)
- Edge regions: Vercel 18+ regions, Netlify ~30 edge nodes, Cloudflare 330+ PoPs (the gap is real)
- Build minutes (free): Vercel 6000/mo (Hobby), Netlify 300/mo (Free — strict), Cloudflare 500/mo on Free
- Functions / serverless: Vercel Edge + Node runtime, Netlify Functions (Node + Edge), Cloudflare Workers (V8 isolates)
- Cold start: Vercel ~200-500ms (Node), Netlify ~500-1000ms (Node), Cloudflare Workers ~5ms
- Best ISR / on-demand revalidation: Vercel by 18-24 months — nobody else has caught up at the framework-integration level
- Image optimisation: Vercel built-in (separate billing past free tier), Netlify built-in, Cloudflare via Workers + Cloudflare Images add-on
- Preview deploys per PR: all three, identical
- Egress fees: Vercel — yes above free tier; Netlify — yes above paid tier; Cloudflare — no, Cloudflare has zero egress fees on Workers and R2
Hosting for Lovable apps specifically
The default path: Lovable's own hosting
Lovable.dev deploys apps to its own hosting infrastructure (Fly.io underneath) by default. Pricing in 2026: Free tier (2 projects, lovable.app subdomain), Pro at $25/mo (custom domain, 10 projects, 2GB storage), Teams at $30/user/mo (collaboration, role-based access). The deploy is one-click from inside Lovable's builder; the trade is the lovable.app subdomain on Free and a per-project ceiling on Pro.
This works fine for prototypes, MVPs, internal tools, and personal projects. It does not scale economically for production apps that need: heavy serverless logic, fine-grained API rate limiting, BYO database control, or sub-50ms global TTFB. For anything in those buckets, you export.
The "I outgrew Lovable hosting" path: Export to GitHub, deploy to Vercel/Netlify/Cloudflare Pages
Every Lovable Pro plan and above includes the "Export to GitHub" button. The export gives you a clean Vite + React + Supabase repo (or Next.js, depending on what you chose during the build). At that point you choose your host like any other modern web app.
For the typical Lovable-built app (Vite + React + Supabase + Tailwind):
- Vercel — works, $20/user/mo on Pro. The default safe choice. Vite + React deploys in 60 seconds with zero config.
- Netlify — works identically, $19/user/mo. Slight edge for non-Next.js apps because Netlify treats Vite + React as first-class without Next.js-specific routing assumptions.
- Cloudflare Pages — works, $5/mo if you exceed free tier. The cheapest of the three by a meaningful margin. Cold starts effectively zero. Egress is free, which matters if the app gets traffic.
- Render — works, $7/mo Static Site tier. Underrated; fast builds, simple billing, no surprise charges.
- Lovable's own hosting (the export and stay version) — if you exported just to own the code but want to keep deploying through Lovable.
Hosting for v0 apps
v0 by Vercel generates React components designed to drop into a Next.js + Tailwind + shadcn/ui project. The output is intentionally Vercel-friendly: the components rely on Next.js conventions (Server Components, App Router, server actions where applicable), and the recommended deployment target in v0's own UI is Vercel.
You can deploy v0-generated code anywhere Next.js runs. Cloudflare Pages now supports Next.js via OpenNext (Cloudflare Workers adapter); Netlify supports Next.js natively via the Netlify Next.js runtime. Real-world friction: v0 outputs occasionally depend on Vercel-specific primitives (Vercel KV, Vercel Blob, vercel/og for OG image generation) that need replacement when you deploy off-Vercel. Plan for 1-3 hours of adapter work per non-Vercel deploy.
Honest take: if you build with v0, deploy on Vercel. The dollar savings of going to Cloudflare Pages are real but the time you spend reworking Vercel-specific primitives usually exceeds the savings until the app is at scale ($100+/mo on Vercel before Cloudflare's pricing wins).
Hosting for Bolt.new apps
Bolt.new is StackBlitz's AI app builder. The default workflow runs the app in WebContainers in your browser (no hosting needed; the code executes client-side in WASM). For production, the standard path is to click "Deploy" inside Bolt, which sends the project to StackBlitz hosting or downloads the project for deployment elsewhere.
StackBlitz hosting is fine for demos and learning. For production, treat Bolt outputs the same as Lovable outputs: download the project, push to GitHub, deploy to Vercel/Netlify/Cloudflare Pages. Bolt outputs are usually Vite + React or Vite + Svelte; both deploy cleanly on any of the three.
Vercel vs Netlify vs Cloudflare Pages: pick by use case
Pick Vercel when
- You are building with Next.js. Vercel's Next.js features (ISR, on-demand revalidation, server actions, Edge Runtime, Image Optimization) have an 18-24 month lead over every competitor and that gap is real.
- Your app uses Vercel-specific primitives: Vercel KV, Vercel Blob, Vercel Postgres, AI SDK. Migration off these is non-trivial.
- You ship v0 components and want zero adapter friction.
- You are in the under-50k MAU range and price is not the deciding factor.
Pick Netlify when
- You are building with Astro, SvelteKit, Eleventy, Hugo, or any non-Next.js Jamstack framework. Netlify treats every framework with equal first-class support; Vercel's Next.js bias is real even when they claim otherwise.
- You want the deepest plugin ecosystem (build plugins, forms, identity, large media). Netlify's third-party extensibility is broader than Vercel's.
- You need on-prem-friendly deploys or self-hosted runners. Netlify has more flexibility here.
- You are a longtime Jamstack practitioner who values the original Jamstack DX over feature completeness.
Pick Cloudflare Pages when
- Cost is the deciding factor. Free tier has unlimited bandwidth, no egress fees, and Workers paid is $5/mo. Vercel and Netlify are 3-4x more expensive at equivalent scale.
- Edge performance matters. 330+ PoPs vs Vercel's 18 vs Netlify's ~30. The TTFB advantage is measurable on global traffic.
- You write Workers (serverless functions) and want cold starts in single-digit milliseconds. V8 isolates beat Node-based serverless on cold start by 50-100x.
- You are already in the Cloudflare ecosystem (R2 storage, D1 database, KV, Durable Objects).
When to pick none of them
- Heavy server-side workloads (long-running jobs, websockets at scale, video transcoding): use Render, Railway, Fly.io, or a managed Kubernetes platform.
- Static sites where price-per-GB is the only metric: GitHub Pages, GitLab Pages, or Cloudflare Pages free tier.
- Enterprise compliance requirements (SOC2 Type 2 + HIPAA + GDPR data residency): Vercel and Netlify both have enterprise tiers; Cloudflare Pages has compliance docs but the workflow is less polished for procurement.
AI-built app specifics — what the AI builder did not tell you
API key management
AI builders like Lovable, v0, and Bolt often embed API keys directly in client-side code if you connect to external services during the build. In production this is a security incident waiting to happen. Before deploying, every API key needs to move to server-side environment variables, and every call needs to route through a server-side proxy (Vercel API route, Netlify Function, or Cloudflare Worker). This is the single most important production fix after exporting from any AI builder.
Streaming responses
AI features (chat UIs, content generation) want streaming responses for perceived performance. Vercel's AI SDK + Edge Runtime is the smoothest path. Netlify Edge Functions support streaming but the framework wrapper is less polished. Cloudflare Workers support streaming via Response.body but require manually wiring through the front-end EventSource or ReadableStream. If your AI-built app has streaming chat, Vercel is the lowest-friction host.
Cold starts on serverless
Cold starts matter for AI apps because the first call after idle is often the user's first impression of your AI feature. Cloudflare Workers cold-start in ~5ms (V8 isolates, no Node bootstrap). Vercel Edge Functions cold-start in 50-200ms (same V8 isolate approach). Vercel Node functions cold-start in 200-500ms. Netlify Node Functions cold-start in 500-1000ms. For chat UIs and other latency-sensitive AI surfaces, Cloudflare Workers or Vercel Edge are meaningfully better than any Node-based serverless.
Egress fees
AI apps that pipe LLM responses to clients can move surprising amounts of data. A streaming chat session with a 4000-token response is ~16KB; 100k chats/month is 1.6GB; 1M chats is 16GB. At scale (10M+ chats/mo), Vercel's egress fees and Netlify's bandwidth overages start to matter. Cloudflare's zero-egress policy on Workers + R2 is increasingly the right answer for AI-heavy apps that scale.
The Vercel alternatives question (590/mo searches)
The honest reason most people search "Vercel alternatives" is one of three: (1) Vercel pricing surprised them on a project that went viral, (2) Vercel is overkill for a small static site, or (3) they want to escape the Next.js-centric framework gravity. For each, a different answer.
- For "Vercel pricing surprise" — Cloudflare Pages or Netlify Pro. Cloudflare wins on cost at scale; Netlify wins on predictability if you want a tier model rather than usage-based.
- For "Vercel is overkill" — Cloudflare Pages free tier or GitHub Pages or Render Static Site. All work for small static sites; Cloudflare gives you the most room to grow.
- For "escape Next.js gravity" — Netlify is still the most framework-agnostic of the three. Astro, SvelteKit, Eleventy, Hugo all feel equally first-class on Netlify in ways they sometimes do not on Vercel.
How this list is built
This comparison comes from running production deployments on all three platforms (Vercel, Netlify, Cloudflare Pages) plus Render and Fly.io across 50+ projects since 2020. Pricing reflects May 2026 published rates. The Lovable, v0, and Bolt.new sections come from actually shipping apps built with each one and exporting to multiple hosts. HostList.io is the broader directory (25,000+ companies) backing the wider hosting picks; for app-platform-specific picks like Vercel and Netlify it is supplementary because those are platforms, not classical hosts.
Frequently asked questions
Where should I host my Lovable app?
For prototypes and internal tools: Lovable's own hosting ($25/mo Pro). For production: export to GitHub from inside Lovable, then deploy to Vercel ($20/user/mo) for ease, Cloudflare Pages ($5/mo) for cost, or Netlify ($19/user/mo) for framework flexibility. The export is the inflection point — Lovable's hosting is fine until you outgrow it.
Is Cloudflare Pages really free for production?
Yes, in practice. Cloudflare Pages free tier has unlimited bandwidth, unlimited requests, and zero egress fees. The free tier limits are: 500 builds/month, 100 custom domains, 20k Workers requests/day. For most personal projects and small SaaS apps, you never hit any of these limits. The paid tier ($5/mo for Workers) kicks in only when you exceed 100k Workers requests/day or need additional features.
Vercel vs Netlify in 2026: which is winning?
Vercel is winning on revenue, valuation, and Next.js market share; Netlify is winning on framework neutrality and ecosystem breadth. Both are profitable and growing. Vercel's 2024-2025 expansion into AI primitives (Vercel AI SDK, v0, Vercel KV, Vercel Postgres) has tilted the playing field for AI-app workloads. Netlify's response (the Netlify Connect data layer, broader composable architecture story) has tilted it for content-heavy and multi-source apps. Pick the one that fits your specific workload; both are sound bets.
Can I host a Next.js app on Cloudflare Pages?
Yes, via OpenNext (the Next.js adapter for Cloudflare Workers). It works for most Next.js apps in 2026, with caveats: ISR has different semantics, some Edge Runtime features are not supported, and Image Optimization needs the Cloudflare Images add-on. For pure SSG Next.js apps the experience is identical to Vercel. For Server Components + ISR-heavy apps the gap is meaningful; stay on Vercel.
What about Render, Railway, Fly.io?
Render is the strongest Heroku replacement: clean billing, persistent Postgres + Redis, background workers, full-stack apps. Railway is similar but lighter on enterprise features and stronger on developer experience. Fly.io is the closest thing to "globally distributed VPS" — full Docker support, edge regions, persistent volumes, websockets. All three are excellent for full-stack apps that outgrow the Jamstack model. For Lovable / v0 / Bolt outputs specifically (which are mostly Vite + React or Next.js front-ends), Vercel + Netlify + Cloudflare remain the simpler fit.
How do I move my domain from Lovable hosting to Vercel?
Five steps. (1) In Lovable, export the project to GitHub. (2) Connect the GitHub repo to Vercel (new project). (3) Set the same environment variables in Vercel that Lovable was using (Supabase URL + anon key, any third-party API keys). (4) Deploy on Vercel, verify the app works at the Vercel-provided URL. (5) Update DNS A/CNAME records to point at Vercel. The whole migration takes 30-60 minutes for a typical Lovable app and the only downtime is the DNS propagation window (5-60 minutes depending on TTL).
What is the cheapest production-ready hosting for a React app?
Cloudflare Pages free tier, unambiguously. Unlimited bandwidth, unlimited requests, free custom SSL, $0/month for most personal projects. The only place it falls short of paid Vercel or Netlify is: build minutes ceiling on free, no built-in form handling (write a Worker), no auto image optimization (use Cloudflare Images $5/mo). For a personal portfolio or a small SaaS landing, Cloudflare Pages free is genuinely free and fast.
Will Lovable / v0 / Bolt apps still be runnable in 5 years?
Yes, because all three export to standard web code (Vite + React, Next.js, Astro). The AI builder is the build-time accelerant, not the runtime dependency. As long as the underlying framework (React, Next.js, Astro) is still supported (and all three have a 5+ year horizon at current adoption), the exported code keeps running. The risk is the builder going away while you are still actively iterating in it; export to GitHub early and keep your repo current.
Related
For VPS-tier hosting (Hetzner, Linode, Vultr, DigitalOcean): the best VPS hosting 2026 post. For managed WordPress hosting (Kinsta, WP Engine, Cloudways): the managed WordPress hosting comparison. For headless WordPress hosting (back-end + front-end split): the headless WordPress hosting guide. For building AI features on top of these hosts: the AI engineer hire page and the Claude Code agency page. For the broader 25k-company hosting directory: HostList.io.