Your hosting bill is only part of what a website costs. Someone must publish changes, fix broken forms, manage access, and keep the site working when a campaign brings more visitors. The right hosting platform makes those jobs manageable for the team you actually have.
Our recommendation: start with Vercel if your developer builds in Next.js and you want an easy way to review and release changes. Start with Cloudflare if your site mostly serves ready-made pages, or your developer wants to bring more infrastructure into one account. The lower subscription price matters most when it comes with a setup your team can maintain.
Which deployment platform fits your website?
Vercel and Cloudflare host websites and applications built with code. Neither is a direct substitute for the visual editor, templates, and content tools in Squarespace or Wix. You can pair hosting with a content management system so an owner can edit pages without changing code, but someone must build that connection.
If you want to design and manage the whole site yourself, our guide to drag and drop website builders is a better starting point. If a developer or agency is building your site, the choice here affects both their work and your running costs.
| Your priority | Our starting choice | Why it fits |
|---|---|---|
| A Next.js site with frequent changes | Vercel | Close framework integration and a convenient review workflow |
| A brochure site or static blog | Cloudflare | Attractive static asset delivery costs |
| One supplier for more infrastructure | Cloudflare | Compute, storage, and database building blocks |
| A small team reviewing an agency's work | Vercel | Preview deployments and collaboration tools |
| An existing, reliable Cloudflare Pages site | Keep it unless needs change | A migration needs a business benefit |
These are starting recommendations. A developer who already knows one platform well may deliver a simpler, cheaper result there than on an unfamiliar alternative.
Cloudflare Pages vs Vercel: include Workers in the decision
Cloudflare Pages is a service for deploying websites, with Pages Functions for server-side tasks. Cloudflare Workers can also serve static sites and run application code. Comparing only Cloudflare Pages with Vercel leaves out an important part of Cloudflare's current offering.
Static sites send visitors pages and files prepared in advance. Static site generators can turn a blog or company website into this kind of output. A member dashboard, by contrast, may need to retrieve account details each time someone opens it. That dynamic content brings compute and database work into the decision.
For a new project, ask your developer to evaluate Workers alongside Cloudflare Pages. For an existing Cloudflare Pages site, ask what a move would improve. Cloudflare provides a migration path, but routing, configuration, and preview environments have differences. A move should solve a real problem, such as a feature requirement or maintenance burden.
Choose Cloudflare Pages when its established workflow meets your needs and your developer can support it. Choose Workers when its application model better fits the planned site. In either case, separate the cost of serving files from the work of running code.
Free tier and paid pricing: compare the whole bill
Starting prices below are in US dollars, as listed in October 2026. They exclude taxes, optional services, and usage beyond included allowances.
| Plan or service | Starting cost | What to budget for |
|---|---|---|
| Vercel Hobby | $0 | Personal, non-commercial projects only |
| Vercel Pro | $20 per month | Additional deploying seats, usage, and add-ons |
| Cloudflare Workers Free | $0 | Request and compute limits |
| Cloudflare Workers Paid | $5 minimum per month per account | Extra compute and separately priced services |
Vercel's Hobby plan rules restrict the free tier to personal, non-commercial use. A business should budget for a suitable paid plan, even if its traffic is small. A free tier that can handle your visitors is not necessarily a plan that permits your use.
The Vercel Pro plan includes one deploying seat and $20 in monthly usage credit. Additional deploying seats cost $20 each; viewer seats are free. Two people who both need deployment access therefore start at $40 per month before extras. An owner who only reviews work may not need another paid seat.
Cloudflare Workers pricing starts at a $5 monthly minimum on the paid plan. Standard pricing includes 10 million requests and 30 million CPU milliseconds monthly; additional usage is metered. Pages Functions use Workers billing. Cloudflare's model separates this compute usage from static assets, whose direct requests are free and unlimited.
That makes Cloudflare attractive for static sites, but “unlimited bandwidth” does not mean an entire application has no costs or limits. Databases, uploads, image processing, and code execution need their own budget. The Workers free tier also has limits on dynamic requests; it is not simply the paid plan without a bill.
Estimate a normal month and a busy one
Ask for two estimates: expected usage and a campaign month with ten times the traffic. Include hosting, the content system, storage, email delivery, image optimization, and support time. A visitor can generate multiple requests, so monthly users alone cannot determine a reliable price.
A $200 maintenance task can erase months of savings on a small hosting bill. Equally, wasteful dynamic workloads can make an easy-to-use platform expensive. Cost efficiency means counting both developer time and service charges. Set alerts and agree who responds to them before surprise bills become an argument.
Framework support: what Next.js means for your team
Next.js is a framework developers use to build websites and applications. If your site uses it, framework support should carry real weight. Vercel supports Next.js directly, which is why we favor it for a small team that wants a familiar path from development to production.
The owner-facing benefit is fewer integration decisions for common features. Your developer may use the App Router for page structure, Server Components to prepare parts of a page on the server, and Server Actions to handle forms. You need those features to keep working as the site changes.
Cloudflare can host Next.js applications too. Its current Next.js guide recommends vinext, a Vite-based implementation of the Next.js API surface. It is in beta, and Cloudflare advises a compatibility check before adopting it for an existing production application. OpenNext remains a documented option for existing applications with migration gaps; static exports can also use Cloudflare Pages.
Before switching, ask the developer to demonstrate your actual framework features: App Router pages, Server Components, form submissions, login, images, and content updates. A page loading successfully does not prove that payments or fresh content work correctly. For a busy owner, a written compatibility result is more useful than a promise of zero configuration.
Deployment workflow and developer experience
A good developer experience should shorten the distance between “please change this” and a safe release. Vercel can create preview deployments from repository changes. A developer sends a pull request, and you review a preview URL before the change reaches the public site.
This is valuable for small teams because the owner can check copy, pictures, and forms without learning the code. Vercel wins our preference for a Next.js team that needs this review loop often. Cloudflare Pages and Workers also have Git-based deployment and preview options, so previews alone are not a reason to move a working site.
Ask your agency to show the whole deployment workflow: make a change, trigger a build with a git push, review it, publish it, and restore the previous version. Also ask who receives error messages when a build fails. The best developer experience is one your replacement developer can understand later.
Environment variables and account ownership
Environment variables hold settings such as an API address; secrets hold private credentials. Keep test and live services separate. A review site should not send real customer emails or alter live orders. Have the developer document which settings apply during the build and which the running application needs.
Your business should control the domain, hosting account, source repository, and billing access. Give contractors their own access instead of sharing an owner's password. This matters more to long-term control than the hosting platform's dashboard design.
Edge functions, Fluid Compute, and performance
Serverless functions run application tasks without your team maintaining a traditional server. Edge functions place suitable work across a distributed network. Cloudflare Workers run code across Cloudflare's network; Vercel offers several runtimes and deployment choices. “Edge” alone does not tell you where every database query happens.
Vercel Fluid Compute improves resource use by letting supported Node.js and Python functions handle concurrent requests within an instance. Fluid Compute also includes cold-start optimizations. It is more useful to assess that current model than to assume every request starts a separate, slow server.
For your developer, the practical questions are runtime limits, package compatibility, and where data lives. Edge functions can suit lightweight request handling, while other workloads need different resources. An edge runtime close to a visitor may still wait for a distant database. Fluid Compute and edge functions are tools for different constraints, not a universal speed ranking.
How to judge the best performance
Test your important pages from places where customers live. Compare a cached article, a first visit, a login, and a form submission. For a global audience, globally distributed delivery helps with static content, but slow third-party scripts and oversized images can still dominate the experience.
Treat performance benchmarks as useful only when the workload resembles yours. The number of edge locations cannot tell you how quickly a customer finishes a booking. Give priority to page usability, completed actions, and error rates under load.
Storage, security, and room to grow
Cloudflare's appeal extends beyond hosting. R2 stores files and supports the S3 API; D1 provides a SQL database; KV stores key-value data; Durable Objects coordinate state for applications. Message queues can move work out of a visitor's immediate request. These building blocks let a developer assemble more of a system with one supplier.
Jodi Bando's experience highlights the value of that consolidation. For a smaller business, the useful question is which services you would actually bring together. An ordinary company site may need very little of this. A member platform with uploads and shared live state may have a reason to evaluate R2 and Durable Objects.
Vercel also offers storage products and database integrations, including options through its Marketplace. Having several providers can be sensible when your team already knows those services. Compare the total setup, account ownership, backup process, and support responsibilities.
Security deserves the same practical approach. Look at DDoS protection, firewall controls, bot management, and access to preview sites in the exact plans you are buying. Platform protection does not fix weak application permissions. Ask who patches dependencies, reviews alerts, and checks that one customer cannot access another customer's records.
Choose Vercel or choose Cloudflare?
Choose Vercel when your developer works in Next.js, your team makes frequent changes, and a smooth review process is worth the paid plan. Vercel remains our starting recommendation for that small-team scenario. Its developer experience can be a business advantage when it saves paid hours.
Choose Cloudflare when static sites and economical delivery are central, or a capable developer wants to combine hosting with more infrastructure services. For high traffic sites, model requests, compute, and storage before assuming the lower entry price guarantees a cheaper application.
Before committing, require a working version of your key customer journey, a monthly cost estimate, a clear maintenance owner, and a recovery plan. If you already have reliable hosting, measure the benefit of moving against the migration cost. The right platform should make the next year of running your website easier.
Frequently asked questions
Is the free tier enough for a business website?
Capacity and permitted use are separate questions. Vercel's free tier is for personal, non-commercial projects. With Cloudflare, check the terms and quotas of every service your business needs. A free plan for static hosting does not cover every possible backend service.
Will moving from Cloudflare Pages to Workers improve SEO?
A hosting move alone offers no ranking guarantee. Preserve URLs, redirects, page content, and indexability. Fix speed or reliability problems that affect visitors, and test important pages before switching the domain. Cloudflare Pages can already serve fast static sites.
How hard is it to leave either platform?
Simple static assets are usually easier to move than an application tied to platform-specific services. Ask which code depends on storage APIs, caching behavior, or serverless functions. Keep exports and backups, then budget for rebuilding those connections as part of any migration.