CloudflarePages
title: Cloudflare Pages type: platform created: 2026-05-16 last_updated: 2026-05-16 related: ["Playradar"] sources: ["https://tanis.codes/posts/deploy-hugo-website-to-cloudflare/"] radar_quadrant: Platforms radar_ring: Assess radar_position: inner
A static site hosting platform operated by Cloudflare, offering CDN delivery, automatic DDoS protection, SSL termination, and CI/CD build integration. Positioned as a competitor to Netlify and Vercel for JAMstack deployments.
| Resource | Limit |
|---|---|
| Bandwidth | Unlimited (static files) |
| Build minutes | 500 per month |
| Custom domains | 100 per project |
| Files per project | 20,000 |
| DDoS protection | Included |
| SSL certificates | Included |
The free tier is sufficient for personal projects and low-traffic sites. There are no bandwidth caps on static asset delivery, which differentiates it from platforms that meter egress.
Cloudflare Pages connects to a GitHub or GitLab repository and triggers a build on each push. The build environment supports common static site generators including Hugo, Gatsby, Next.js, and Astro. Build output is deployed to Cloudflare's CDN edge network.
For Hugo, the build command is hugo --minify (optionally with a custom config file flag). The output directory is public/.
After the initial deploy, projects receive a Pages subdomain (project-name.pages.dev). Custom domains are added via CNAME DNS records pointing at the Pages subdomain.
Because Cloudflare acts as both the DNS provider and the CDN, domain configuration is tighter than on other platforms. Domains registered elsewhere must delegate nameservers to Cloudflare before the custom domain feature is available. Nameserver propagation typically completes within 15 minutes.
HTTP redirect rules (e.g., www to apex domain) are configured within the Cloudflare dashboard rather than via Hugo config or _redirects files.
Cloudflare Pages competes directly with Netlify and GitHub Pages for static hosting. The differentiator is Cloudflare's network (one of the largest CDNs globally) and the unlimited bandwidth on the free plan. The tradeoff is tighter coupling to the Cloudflare ecosystem, including DNS delegation as a prerequisite for custom domains.
Cloudflare Pages sits in the Assess ring of the Platforms quadrant, at inner position. First studied via the tanis.codes deployment guide on 2026-05-16; no personal deployment to date. The platform is mature, has a generous free tier, and requires no infrastructure management. Inner position reflects a clear, low-friction path to trial — deploying a static site requires only a GitHub repo and a Cloudflare account — and strong applicability to personal projects and documentation sites. The remaining gap before Trial is a completed deployment.
