Cloudflare Pages Free vs Vercel Hobby
For a static documentation site, portfolio, or landing page, start with Cloudflare Pages and count the build output before choosing. For a personal dynamic Next.js app, Vercel Hobby is an option if it fits its usage limits. For a commercial Next.js app, compare Vercel Pro with Cloudflare Workers. Vercel's Hobby terms restrict Hobby to personal or non-commercial use, regardless of whether the app fits the included traffic.
| What to check | Cloudflare Pages Free | Vercel Hobby |
|---|---|---|
| Builds and deploys | 500 builds/month; one build at a time per account | Up to 100 deployments/day |
| Custom domains | 100 per project | 50 per project |
| Static delivery | Free, unlimited asset requests that do not invoke Functions | 1 million CDN requests and 100 GB Fast Data Transfer monthly |
| Dynamic requests | 100,000 requests/day shared with Workers Free on the account | 1 million Function invocations/month, with separate CPU and memory allowances |
These are not equivalent meters: a Pages build is not a Vercel deployment, and a CDN request is not a function invocation. The limits above come from the Pages limits, Pages Functions pricing, and Vercel Hobby docs. Confirm which plan and billing mode your account uses before putting a launch budget behind these numbers.
Cloudflare Pages: Count files, builds, and requests separately
Count the files you ship, not the articles you write. A multilingual documentation site that generates an HTML document, a search record, and additional assets per page can hit the Free plan's 20,000-file limit well before it has 20,000 articles. Check the generated directory after a normal production build, including every locale, image variant, and client bundle. An individual 40 MiB video does not fit under the 25 MiB asset limit even if the rest of the site is tiny. Host that asset separately; if you choose object storage, it has its own meter. ToolPick's Cloudflare profile separates R2 storage and request costs from website plans.
Count previews as work for the build system. Forty production builds and 420 preview builds in a month leave 40 of the 500 builds on Free. An active preview URL is not the same thing as a free build every time someone updates a branch. Cloudflare documents GitHub and GitLab integration and branch controls. Bitbucket and self-hosted Git are not direct integrations. If the project needs to build from one of those repositories, start with Direct Upload and build in your own CI, rather than assuming you can switch an existing Git-integrated project to Direct Upload later.
Check which requests invoke code. A static site that serves 600,000 asset requests in a day does not touch the Functions request allowance if those requests bypass Functions. If the same site also handles 60,000 Function invocations and another Worker on the same account handles 30,000 requests, it uses 90,000 of the daily 100,000. Raise the Function traffic to 85,000 and the account reaches 115,000 even if every other day is quiet. The allowance resets at midnight UTC; unused requests on quiet days do not cover that peak.
With Functions present, the routing docs say they can be invoked by default for all requests. Inspect the generated _routes.json and verify that public assets bypass the function while routes that need authentication or personalization still invoke it. Don't apply a broad exclusion to a path just because it serves something that looks static.
Vercel Hobby vs Pro: When the bill starts
Do the eligibility check before any quota math. A personal experiment may fit Hobby. A commercial product cannot use Hobby just because it's a static landing page or because its request count is small. Vercel documents Hobby's included 1 million CDN requests, 100 GB Fast Data Transfer, and 1 million Function invocations as separate monthly allowances. Check the units too: 100 GB delivered to visitors is not the same as the 10 GB Fast Origin Transfer allowance, which concerns traffic between Vercel's network and its compute products. An image-heavy site and a lightly visited dashboard can hit different limits.
For commercial use, model Vercel Pro with one deploying seat at $20/month. Two paid deploying seats make the platform and seat charges $40/month before metered usage, add-ons, third-party services, and tax. Coworkers who only view deployments or comment on previews can use free Viewer seats; they cannot configure or deploy the project. One person with deployment access and four reviewers does not cost the same as five deployers. The plan includes $20/month of usage credit. It is for eligible usage, not a discount on the base fee or another seat. Compare the meters shown in your account rather than treating the included credit as an unlimited compute budget.
Cloudflare Workers Paid starts at $5/month per account; its Standard plan includes 10 million requests and 30 million CPU milliseconds per month. Those compute terms cover Pages Functions as well, but the $5 does not increase the Pages build allowance. At eight million dynamic requests a month and four milliseconds of CPU per request, the request count fits while the 32 million CPU milliseconds exceed the CPU allowance. Price the CPU overage separately, and budget databases and object storage according to their own plans. The example is a planning calculation, not a quote.
Static export is not full-stack Next.js
Use Pages for a static Next.js export. The Cloudflare Pages guide for Next.js points to its static export workflow. Run a production build and verify that the routes you need exist in the output, including deeper routes opened by a direct URL. If an account page or editor needs to read a session and fetch data when a request arrives, rebuilding a set of static files is not a substitute for that behavior.
Use Workers or Vercel for full-stack Next.js. Cloudflare's Next.js on Workers guide currently recommends vinext, labeled beta, and lists OpenNext as another deployment path. Evaluate that path separately from Pages. The part to compare is whether your pinned Next.js version, database driver and dependencies behave correctly in the target runtime, not whether the homepage comes up. Include authentication flows, a route handler, a Server Action, and revalidation only if they matter to your app. Test the Cloudflare candidate in its Workers preview runtime instead of taking success in the Node.js development server as proof.
Compare external state as its own migration. Vercel says that its old Vercel Postgres product is no longer available; existing databases moved to Neon in December 2024 and new projects can connect a Marketplace provider. Your plan estimate needs the chosen database provider's terms, not a Vercel Postgres line item. Before moving the frontend, use a non-production database to check the connection driver, regional latency, credentials configuration and who can restore the data. A successful preview that reads only fake data does not exercise the cutover dependency.
What to try before changing hosting
- Choose the route that would break the launch. For a static site, rebuild the largest locale, open a deep documentation URL directly, and check a 404 and a redirect. For a product, exercise sign-in and write one record through the same server path that production uses. A bare starter template does not test your decision.
- Measure the billing counters. On Pages, check which public asset routes invoke Functions and count the other Workers on the account. On Vercel, separate CDN requests, data transfer, and compute. Start with the busiest day you expect to handle, then build a monthly estimate from the observed traffic mix instead of assuming that every day matches your monthly average.
- Run one release with the actual roles. Have a deployer publish a preview and a reviewer open it. Verify that the preview cannot write to production. Record who owns the domain and who can revert the release. Before moving production, decide whether your rollback includes DNS, application code, and data schema; rolling back the app alone will not undo a data migration.
- Write down a stop condition. Stay on Pages for static content if it fits the build and file budget and your dynamic routes have clear headroom. Prefer Vercel Pro if its Next.js path covers a feature you need and Workers would require an unproven dependency replacement. Choose Workers over Pro only after the feature you depend on passes the runtime check and the estimated savings cover the work of migrating and maintaining the new setup.
For a live site, estimate the switch separately from the recurring bill. If a team saves $15 a month on the features it needs but spends $450 in engineering time to move its previews and release workflow, that is a 30-month payback before any savings are realized. Conversely, a clean static export with no server dependency may not require rewriting anything. Record the one-time cost and the monthly difference as separate figures, and keep the cheaper bill from deciding for you.
If preview workflow and full-stack Next.js support are the deciding factors, compare Vercel and Netlify as well. If you are also replacing the backend or need an always-running process, shortlist options in Vercel alternatives for Next.js before forcing that service into a static hosting plan. The hosting and data topic hub covers costs on the other side of that split.