Every service, ranked by real customers

Ran a web app on Vercel and liked the easy GitHub deploys and dashboard, but worried about the bill when junk traffic hit usage-based pricing, and later moved to a rented VPS.

Built a GitHub plus Cloudflare Pages workflow that is straightforward and publishes a site in under 5 minutes at no extra cost per site.

Moved client Next.js apps to Cloudflare Workers because Vercel started charging an extra 20 dollars for external project members who want to push code.

Still uses Netlify for all projects because it is simple and just works: connect the repo and DNS, environment variables, deploy stage and automated builds are all easy.

Self-hosts now but says that, having used Vercel, Heroku and AWS before, Vercel was the cheapest option for the value.

Left Vercel because with two developers the per-seat charges plus a separate database made costs crazy for a starting project, versus a Coolify setup at much less.

They moved their static site to Neocities and say it works well, with the custom domain DNS setup going fine.

Moved a simple site with forms and a blog from Wix to Cloudflare in about 4 days and has never been happier.

Moved off Netlify because the new credit system charges 15 credits per deploy and traffic, and the site goes dark when credits run out.

Has used Netlify flawlessly for Angular and Flutter sites on the free tier for a year, paying 20 a month for private repos, though support took about 24 hours on a DNS issue.

They pay about $20 a month for Vercel and stay under the included usage, but disabled overages after one month went over and the bill reached around $70.

They used Vercel in an enterprise setting at roughly $250K a year for 20 million MAUs and about 400 billion requests, and said it was worth the money compared with building the infrastructure themselves.

They were banned from Neocities after complaints about their controversial content. They liked how simple it was to use and still had a ZIP of their HTML/CSS files to move elsewhere.

Business site on Vercel loads fast sometimes but most of the time shows site cannot be reached; calls it the worst host used in 20 years.

After nearly two years on Vercel with a site of many pages, costs hit about 10 dollars a day and they moved to a dedicated VPS at 29 a month.

Finds Vercel’s mandatory phone verification when creating accounts the most annoying part and sometimes uses Cloudflare Pages instead.

A first-time builder says Vercel cost an astronomical amount for just the homepage and moved off it.

Migrated four Vercel Next.js builds to Cloudflare within a day, keeps all builds in one place and says costs are better at scale.

They moved their static sites to Cloudflare Pages after a paid host lapsed, using the free tier with a custom domain and no card required.

Finds the Cloudflare Pages free tier very generous with no commercial restriction, and uses it with Workers for everything now.

Switched from GitHub Pages to Cloudflare Pages and says it has been rock solid.

Hosts a blog, portfolio, photo gallery and a couple of live side products with real users on Cloudflare Pages for a total bill of $0.

Uses Cloudflare Pages for around 5 websites, three of them portfolios, and adds Workers when functions are needed.

Has had a portfolio on the Cloudflare Pages free tier for a while without any issue.

Vercel charges an extra 20 a month per committer on private repos on top of the Pro account, so they cancelled the project and Pro plan.

Chose Cloudflare Pages over Vercel and has had a great experience so far.

Pays 20 a month for Vercel for personal and a wife’s coaching site and says it has been great.

Vercel’s extra per-seat billing was more than their nonprofit could manage so they cancelled.

Has several static sites on Netlify with Svelte, Next and Vue and no issues, and uses its DNS management as well.

Has used Netlify for a client site for nearly three years, great for static sites, with build minutes and serverless limits as the main caveats.

Netlify turned off a site after 300 credits vanished on an idle static site; they paid 9 to restore it and are moving to Cloudflare.

Found deploying Next.js to Cloudflare pretty straightforward, with a really smooth adapter.

Tried deploying Next.js on Cloudflare with OpenNext but hit caching problems and runtime errors.

They switched to Vercel after GitHub Pages failed for their static Next.js export, and it is working there.

They could not get their Next.js image export setup working on GitHub Pages despite trying basePath in config and inline, and gave up and moved to Vercel.

An SSG ecommerce site took 2-3 seconds per page navigation on Netlify but 300-400ms on Cloudflare and Vercel, so they moved to Astro on Cloudflare.

