# Cloudflare Pages Canonical: https://inetgeek.com/hosting/cloudflare-pages/ Static and full-stack site hosting on Cloudflare's network, billed together with Workers compute. ## Who it suits Projects where the entire fixed cost should be a $5 monthly account minimum rather than a per-seat fee, and teams already running on the wider Workers platform. Billing is metered, so cost tracks traffic rather than headcount. Consider something else if Your repository is hosted somewhere other than GitHub or GitLab, or the free plan's 500 builds a month is not enough headroom. ## Adoption signals - Detected running on 58,440 live sites (BuiltWith, checked 2026-09-12) ## iScore 62 / 100 (80% interval 56–69), rank 4 of 6 in hosting — interval overlaps the next rank, so this is an ordering, not a finding. inetGeek's own reading, computed from sourced facts against category peers by disclosed rules. Not a provider claim. Intervals are 80%; a provider with few documented facts is pulled toward the category middle rather than scored on what little is known. Method: https://inetgeek.com/iscore/. Full output with every criterion's basis: https://inetgeek.com/scores.json. Every hosting peer ranked: https://inetgeek.com/hosting/cloudflare-pages/alternatives/ - Price: 82 (65–99), weight 25%, 5 of 5 criteria scored - Capacity and limits: 51 (45–57), weight 20%, 5 of 8 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: bandwidth_included, max_request_duration, regions - Capabilities: 69 (52–86), weight 20%, 4 of 10 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: autoscaling, managed_databases, persistent_processes, persistent_storage, scale_to_zero, streaming_response_limit - Trust and compliance: 54 (34–73), weight 15%, 2 of 10 criteria scored; scored for peers, not here — undocumented or stated without a number or a yes/limited/no: encryption_at_rest, gdpr_data_residency, hipaa_eligible, iso27001, pci_dss, private_networking, rbac, uptime_sla - Evidence: 90 (90–90), weight 10%, 4 of 4 criteria scored - Adoption: 10 (0–20), weight 10%, 1 of 2 criteria scored ## What the documentation says ### Pricing - Free tier: Yes ([source](https://developers.cloudflare.com/workers/platform/pricing/), read 2026-09-05) - Kind of free offer: Free tier ([source](https://developers.cloudflare.com/workers/platform/pricing/), read 2026-09-05) - Credit card to start: No ([source](https://www.cloudflare.com/products/pages/), read 2026-09-21) - Entry paid plan: $5 / month account minimum ([source](https://developers.cloudflare.com/workers/platform/pricing/), read 2026-09-05) - Pricing model: Metered usage with a $5 monthly account minimum ([source](https://developers.cloudflare.com/workers/platform/pricing/), read 2026-09-05) - Egress over allowance: No egress charge. Cloudflare states that requests to static assets are free and unlimited, and Pages Functions are billed as Workers — so bandwidth is not a metered dimension on either half of a Pages project. ([source](https://developers.cloudflare.com/workers/platform/pricing/), read 2026-09-07) - Startup credit program: Cloudflare for Startups: tiered credits up to $350k for a year, starting at $10k on Tier 3. ([source](https://www.cloudflare.com/forstartups/), read 2026-09-14) ### Limits - Memory (entry plan): 128 MB per isolate, on both the Free and Paid Workers plans. ([source](https://developers.cloudflare.com/workers/platform/limits/), read 2026-09-13) - Sites or apps included: 100 projects per account (platform-wide, all plans) ([source](https://developers.cloudflare.com/pages/platform/limits/), read 2026-09-14) - Monthly visits cap: No cap on static asset requests on any plan; requests to Pages Functions count against the Workers Paid plan quota ([source](https://developers.cloudflare.com/pages/functions/pricing/), read 2026-09-05) - File, inode or volume limit: 100,000 files per site on paid plans (20,000 on Free); maximum single asset size 25 MiB ([source](https://developers.cloudflare.com/pages/platform/limits/), read 2026-09-05) - Build allowance: 500 builds per month on the Free plan ([source](https://developers.cloudflare.com/pages/platform/limits/), read 2026-09-14) - Concurrent builds: 5 concurrent builds on Pro (1 on Free, 20 on Business), with 5,000 builds per month on Pro ([source](https://developers.cloudflare.com/pages/platform/limits/), read 2026-09-14) - Max request duration: No limit for HTTP requests. A Worker keeps running as long as the client stays connected; Cron Triggers, Durable Object alarms and Queue consumers are capped at 15 minutes. ([source](https://developers.cloudflare.com/workers/platform/limits/), read 2026-09-13) ### Execution - CPU time limit: Up to 30 seconds of CPU time under the Standard usage model, which the Pages docs state Pages supports. CPU time is tracked separately from duration in the Pages Functions metrics dashboard; the same page notes that network-bound work inflates duration but not CPU time. Not plan-differentiated on the page. ([source](https://developers.cloudflare.com/pages/functions/metrics/), read 2026-09-05) - Streaming response limit: No enforced ceiling. Cloudflare documents no response body size limit; CDN cache limits apply at 512 MB on Free, Pro and Business and 5 GB on Enterprise. ([source](https://developers.cloudflare.com/workers/platform/limits/), read 2026-09-13) - Managed connection pooling: Supported — Pages Functions with Hyperdrive bindings must be deployed with Node.js compatibility. ([source](https://developers.cloudflare.com/pages/functions/bindings/), read 2026-09-14) ### Deployment - Git deployment: Supported ([source](https://developers.cloudflare.com/pages/configuration/git-integration/), read 2026-09-14) - Scheduled jobs: Not supported ([source](https://developers.cloudflare.com/workers/static-assets/migrate-from-pages/), read 2026-09-14) ### Infrastructure - Edge network: Supported — Cloudflare's network page advertises deploying to 330+ cities. ([source](https://www.cloudflare.com/network/), read 2026-09-14) - Regions: No region selection. Pages Functions run in the data centre closest to the request; Smart Placement can instead pin a Worker near a named cloud region, host or hostname. ([source](https://developers.cloudflare.com/workers/configuration/smart-placement/), read 2026-09-14) - Uptime SLA: Cloudflare's Workers SLA promises 99.99% and says it applies to use of Workers only. Pages Functions run on the Workers runtime, but no SLA names Pages, so the commitment is not stated for this product. ([source](https://www.cloudflare.com/workers-service-level-agreement/), read 2026-09-14) ### CDN - Points of presence: 348 cities, counted in the Data Center Locations section of Cloudflare's network page. A banner on the same page says 330+. ([source](https://www.cloudflare.com/network/), read 2026-09-14) ### Support - Support on entry paid plan: Community forum and Discord on every plan, with Discord named as the Developer Platform channel. Opening a support case needs Pro or above — Free is limited to billing, account and registrar issues. Live chat starts at Business, emergency phone at Enterprise. ([source](https://developers.cloudflare.com/support/contacting-cloudflare-support/), read 2026-09-14) - Response time commitment: None on the $5/month Workers Paid plan Pages bills against: Cloudflare says pay-as-you-go and Free customers get no SLA and are answered in the order received. Priority response times are sold as the Premium and Enterprise SLAs — 1 hour and 2 hours for an urgent P1. ([source](https://developers.cloudflare.com/support/contacting-cloudflare-support/), read 2026-09-14) ## Compared with - [Cloudflare Pages vs Vercel](https://inetgeek.com/compare/vercel-vs-cloudflare-pages/) - [Cloudflare Pages vs Netlify](https://inetgeek.com/compare/netlify-vs-cloudflare-pages/) - [Cloudflare Pages vs Deno Deploy](https://inetgeek.com/compare/deno-deploy-vs-cloudflare-pages/) - [Cloudflare Pages vs Cloudflare Workers](https://inetgeek.com/compare/cloudflare-workers-vs-cloudflare-pages/) - [Cloudflare Pages vs AWS Amplify](https://inetgeek.com/compare/aws-amplify-vs-cloudflare-pages/)