Static site hosting in 2026: Cloudflare vs Netlify vs Vercel (and why AI changes the math)

When you have a static site ready to publish —a business website, a blog, a landing page built in Astro—, one decision remains that almost nobody explains well to you: where to host it. The three options that dominate the conversation are Cloudflare Pages, Netlify and Vercel, and most of the comparisons you will find are in English and written for developers. This guide translates them into what really matters for a business: which comes out cheapest, which avoids surprise bills, and why AI crawling —a new factor in 2026— changes the math in favor of one of them.

We lay it out as an honest arbiter, not as a vendor for one platform: we are not hosting resellers and we are not tied to any provider. We build sites and deploy them wherever best suits each case, so we can tell you without bias where each one wins and where it does not. For the vast majority of static business sites, the conclusion is fairly clear, but it is worth understanding why, because the "why" is what protects you from overpaying or from getting a scare on the bill.

In one sentence: for a static site all three are equally fast; Cloudflare Pages wins on cost (unlimited bandwidth, no egress, no surprise bills), Vercel stands out for its Next.js integration, and Netlify for integrated features like forms; for an Astro site the three are equivalent, so you decide on cost, and there Cloudflare wins, especially now that AI crawling consumes bandwidth.

What really sets the three apart

Let us start with what matters, because all three platforms do the basics well —take your site, distribute it over a global network and serve it fast— and the difference is in the model, not the capability. Cloudflare Pages wins on cost structurally: its free plan offers unlimited bandwidth, with no egress charges, over one of the largest networks in the world, with attack protection included on every plan. Its reputation is for requiring a bit more initial configuration, but in exchange it delivers the lowest cost at any scale. When your traffic grows, its bill does not spike, because it does not charge by usage.

Vercel shines at something else: the developer experience, especially if your site is built in Next.js, with which it integrates like no other. It is excellent for applications, but its model charges per team member and by usage above certain limits, and its free plan is reserved for non-commercial projects. Netlify was the pioneer of this kind of hosting and still offers convenient integrated features —forms, identity, testing— but its credit-based billing has become confusing and several voices in the industry find it increasingly hard to recommend over the other two. For a pure static site, none of these differences shows up in speed; they all show up in the bill and in the features.

The uncomfortable honesty: surprise bills

There is a risk almost nobody warns you about when choosing your hosting, and it is worth facing head-on. On platforms that charge by usage, an unexpected traffic spike turns into an unexpected bill spike. If your site goes viral, if you suffer an attack that drives up requests, or if a crawler downloads your entire site many times, you end up paying for all that extra usage you did not plan for. It is not theoretical: there are documented cases that became sadly famous, like a project whose bill jumped to over a hundred thousand dollars from unexpected downloads, or a small studio that saw its weekly bill spike to tens of thousands when its traffic multiplied overnight.

The important part is not to panic, but to understand that this is avoidable by design. On a platform with unlimited bandwidth like Cloudflare, that chain —traffic spike turning into a giant bill— structurally cannot happen, because it does not charge for bandwidth usage. The best protection against a surprise bill is not checking the dashboard anxiously every day, it is choosing from the start a pricing model where the surprise simply does not fit. For a business that does not want to depend on luck or constant vigilance, that peace of mind has a concrete value.

The 2026 wedge: AI crawling consumes your bandwidth

Here is the new factor almost no comparison mentions yet, and that tips the scale even further. When AI crawlers and agents go through your site —to index it, to cite you in an answer, for an agent to buy in your store—, that traffic consumes bandwidth exactly like a human visit. And AI traffic is growing at an enormous pace: increases of several thousand percent over the last year are reported. On a platform that charges by usage, each of those passes adds to your bill, precisely when you most want AI to read you.

There an uncomfortable paradox appears on Vercel and Netlify: the success of being discovered by AI costs you money in bandwidth, and the more you are crawled and cited, the more you pay. On Cloudflare, with unlimited bandwidth, being crawled, cited and bought by AI is free, no matter how much that traffic grows. It is the same logic that runs through everything we write about architecture and AI visibility: the technical decision that seems minor —where you host— ends up affecting how much it costs you to be visible precisely in the channel that is growing fastest. That is why, for a business site that wants to be readable and citable by AI without it costing it, hosting with unlimited bandwidth stops being a technical detail and becomes a cost decision. We connect it with the rise of AI-mediated commerce and with the framework choice in Astro vs Next.js.

Why a static site barely needs a server

To understand why this hosting can be so cheap or free, it helps to see what is happening underneath, because that is where the connection with everything we defend about architecture sits. A static site is nothing more than a set of finished files —the HTML, the styles, the images— that the platform delivers as-is, without running code or querying a database on each visit. The server barely has to "think": it just takes the right file and serves it from a point near the visitor. That is why distributing it to millions of people costs so little, and why the free plans of these platforms are enough for most business sites.

Compare it with a WordPress site, which on each visit runs code and queries a database to assemble the page on the fly. That requires a more powerful and more expensive server, which can also buckle precisely when a traffic spike arrives —the worst moment to go down. The cost difference between hosting a static site and hosting a dynamic one is not a provider detail, it is a direct consequence of the architecture. So the same decision that makes a static site fast and readable to AI also collapses its hosting cost and removes the server as a point of failure. The question "which powerful server do I need?" is, for a well-built static site, almost always the wrong question: you need barely any, and that is precisely one of its biggest hidden advantages.

So, which do I choose?

The honest answer depends on your case, but for the vast majority of static business sites the framework is simple. If your site is static —and a content site in Astro is—, all three will give you the same speed, so you decide on cost and peace of mind, and there Cloudflare Pages tends to be the best choice: unlimited bandwidth, no surprise bills, and AI crawling at no cost. If your project is a Next.js application that needs the best developer experience with that framework, Vercel has a strong argument. And if you depend on specific integrated features like a ready-made forms or identity system, Netlify can be justified. Outside those particular cases, the default value is clear.

What makes no sense is choosing blindly, or staying on the trendy platform without looking at the billing model, because that is where the surprises appear. Just like with the framework choice, the principle is the same: the right tool for your case, decided on real criteria —cost, risk, features—, not by inertia. If all this sounds like more technical decisions than you want to make, that is exactly the part we solve for you.

What we do

So you know what to expect, we say it straight. We build your static site and deploy it on the platform that best suits it, usually Cloudflare Pages for cost and peace of mind, but Vercel or Netlify when a specific feature justifies it. We are not hosting resellers who push you to the same provider to charge you a margin, and since the domain and the accounts stay in your name, you are not locked in with us or with any platform. We hand you a site that is fast, cheap to maintain and free of surprise-bill risk, and we take on the technical configuration so you only see the result. The hosting decision, well made, is one of those that pay off quietly every month.

And it is, on top of that, a decision you almost never have to redo: settled well from the start, it goes along with you without causing trouble as your site grows. That is the difference between a technical detail handled in time and a headache that keeps coming back. Where you host is the last mile of a well-built site, and getting it right closes the loop on everything the architecture set out to do: a site that is fast for your visitor, readable to AI, and cheap to keep running no matter how much it grows. None of it is glamorous, and that is exactly the point: the best hosting decision, in the end, is the one you never have to think about again.