They deployed the same project on Netlify without extra basePath work and it worked straightforwardly.

Runs a professional portfolio built with Astro for free on Cloudflare with a proper domain and stupid fast performance; calls Cloudflare very cheap and powerful below enterprise level.

Rebuilt their site and hosts it free on Cloudflare Pages, paying only about $5 a year for the domain.

Their Next.js site has been painless on Vercel, usually just a git push, and the convenience keeps them there.

They host web games and client landing pages on Vercel with GitHub and Claude, say it works flawlessly after spending thousands on Webflow, and would gladly pay when needed.

They build their portfolio in Webflow, export the code and host it free on Netlify, and say it works perfectly for a static portfolio.

After five years paying Webflow fees they exported their one-page portfolio and now host it free on Cloudflare Pages.

Hosts a one-file game on the Cloudflare Pages free tier with a Worker plus KV leaderboard that has served players in 25 countries.

Deploying a Next.js app to Cloudflare Pages hit many Edge Runtime incompatibility errors that were only solved by moving to Workers.

Their GitHub Pages custom domain site worked for a week, then showed an SSL protocol error for two days. Removing and re-adding the domain and re-enforcing HTTPS did not help.

After traffic hit limits on an open-source app the user upgraded to the 20 dollar plan and still got a surprise 100 dollar add-on bill at month end, then moved to their own VPS.

Their free Netlify account was suspended without notice and support gave no response for over a week.

Could not get a Lovable site migrated to Cloudflare Pages and found its control panel like operating a space station.

Hates it, calling it absolute garbage, and points to endless complaints in the Amplify Discord from people frantically trying to fix their production deploys.

Two years of building a tutoring platform ended in migrating to Supabase because DynamoDB lacked SQL joins and Cognito authentication was a pain.

Has never had any issues with Vercel despite hearing complaints, finding it easy in and out for simple projects.

Had a site on Vercel for a week and found great developer experience but bad invoices.

Runs many small low-traffic projects on Vercel, which is cheap for that and simplifies deployment, moving projects out only if traffic grows a lot.

Uses Vercel because it is easy and friendly for ship-and-test projects, keeping a private VPS for more demanding validated projects.

Hosts all company websites on Vercel Pro for about 20 euros and considers it a good deal.

Has used nothing but Vercel since discovering it, for both Next.js and SvelteKit.

They autodeploy their projects from GitHub to Cloudflare Pages and like the extra features included for free.

They run web apps with multiple users on Vercel and stay well within the free tier; a bug once maxed their function invocation cap, so they started a new account and moved their repo.

They migrated a Next.js app off Vercel and found hosting it elsewhere annoying, taking a few months to set up CI/CD and a VPS.

Netlify took two live sites fully down when deploy credits ran out, could not buy credits on free, and a 2FA failure locked them out of the account.

Upgraded to Netlify Personal at 9 a month but still only gets 1000 credits, which frequent deploys burn through quickly.

Runs 13 apps on Cloudflare for two years, compares it to Vercel at work, and says it is now better, cheaper and running smoothly.

Says Vercel is great and works well with their Next.js setup via GitHub Actions.

At an agency, Netlify’s Image CDN went down for an hour and later the whole system returned 503 or SSL errors for about an hour with the dashboard inaccessible.

Moved from Netlify to Cloudflare Pages for 500 free builds and no server compute, but found concurrent builds need a $20 Pro tier and support did not help.

Has worked on products with 50,000 daily active users on a 20 dollar a month Vercel plan.

Moved from Wix to Netlify with Claude and GitHub so code changes auto-deploy, with DNS the hardest part.

Has 6,600 users across staging and production on Vercel for a total bill of 70 dollars.

Worked on an e-commerce shop on Vercel with about 50,000 orders a month that cost around 10,000 dollars a month, suggesting parts of the backend belonged on AWS.

Was billed about 300 dollars a month on Vercel and cut it to about 100 dollars with a dedicated server, Cloudflare and Coolify.

