Matthew Prince on why Cloudflare offers a free version and always will (2016)

Original Article ↗ Hacker News Discussion ↗

Cloudflare’s promise to keep offering a free CDN tier prompts debate over how it can afford “unlimited” bandwidth and what trade-offs this model creates. Commenters note that raw transit is now extremely cheap at scale and argue that paid enterprise features, cross-subsidization and data network effects make the free tier sustainable, at least for now. Others worry that Cloudflare’s dominance turns it into an internet gatekeeper, enabling opaque blocking, privacy risks, de facto censorship and a future pivot toward more extractive pricing once growth slows.

Bandwidth economics and cloud pricing

  • Some argue most people overestimate bandwidth cost due to “big cloud” pricing; at scale, estimates like ~$1/TB (or even much less with large uplinks, peering, 95th-percentile billing) are mentioned.
  • Others respond that hyperscalers’ egress prices cross-subsidize very expensive global, low-latency, DDoS-resistant infrastructure, not just raw transit.
  • Disagreement on how relevant ad-funded piracy/streaming sites are as proof that high-quality, reliable bandwidth is cheap.

Cloudflare’s free tier and business strategy

  • The free tier is seen as smart: marginal cost per extra user is near zero, so free usage feeds growth and funnels a fraction into paid plans.
  • The scale of traffic is viewed as a valuable data source, including for training AI models, which further strengthens Cloudflare’s position.
  • Some note Cloudflare is widely used for early-stage projects and prototypes because it avoids upfront credit-card gating.

Onboarding, anonymity, and legal constraints

  • Cloudflare can be used with only an email, unlike most hosting that demands identity and credit cards. This is valued for anonymity and hobby projects.
  • Other providers (e.g., certain German hosts) reportedly require photo ID due to national telecom law, contrasting with Cloudflare’s lighter onboarding.

Centralization, privacy, and censorship concerns

  • Many worry Cloudflare has become a de facto gatekeeper: when it goes down, large swaths of the web fail.
  • Concerns include: pervasive CAPTCHAs (especially with privacy tools like iCloud Private Relay), user-agent discrimination, and opaque trust chains for non-technical users.
  • Fears that Cloudflare can effectively censor or deny service to legal but “unattractive” sites, while some illegal ones allegedly persist.
  • A few express extreme skepticism, speculating about intelligence-agency-style surveillance roles (presented as conjecture within the thread).

User experiences: performance, blocking, and alternatives

  • Some are highly enthusiastic: generous free tiers, good DX, easy deployment, and DNS/Pages/Workers praised.
  • Others report:
    • Being blocked from small blogs behind Cloudflare, sometimes seemingly due to over-aggressive default rules or geo/adblock/VPN filtering.
    • Persistent CAPTCHAs or “you have been blocked” pages.
    • “Phantom latency” of ~5–10ms or more, sometimes exacerbated by WAF rules or misconfigured cache rules.
  • A few prefer running their own edge/CDN stack for finer control and privacy, accepting more work and weaker DDoS protection.

Profitability and future “enshittification” risk

  • Multiple comments stress Cloudflare remains unprofitable and has raised significant external funding.
  • From this, some predict eventual price hikes or degradation of the free tier as investors seek returns.