Cloudflare's Free Tier Is a Trap for Some Side Projects
Cloudflare's free tier looks like a zero-cost launchpad, but the moment a project needs real compute, stable mainland China access, or a payment method beyond Visa/Mastercard, the economics and logistics flip. Developers who skip the fine print end up with a site that works everywhere except where their users actually are.
Cloudflare's free tier — CDN, DNS, Pages, Workers, Tunnel, and object storage — can replace a VPS for personal sites, demos, and MVPs. GitHub integration and the Wrangler CLI let AI coding agents handle deployments directly from the terminal. Tunnel, in particular, makes exposing a local service to the internet trivial without opening ports or revealing the origin IP.
But the free tier has hard edges. Workers run in a V8 sandbox and cannot handle video transcoding, heavy data processing, or browser automation; those tasks require Containers, which start at $5/month with no free tier. R2 storage demands a payment card on file even for the free 10 GB, and the supported cards exclude Alipay, WeChat Pay, and UnionPay — a significant barrier for developers in mainland China.
Access from mainland China is the biggest practical problem: overseas traffic is fast, but domestic users often hit latency, instability, or outright unavailability depending on the ISP and time of day. Projects that hardcode local filesystem paths also break on Cloudflare's platform, requiring environment-aware rewrites that AI-generated code frequently misses.
Cloudflare's free tier is a global product with a regional blind spot: it works brilliantly for an audience outside China but creates a self-serve dead end for developers whose users are inside the Great Firewall.
The requirement to bind a foreign payment card for R2 and Containers is a quiet gate that filters out a large pool of Chinese solo developers before they ever hit a technical limit.
AI-generated code tends to litter projects with hardcoded local paths and temporary files, which collide directly with Cloudflare's stateless, no-filesystem execution model — a friction point that will only grow as agentic coding spreads.