Their work Vercel Pro plan produced a last bill of around 10,000 dollars, so they are looking for alternatives.

Runs a SaaS with 300 users on Vercel and pays only 20 dollars a month with no problem.

Averages 3,800 unique sessions a day on Vercel while paying 20 dollars a month and expects it can handle more.

Chose Cloudflare Pages after trying multiple services because the free plan is generous, while Netlify got limiting with limited monthly deployments.

Built their site with Porkbun, Cloudflare and GitHub; Netlify ran out of commits so they moved to Cloudflare, which worked really well.

Bought a domain at Porkbun and hosted the page on Cloudflare, finding it a lot faster and more feature rich.

Their agency hosts over 40 sites for about 30 dollars a month and has never been charged an overage.

Deploys several very large projects on Vercel without spending a fortune, paying only for a Pro account to remove the watermark, and calls it the best of the best after trying alternatives.

A traffic spike cost 317 on Vercel Pro; support took about two weeks but gave a root cause analysis, mitigation guidance and a 278 refund.

A colleague deploying 30-plus times a day racked up a 250 dollar Vercel bill for one project in build time alone, so they are moving to a VPS for about 70 dollars a month across several projects.

Runs a big website with thousands of users and many pages on Vercel and finds the cost fair, way cheaper than paying devops to handle Kubernetes scaling.

Used Vercel for years before moving about 50 projects to Cloudflare, calling Vercel overly expensive and charging for things that are nearly unlimited elsewhere.

Auto-deployment on Cloudflare Pages started failing on env-var imports after a UI-only change, forcing manual wrangler builds and deploys.

Finds Vercel works well with many good features and does everything needed on the free plan.

Stays on Vercel because moving off cost far more time in config and builds, though a small project once had higher usage than expected.

Calls Vercel the best because analytics, caching and observability just work and save hours, so paying an extra 50 dollars a month is fine.

Has deployed numerous Next.js apps on Cloudflare Pages on the free tier without running out of usage; compatibility has improved a lot.

Pays about 25 dollars a month on Vercel for 50,000 users plus over two million scraper hits and finds the features useful and simple.

Has ten sites on Vercel and has not passed 5 dollars in spend; calls it unbeatable hosting value for low-traffic sites.

Runs multi-tenant sites on Vercel that barely hit 10 percent of plan limits, very snappy sites and happy clients, though not heavy e-commerce or media sites.

Has paid the same 20 dollars a month to Vercel for over five years, with only about 20 dollars in extra charges in total, and likes it.

Loves Vercel as super easy to set up and maintain, with one catch: the Pro plan opts you into expensive Turbo build machines that you should switch to standard.

Pays 20 dollars a month to Vercel, merges to main and the site deploys, expecting the business model to cover bills as it scales.

Runs a website on the Vercel free plan and it works perfectly fine.

Their company pays over 100,000 dollars a year to Vercel, mostly ISR costs on a frequently changing catalogue site, and feels held hostage because migrating off is costly.

Runs 20 client websites from one multi-tenant Vercel app with tens of thousands of monthly page views and still has not passed the 20 dollar a month limit; cheaper than their old Google Cloud setup.

Likes Vercel for its generous free tier, easy initial deployment and extras like basic observability and DDoS protection; says it is not meant to scale cheaply.

As a solo developer finds Vercel CI/CD, GitHub integration, cron support and rollback a lifesaver compared with maintaining production infrastructure.

Calls Vercel one of the best software products they have come across.

Migrated most Node apps off Vercel to cut cost after their Vercel plan surprisingly doubled in price.

They ran four side projects on Vercel with modest traffic and were hit with a 380 dollar invoice, which they found shocking for projects that earn nothing.

Needing a static IP for security meant a 100 dollar base charge plus extra Vercel Private Data Transfer, and every cache-miss build downloading packages through that IP cost a fortune.

Vercel bill crept up to 300-plus dollars with unchanged API routes and the logs needed another paid subscription to inspect; they migrated off, which was painful but worth it.

An app that has basically not changed started seeing Vercel costs creep up each month from bot and AI traffic plus ISR.

