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.