What Claude (Anthropic) with web search answered for static site hosting (agencies) on 2026-10-01

Claude (Anthropic) with web search claude-opus-5 asked 2026-10-01

Coverage: Claude (Anthropic) with web search. Other engines not included.

The question asked, verbatim: best static site hosting for agencies

Brands named, in the order the engine gave

1. Cloudflare mentioned
   Cloudflare (Workers with static assets, or Pages) - my default for an agency running many client sites.
2. Workers mentioned
   Cloudflare (Workers with static assets, or Pages) - my default for an agency running many client sites.
3. Vercel compared
   The cost difference at scale is not subtle: modeled at 5TB bandwidth + 10M function invocations, it's roughly $250/mo on Cloudflare vs ~$2,200 on Vercel and ~$2,800 on Netlify.
4. Netlify compared
   The cost difference at scale is not subtle: modeled at 5TB bandwidth + 10M function invocations, it's roughly $250/mo on Cloudflare vs ~$2,200 on Vercel and ~$2,800 on Netlify.
5. Next.js mentioned
   Vercel - pick this when the work is Next.js, which is often enough.
6. AWS mentioned
   - AWS S3 + CloudFront - when the client's procurement or security team requires AWS, or you're inheriting an AWS estate.
7. AWS S3 + CloudFront mentioned
   - AWS S3 + CloudFront - when the client's procurement or security team requires AWS, or you're inheriting an AWS estate.
8. S3 + CloudFront mentioned
   - AWS S3 + CloudFront - when the client's procurement or security team requires AWS, or you're inheriting an AWS estate.
9. GitHub Pages mentioned
   - GitHub Pages - free, fine for documentation, internal tools, and your own agency microsites.
10. DigitalOcean App Platform / Render mentioned
    - DigitalOcean App Platform / Render - sane middle ground when a client site needs a small backend or database alongside static output and you don't want to think in edge-runtime constraints.
11. Render mentioned
    - DigitalOcean App Platform / Render - sane middle ground when a client site needs a small backend or database alongside static output and you don't want to think in edge-runtime constraints.
12. Webflow mentioned
    - Webflow or Framer - not static hosts in the Jamstack sense, but if the real requirement is "the client's marketing person edits pages without calling us," these end more agency retainers' worth of ticket volume than any CDN choice will.
13. Framer mentioned
    - Webflow or Framer - not static hosts in the Jamstack sense, but if the real requirement is "the client's marketing person edits pages without calling us," these end more agency retainers' worth of ticket volume than any CDN choice will.
14. Cloudflare Workers mentioned
    Default to Cloudflare Workers static assets for the bulk of the client portfolio, Netlify where you want the partner relationship and the forms/previews workflow to carry non-technical client review, Vercel reserved for Next.js-heavy flagship builds where the seat cost is absorbed into project budge
15. Cloudflare Pages compared
    - Cloudflare Pages vs Workers 2026 (https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/)

Sources the engine cited

The answer, as recorded