Got a Vercel bill with over 120 dollars of on-demand usage so far in the cycle.

Production deploys on Vercel failed during a Dubai region incident even though the project had nothing in that region, stalling a release.

Benchmarked Vercel serverless as showing very strong cold and warm performance and a very mature product for Next.js.

Deploying a TanStack Start site to Cloudflare Pages was messy until they dropped the plugin and prerendered statically, after which Pages served the output properly.

Finds Vercel at 20 dollars a month very reasonable for maintenance-free scaling, one-click deployment and git integration for most projects.

Uses Vercel for an MVP because of automatic preview and production deployments on commit and PR with live URLs, easy environment variable management, and helpful docs.

Free-tier Vercel limits were blown by GPTBot making 164,000 requests a day to an open-source docs site, forcing an upgrade to Pro, though the free tier had been enough before.

They are trying Vercel and host all their low-traffic small business sites under one $20 a month plan.

A ByteDance crawler ran up a roughly 20,000 dollar Vercel bill and Vercel refused to reduce it.

They host their personal site on Neocities and describe it as free and about as easy to use as Visual Studio Code, with an old-fashioned mission they like.

Moved a Kickstarter landing page from Lightsail WordPress to Cloudflare Pages with Supabase and is very satisfied with the setup.

Benchmarked Netlify as the slowest of Vercel, Cloudflare and Netlify, slow when warm and about 3x slower on cold starts.

Uses Cloudflare Pages for a React SPA frontend and finds it ridiculously fast for static hosting.

Dropped a $180 renewal host for free Cloudflare Pages for a portfolio site and was glad to be rid of cPanel and DNS hassle, noting it is unbelievably fast.

Replaced a $320 a year WHM/cPanel setup with a static site on Cloudflare, took about two days to learn, and now pays only for domains.

During a Vercel incident a commit broke their app, further commits stayed staged and they could not log back in.

During a Vercel incident the site stayed up but new deployments were ignored and the dashboard would not load.

A static site on the Netlify free plan burned 180 credits quickly because each git push cost 15 credits, leaving only 59 credits before a shared QR-coded URL goes live.

Recently migrated from Vercel to Cloudflare because it does not charge for edge requests and calls it the smartest thing to do.

Moved a popular static site pushing about 6 TB of bandwidth a month from Vercel to Cloudflare Pages and after a couple of weeks the bill is still free.

Frustrated at being nickel-and-dimed 150 dollars by Vercel for Deployment Protection Exceptions and is strongly considering leaving.

At a company with few people managing servers, Vercel is a one-time setup plus git push and just works, with labour cost far lower than AWS apart from one big outage.

Vercel bill reached 1,933.93 dollars in one month, up from 30 the month before, after Meta crawler traffic triggered millions of serverless function invocations.

Left Netlify after finding that its password-protected site feature for an under-construction domain costs a premium.

A nonprofit with 14 million unique monthly visitors was facing 23,000 dollar monthly Vercel bills and found Vercel support and sales worthless, so moved to VPS servers that drop for seconds at times.

After several years under 100 dollars a month on Vercel, one month jumped to over 800 for a front-end-only Next.js app, and support took nearly two weeks to give a generic answer; moved to Cloudflare Workers.

Pays over 300 dollars a month on Vercel for what would cost about 80 on AWS directly; likes the developer experience but finds the markup insane and pricing opaque.

Used Vercel 2-3 years for several client projects on the free tier without paying anything, running complex Next.js and Vite apps with firewall and bot controls built in.

Uses Vercel hobby for dozens of projects, has never hit limits or been banned, and finds them friendly to free users.

Has run a small business site on the Vercel Hobby plan for over two years with about 60 visitors a day and no ban.

Deploying Next.js with OpenNext to Cloudflare Workers has been challenging, with missing features and a specific required setup.

Says the Vercel free plan already offers speed insights, analytics and DDoS protection and works wonderfully with GitHub.

Handled a small business web app with invoicing, attendance tracking, and analytics for a full month in production without a single issue.

