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

Claude (Anthropic) with web search claude-opus-5 asked 2026-09-25

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 Pages / Workers - My default for most agency static work.
2. Cloudflare Pages mentioned
   Cloudflare Pages / Workers - My default for most agency static work.
3. Cloudflare Pages / Workers mentioned
   Cloudflare Pages / Workers - My default for most agency static work.
4. Workers mentioned
   Cloudflare Pages / Workers - My default for most agency static work.
5. Vercel mentioned
   DX is rougher than Vercel and framework support is uneven, so it's a worse fit for anything exotic.
6. Netlify mentioned
   Netlify - The best-balanced pick if you want a real platform rather than a CDN with a deploy hook.
7. Next.js mentioned
   Vercel - Take it when the work is Next.js, or when image optimization and the collaboration/preview UX are worth paying for.
8. Kinsta mentioned
   Kinsta Static Site Hosting - Up to 100 static sites from one account, Git-based deploys.
9. WordPress mentioned
   The specific reason to pick it: you're already on Kinsta for client WordPress and want one vendor, one invoice, one support contract.
10. GitHub Pages mentioned
    GitHub Pages - Free, trivial, fine for internal tools, docs, and throwaway campaign microsites.
11. AWS S3 + CloudFront mentioned
    AWS S3 + CloudFront (or Azure Static Web Apps) - Only when the client's procurement or security team requires the site to live in their cloud account.
12. S3 + CloudFront mentioned
    AWS S3 + CloudFront (or Azure Static Web Apps) - Only when the client's procurement or security team requires the site to live in their cloud account.
13. Azure mentioned
    AWS S3 + CloudFront (or Azure Static Web Apps) - Only when the client's procurement or security team requires the site to live in their cloud account.

Sources the engine cited

The answer, as recorded

Short version: for agency work the deciding factor usually isn't raw performance - it's per-seat pricing, how many sites you can park cheaply, and how cleanly you can hand a site off to the client later. Ranked on that basis: **1. Cloudflare Pages / Workers** - My default for most agency static work. Unlimited bandwidth on every tier including free, unlimited sites, and $5/mo for Workers covers edge compute for basically the whole portfolio. If you have 30 client brochure sites, most of them cost you literally nothing. DX is rougher than Vercel and framework support is uneven, so it's a worse fit for anything exotic. Handoff is easy too - clients can create their own Cloudflare account and you transfer the zone. **2. Netlify** - The best-balanced pick if you want a real platform rather than a CDN with a deploy hook. The key agency detail: Pro is a flat $20/mo for *unlimited* team members, vs. Vercel's $20 *per seat* - that's the difference between $20 and $200 for a ten-person shop. Built-in forms, identity, and scheduled functions kill a lot of small backend work on marketing sites, and deploy previews are a genuinely good client-review tool. **3. Vercel** - Take it when the work is Next.js, or when image optimization and the collaboration/preview UX are worth paying for. Best-in-class there, no argument. But per-developer pricing plus usage-based billing means bills can spike unpredictably, which is painful when you're reselling hosting at a fixed monthly rate. **4. Kinsta Static Site Hosting** - Up to 100 static sites from one account, Git-based deploys. The specific reason to pick it: you're already on Kinsta for client WordPress and want one vendor, one invoice, one support contract. **5. GitHub Pages** - Free, trivial, fine for internal tools, docs, and throwaway campaign microsites. Don't put a paying client's primary domain on it - no real redirects, no headers control, no preview deploys. **6. AWS S3 + CloudFront (or Azure Static Web Apps)** - Only when the client's procurement or security team requires the site to live in *their* cloud account. More setup, worse DX, but it sidesteps the "who owns the hosting account" fight entirely. One thing worth deciding before you pick: whether you're reselling hosting as a margin line or just billing build time. If it's margin, Cloudflare's economics are hard to beat. If you're passing hosting through at cost, Netlify's flat team pricing and forms save you more in labor than you'll ever save in bandwidth. Sources: - [Vercel vs Netlify vs Cloudflare Pages Pricing 2026 Compared](https://aibizhub.io/articles/vercel-vs-netlify-vs-cloudflare-pages-pricing-2026/) - [Netlify vs Vercel vs Cloudflare Pages: The Honest 2026 Comparison](https://toolchase.com/blog/netlify-vs-vercel-vs-cloudflare/) - [10 Best Static Website Hosting Providers in 2026](https://crystallize.com/blog/static-hosting) - [Best Static Site Hosting Platforms in 2026 (Free + Paid)](https://pandastack.io/blog/best-static-site-hosting-2026) - [Cloudflare Pages vs Netlify vs Vercel: Static Site Hosting Compared (2026)](https://danubedata.ro/blog/cloudflare-pages-vs-netlify-vs-vercel-static-hosting-2026)

Markdown edition · 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.