DEV Community

Jianfang Peng
Jianfang Peng

Posted on

5 Cloudflare Free-Tier Tricks I Use to Run My Side Projects

Cloudflare's free tier is, pound for pound, the best deal in web infrastructure. Not "free trial" free — actually free, no card, no gotchas. Here are five things I genuinely run on it for my side projects.

1. Unlimited email addresses on my own domain (Email Routing)

This is the trick most people sleep on. Buy a domain for ~$10/year, add Cloudflare Email Routing, and suddenly shop@mydomain.com, support@mydomain.com, whatever-i-want@mydomain.com all work — forwarded to one real inbox. No mailboxes to pay for, no "5 free aliases" limits.

The setup takes about 10 minutes: verify the domain, add two DNS records (MX + SPF), write routing rules. I use one rule that catches everything not matching a specific address and forwards it to my main Gmail. Services that need a unique address per signup get a unique address. One inbox to rule them all.

2. DNS that isn't a footgun

Registrars ship DNS that's "fine" until it isn't — slow propagation, cryptic errors, no API worth using. Cloudflare DNS is free, fast, and has a real API with tokens you can scope per-zone. Everything lives in one dashboard with an audit log, so when something breaks at 2 AM you can see exactly who changed what.

3. Workers for the glue nobody wants to maintain

Need a tiny JSON API, a redirect service, or a webhook relay? A Cloudflare Worker is a few dozen lines of JavaScript and deploys in seconds. The free tier gives you 100,000 requests/day — more than any side project will touch. No server to patch, no container to restart, no bill.

4. Tunnel: expose localhost without exposing yourself

Developing a webhook integration and need a public URL for localhost:3000? cloudflared tunnel gives you a real HTTPS URL with zero port-forwarding, zero firewall rules, and zero "your home IP is now public" anxiety. It's the cleanest way to demo work-in-progress to a client.

5. Cache everything aggressively (then purge when you must)

The free CDN caches your static assets at 300+ edge locations. The part beginners miss: set real cache rules for images, CSS, and JS, then use "Purge Cache" (or the API) when you deploy. Most side-project slowness is just every request round-tripping to a cheap VPS — the free CDN deletes that problem.

The honest caveat

Free doesn't mean unlimited-everything. Email Routing is forwarding-only (no sending from those addresses without extra setup), Workers has CPU-time limits per request, and the free tier won't hide a genuinely terrible origin server. But for a side project doing normal side-project things, this stack covers DNS, email, glue code, demos, and caching for roughly the price of the domain alone.

Top comments (0)