Had Claude Code build a static site on free GitHub and Cloudflare, costing about $3.50 a month with domain and Claude.

Migrating 23 projects from Netlify, which became greedy, to Vercel, which feels much more mature with many more features.

Runs several Express apps and Hono APIs on the Vercel free tier and stays under its limits.

A Vercel project with 18-20k daily visitors produced a bill of about 1,000-1,200 dollars a month, mostly Fast Data Transfer at 80-160 GB a day, with a 2.5 MB first load bundle.

Runs a fairly complex marketing site with hundreds of pages and millions of monthly visitors on Vercel Pro for about 200 dollars a month.

They run their own custom domain on GitHub Pages without buying an SSL certificate, since it comes with a Let's Encrypt certificate.

Says the Netlify free tier is no longer worth considering because the credit system allows only about 20 deploys a month before the site stops; helped a friend move to Cloudflare Pages.

They use Neocities to host their retro photo editor site and say it is great, noting the platform limits them to its .org domain.

They use Amplify for simple web apps with APIs behind an API gateway. Their full setup with extras cost around 60 a month, and they recall SSR apps on Amplify possibly being pricier.

A developer hosts their site on Vercel's free tier with their own custom domain.

On the new Netlify free plan they burned all 300 credits in under two days with tiny traffic from frequent builds, pausing every site.

Stopped using Netlify the day of a startup demo when their site was terminated with no communication.

They deployed a client landing page on GitHub Pages for free with a custom domain and HTTPS and no server costs. DNS propagation was slow but it was smooth once sorted.

Moved from Netlify to Cloudflare Pages and finds it better with better free limits, more stable infra and a better UI.

Netlify was great until credits made deploys feel costly, so they now think twice before pushing code.

They tried Cloudflare Pages and Workers after migrating from the Azure edg.io sunset but hit a problem disabling weak cipher suites. They found it frustrating and had to move back to an Azure CDN service.

Calls Netlify new credit system bad, with 15 credits per deploy against 300 credits free and 2000 on a 10 dollar plan; moving to GitHub Pages.

Recent experimenting left them very pleased overall, and they see the global CDN, tight CI/CD coupling, zero downtime, easy authentication and free deployment environments as big pluses.

Gave up deploying a Next.js 15 app with dynamic routes to Cloudflare Pages because it was too annoying and used Vercel instead.

Vercel image transformation costs jumped from about 15 dollars to 70 in one month with only a slight traffic rise, now most of the bill, so they are migrating away.

They have used Netlify since 2019 for static sites with the source on GitHub and say it has always worked well for them.

Next.js on-demand revalidation did not work at all during testing, adding frustrating DevOps overhead.

Hosting dozens of sites on the free tier has worked smoothly without rate-limit or DDoS issues.

They run their static Jekyll site on GitHub Pages and like it, but want a host for larger resources like a photo blog.

Got an unexpected 1,141.89 dollar Vercel bill, mostly Fast Data Transfer (1,031) and Edge Requests (87), for a Next.js site with static pages and an ISR blog.

Had a similar surprise Vercel bill before and, after contacting support and describing the situation, got a 50 percent discount on the invoice.

Says Vercel support does a one-time waiver for surprise bills that do not track normal usage; two employees had this happen in the past year and it was waived quickly.

At a big tech company experimenting with Next.js, a 300,000 dollar Vercel bill landed in their inbox a few years ago.

Runs a startup with multiple users and decent scale on Vercel for about 150 dollars a month infrastructure plus 120 for v0 seats.

Netlify did not work out of the box for Next.js, needing the plugin installed manually plus a netlify.toml file, but then it worked and runs well; free tier lacks analytics.

First time using Cloudflare, found deploying a React/Vite fan app to Pages super easy, with only a ~$10 domain as cost.

Was charged about 6,000 dollars on a 20 dollar Vercel plan after a few million network requests with some large files, and says Vercel fights refunds; now pays a fixed 24 dollars on DigitalOcean.

An app with 30-50k monthly traffic but 600,000 daily bot hits cost 15 dollars on a VPS and 300 a month on Vercel, with about 10 dollars daily; quit after a few days.