Searched. Quick caveat on sources: a lot of what ranks for this query is affiliate blogspam (Hostmora, PandaStack, etc. - I'd ignore "Hostmora" entirely, it's not a real agency platform). Here's what I'd actually name: ## The main three **1. Cloudflare (Workers with static assets, or Pages)** - my default for an agency running many client sites. Unlimited bandwidth and unlimited sites on the free tier, 500 builds/month, no commercial-use restriction, 300+ PoP network. The cost difference at scale is not subtle: modeled at 5TB bandwidth + 10M function invocations, it's roughly $250/mo on Cloudflare vs ~$2,200 on Vercel and ~$2,800 on Netlify. For agencies, that means a client's traffic spike never becomes an awkward invoice conversation. One thing to know: for *new* projects Cloudflare now steers you to **Workers with static assets** rather than Pages - Workers reached parity for static assets, SSR, and custom domains as of March 2026. Pages isn't formally deprecated and existing projects are fine with no migration deadline, but all new investment is going into Workers. Start new client builds on Workers. ([mecanik.dev](https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/), [cogley.jp](https://cogley.jp/articles/cloudflare-pages-to-workers-migration)) **2. Netlify** - the one with an actual agency motion behind it, which matters more than people expect. There's a formal Agency Partner Program: dedicated account manager, co-selling, lead sharing, up to 20% revenue share, plus a free Business license for your own site and a sandbox account for client proposals and pre-sales demos. Product-wise, Deploy Previews per PR are the best client-review mechanism in the category - you send a URL, the client comments, no staging server to maintain. Built-in forms and identity also kill off a surprising number of small custom builds on brochure sites. ([netlify.com/partners](https://www.netlify.com/partners/), [agency partner guide](https://www.netlify.com/blog/2021/07/19/the-agency-partners-guide-to-managing-client-projects-with-netlify/)) **3. Vercel** - pick this when the work is Next.js, which is often enough. Best-in-class DX, push-to-deploy, preview per PR. The agency problem is seat pricing: Pro is $20 *per developer* per month, so a five-person team is $100/mo before any usage, and bandwidth overages on top of that are where agency margins quietly go. Great for your flagship builds, expensive as a default for a portfolio of 40 small client sites. ([devtoolreviews](https://www.devtoolreviews.com/reviews/vercel-vs-netlify-vs-cloudflare-pages-pricing-comparison-2026)) One pricing correction worth making: several articles claim Netlify Pro is a flat $20/mo for an unlimited team vs Vercel's per-seat. That contradicts the per-member figure in the same roundups, and Netlify has historically priced Pro per member. Check [netlify.com/pricing](https://www.netlify.com/pricing/) directly before you build a quote around it. ## Worth naming for specific situations - **AWS S3 + CloudFront** - when the client's procurement or security team requires AWS, or you're inheriting an AWS estate. Cheapest raw storage/egress at volume, but you're building the CI/CD and preview workflow yourself. Bill it as infrastructure work. - **GitHub Pages** - free, fine for documentation, internal tools, and your own agency microsites. Not for client production: no real build config, no preview deploys, no support path. - **DigitalOcean App Platform / Render** - sane middle ground when a client site needs a small backend or database alongside static output and you don't want to think in edge-runtime constraints. - **Webflow or Framer** - not static hosts in the Jamstack sense, but if the real requirement is "the client's marketing person edits pages without calling us," these end more agency retainers' worth of ticket volume than any CDN choice will. Name them when the brief is a brochure site, not an app. ## What I'd do Default to **Cloudflare Workers static assets** for the bulk of the client portfolio, **Netlify** where you want the partner relationship and the forms/previews workflow to carry non-technical client review, **Vercel** reserved for Next.js-heavy flagship builds where the seat cost is absorbed into project budget. Separate from platform choice, the single most valuable operational habit: **put each client's production project on a billing account the client owns.** Running several clients' production sites inside one agency account makes per-client cost attribution guesswork and turns handoffs or offboarding into a migration. Netlify's own agency guidance says the same thing, and it applies equally on Cloudflare and Vercel. ([netlify.com](https://www.netlify.com/blog/2021/07/19/the-agency-partners-guide-to-managing-client-projects-with-netlify/)) Sources: - [Cloudflare Pages vs Workers 2026](https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/) - [Cloudflare Pages to Workers migration](https://cogley.jp/articles/cloudflare-pages-to-workers-migration) - [Netlify Partners](https://www.netlify.com/partners/) - [The Agency Partner's Guide to Managing Client Projects with Netlify](https://www.netlify.com/blog/2021/07/19/the-agency-partners-guide-to-managing-client-projects-with-netlify/) - [Vercel vs Netlify vs Cloudflare Pages pricing comparison 2026](https://www.devtoolreviews.com/reviews/vercel-vs-netlify-vs-cloudflare-pages-pricing-comparison-2026) - [Vercel vs Netlify vs Cloudflare Pages 2026](https://coderfile.io/blog/vercel-vs-netlify-vs-cloudflare-2026)

Near this answer

The same question, recorded on other dates: 2026-09-29, 2026-09-27, 2026-09-25, 2026-09-23, 2026-09-20, 2026-09-16, 2026-09-14, 2026-09-12, 2026-09-10, 2026-09-08.

static site hosting, asked for other audiences: startups (asked 2026-10-01).

Other categories with a recorded answer: api management platforms, application performance monitoring, ci cd platforms, code repository hosting.

Markdown edition · JSON record · the question page, with every recording · Answer Watch · AEO Watch

Answer Watch records what one AI answer engine said on one date, nothing more. Each page names the engine and the model, carries the date the question was asked, and lists the brands that appeared in the answer in the order the engine gave them, with the sources it cited. It is a measurement, not a ranking, not a recommendation and not a claim about the world. Brands that did not appear in an answer are not named on any public page. Coverage: Claude (Anthropic) with web search. Other engines not included.