Has published SvelteKit apps to Cloudflare Pages for years for free without issue: pushes auto deploy and are live within seconds with no config.

Uses OpenNext to deploy a large AI open source project on Cloudflare Workers and says it is working well.

Netlify changed its pricing so that every action, including production deploys, now consumes credits; the user found the free trial of the alternative worse than Netlify.

Recommends Netlify as pretty much a direct replacement for Vercel with a good free tier; the Next.js plugin installs automatically.

A developer finds Netlify super steady, with easy DNS, forms and redirects.

A developer prefers Cloudflare Pages over Vercel: easy to set and forget, a generous free tier, and sites running for years with no issues.

Is using Netlify with no issues at all until Cloudflare is ready for their needs.

Says Vercel gates Secure Compute behind Enterprise as a paid add-on, blocking small teams that need SOC2 compliance.

Self-hosts because Vercel at 20 dollars per user would cost about 140 a month for a team of seven, which they call borderline predatory.

Says Vercel works great in their experience, is easy and cheap and has a ton of features.

Hit the 10ms CPU limit on Cloudflare in a single test todo app and found the configuration obtuse and chaotic.

Uses Vercel for a large production front end with no issues and for proofs of concept, with free tier, custom domain and GitHub auto-deploy all easy.

Runs a SvelteKit app on Cloudflare Pages and found it very straightforward to set up.

They have hosted their site on Neocities for a year or two and use about 4.5 GB, and so far it has been great at roughly $5 a month. They were disappointed by the 100 MB per file limit when uploading larger media.

Hated it from the start and quit after a week or two, finding it cumbersome and more work than needed for simple processes.

Their business hosts four sites on Cloudflare Pages completely free with automatic preview deployments like Vercel, and received 250,000 dollars in Cloudflare credits.

A Next.js app worked fine on Cloudflare Pages for two years, but the forced move to Workers was slow, poorly documented and cost a morning, so they went to Vercel.

A new LLC owner hosted their hand-coded site on Cloudflare Pages/Workers with D1 storage for the contact form, for close to free.

Has felt locked into Vercel and obscured by edge requests issues, and will move off unless Vercel becomes more open about hosting elsewhere.

Hosts all hobby services on Vercel because the free tier costs nothing, and would likely stay as projects grow because it is easier.

Happy with Vercel for now because it lets them host React sites easily and for free.

Says that whatever else is wrong with Vercel, difficulty is not one of them: deploying a Next.js site there is trivially easy.

Got a 237 dollar Vercel Pro bill in six days for 25,000 visitors, driven by edge requests, data transfer and image transformations, projecting to about 1,200 a month.

Hit heavy egress charges and abusive traffic on Vercel with images and dynamic content, only fixed by caching and putting Cloudflare in front.

Uses Cloudflare Pages with GitHub Actions so pushes to the branch go live within about 30 seconds.

Has really enjoyed their experience with Netlify.

Spends about 1,000-1,500 dollars a month on Vercel and rates it great, but finds the enterprise sales people naggy and will probably eject once larger.

Happy they went deeper into Vercel: image optimisation got cheaper, fluid compute saves money, builds are cheaper and web analytics pricing dropped.

Got robbed on a Vercel bill when DDoS requests came through and Vercel did not bother refunding, so switched to DigitalOcean.

Small team chose Vercel and Next.js for very little setup and considers it the right professional choice despite disliking Vercel influence.

During the June 2025 Google outage they could not push a site update to Firebase from VS Code.

Switched to Cloudflare Pages with Eleventy after GitHub Pages needed a public repo, and it still works great and is free.

Hosts a vanilla HTML starter repo on Netlify for free and finds it extremely simple.

Hosts three 11ty sites on Netlify and loves it.

Builds a Next.js static site and hosts it on Cloudflare Pages for free.

Their multilingual site with a couple hundred sitemaps that cannot be statically generated is billed around 700 dollars a month by Vercel.

Runs headless Chromium PDF generation inside Vercel functions and says it works beautifully.

Vercel has done a decent job hosting their low-traffic portfolio site.

Loves Vercel deploys and starts everything there, moving bigger projects to Coolify later.

Runs two sites on Netlify and cannot fault them: point to the GitHub repo and it deploys in minutes with zero configuration.

Found Vercel hella expensive at 40-plus dollars a month for a site with 2,000-4,000 daily users with barely cacheable SSR, then moved to Fly.io for about 11.

Prefers Vercel over GitHub Pages because apex and www domains with SSL just work, and likes the easy-to-configure Vercel Analytics.

Uses custom GitHub Actions for Vercel deployments and says it works perfectly fine.

After trying many approaches, Vercel remains the platform that gives the most comfort: easy to deploy, friendly interface, CDN support and basic analytics, simpler than Cloudflare Pages.

Loves that Vercel just works out of the box with automatic deploys and a built-in CDN, but costs crept up once when image optimization, caching and serverless functions were not managed carefully.

Calls Vercel new pricing horrendous for paying customers and is canceling the subscription and moving files elsewhere.

Their team uses GitHub Pages at work for dozens of deployments, all built with Vite, without needing separate hosting.

Switched from Vercel, which charged about 300 dollars a month, to DigitalOcean at about 50 dollars a month and calls it the best decision.

A side project with barely any real traffic got a 949 dollar Vercel bill after upgrading to Pro when a crawler hit dynamic routes; support offered only 25 percent off.

After years on Vercel moved all apps to Cloudflare Pages with D1 and R2 for 5 dollars a month, with builds under 30 seconds, and will never look back.

Vercel protection was not good enough during an attack: more than a million edge requests in one hour, until Cloudflare rate limiting and rules in front fixed it.

Hit many build issues deploying a production Next.js monorepo to Cloudflare, with deployments breaking after code changes.

Still committed to Vercel and loves the platform, but per-seat pricing makes each new hire costly for a small startup.

Runs a Next.js 15 app with Auth.js and role-based access on Cloudflare without OpenNext.

Fought with next-on-pages on Cloudflare Pages before giving up because of the many limitations they had to build around.

Finds Vercel plenty competitive on pricing for what it offers and has never had cost be the bottleneck while scaling a startup.

Uses Vercel for personal projects and finds it far more straightforward to set up than their AWS SST deployment, without hitting prohibitive costs.

Rebuilt their Wix site with Bolt and deployed free on Netlify, paying only for the domain, with a result better than Wix.

Is a big fan of Cloudflare Pages for Next.js, cheaper and much less of a headache than Vercel.

Needed only custom SSL certificates but was quoted 20-25k a year for Vercel Enterprise versus about 70 a month on Pro.

Has many projects on Netlify and has never had to pay anything.

Came from Netlify to Cloudflare, finds it easier to use and simple to connect a custom domain.

A domain stopped working on Netlify out of the blue, the site was down for days and moving to Cloudflare Pages fixed it.

Uses Netlify mostly for Astro and Next.js sites with no billing issues.

Netlify took their site offline over a trademark complaint with zero communication, after which they moved to Cloudflare.

Standalone Next.js builds via GitHub Actions fail during deployment because the pipeline attempts to deploy nonexistent Azure Functions.

Sticks with Vercel managed infrastructure instead of paying a senior DevOps engineer, running a 10-person startup and even looking forward to a larger enterprise deal.

Finds Vercel a great developer experience but is annoyed by inevitable serverless cold starts and ridiculously expensive analytics and add-ons.

Pays only about 70 dollars a month on Vercel for around 500,000 monthly users.

Production workload that grew on Vercel hit a 2100 percent jump from Pro to entry enterprise, HIPAA entry cost-prohibitive and no native websockets, so Vercel is good only for dev/test.

Says Vercel charges for every function call, duration, feature and surge in traffic, more than anywhere else, and that it is not a serious platform for serious businesses.

Found Vercel MongoDB integration opens a new connection for every request; even with Fluid compute a mini DDoS hit the 500 connection limit, so they moved the app to Fly.io.

Has used Netlify for years without a single issue, though the thread now has them considering alternatives.

A static Next.js site hosted on Netlify works like a charm.

Gave up on Cloudflare because the Worker runtime could not run their PDF generation, so they containerized the app and hosted it elsewhere.

Runs 10 SvelteKit websites on Cloudflare Pages and finds them fast and is satisfied.

Runs a large SvelteKit app on Cloudflare Pages and calls it really cheap and fast, with rate limiting rules and no egress fees.

Moved from Netlify to Cloudflare and says they get all of the Netlify benefits for free.

After years on Netlify free they upgraded to Pro at 20 but were charged 44 because git contributors with a mismatched email count as members, and support refused to explain or downgrade.

A startup pays about 35 dollars a month plus occasional overages for Vercel, never thinks about frontend infrastructure, and says it never goes down while serving up to 1,000 visitors a day.

They hosted a social media site on Netlify, proxying requests to a separate backend to avoid CORS issues and cut backend load.

Moved from Cloudflare Workers to Vercel and found deployment ten times easier and bug free after constant errors connecting with Workers.

With millions of users, was unhappy with Vercel communication during a couple of outages last year given how much they pay, and tested an AWS SST backup that performed slightly better at a fraction of the cost.

Deployed a React app 15 times in two weeks using only 13 of 300 free build minutes and calls Netlify amazing.

Usually deploys on Vercel because the CI/CD pipeline and built-in security are really nice with great developer experience.

A recent Cloudflare advocate: Workers and Pages have been amazing, powering millions of requests a month for extremely cheap.

Uses Vercel with no issues for Next.js apps with millions of views a month; January cost about 220 dollars, with the main cost being edge requests, and it was pricier in early 2024.

Uses Cloudflare to host a React app in production and has never had any issues.

Uses Vercel for a Next.js frontend with around 800,000 page views a month without issues, with Cloudflare for DDoS protection and R2.

Found Vite React with Hono on Cloudflare Pages crazy fast, while Vercel seemed hit-or-miss with load times.

HTML, JS, and CSS files from a custom-built Angular 19 deployment randomly fail to load with 404 errors on every browser refresh.

Switched static pages to Cloudflare and finds the limits very generous.

Netlify siphoned off about 200 dollars a month for a static site updated every 15 minutes; GitHub Actions made it free.

Has had over a dozen sites on Netlify for six years, rarely paying more than 12 a month and mostly free, with one site at about 60,000 users a month.

Calls Netlify great and simpler to use than Vercel.

Moving many sites to it cut hosting costs by 60 to 70 percent compared to Vercel, but brought poor UX, slow builds and time-consuming configuration.

Their small portfolio site used about 25 GB of monthly downloads, over the no-cost plan limit, and they plan to leave. On the paid plan in the past they paid roughly 20-50 dollars a month.

They host a Next.js app on Firebase Hosting and say it works great, including preview hosting and the GitHub action for deployment.

Found working with Cloudflare Pages insanely frustrating, struggling for weeks to get SvelteKit set up and logging working.

Paid about 35 dollars per environment on AWS, which translated to 800 dollars in a single month on Vercel; calls Vercel expensive but a valid launchpad for operational overhead.

They value Deno Deploy as a reverse proxy with built in logging that they find less convoluted than Vercel.

They run three sites on AWS Amplify, one of them private, and are past the free tier. They have paid nothing beyond domain name costs.

They set up password protection on their Cloudflare Pages site and say it works fine.

As a developer needing a recent Node.js version they spent over a month getting a static web app running on Azure, versus two minutes locally.

Continuous deployment pipeline and monitoring were quick to configure right out of the box with minimal ongoing maintenance costs.

Runs about 30 Next.js sites for small businesses and finds Vercel cheaper than Netlify at that size, since Netlify pushes you to higher per-site function tiers.

Deploying a Next.js app fails with a 250MB function content size limit error even when the local build directory is only 110MB.

Has used Netlify for three years with thousands of monthly users and never needed more than the 19 dollar a month Pro plan.