Cloudflare

Founders note: I really love this solution. DNS hosting is blazingly fast and super easy to use—if any DNS setup service can be considered easy. The free tier is sugar-dad generous. The UI is not. It looks like a GCP or AWS clone, and it takes a bit to figure out it is not like those services. But with a little AI helper, I have seen non-techies make it rock.

What Cloudflare is

Cloudflare is one platform for apps, agents, and security at the edge: DNS, CDN, Pages (static sites and SPAs), Workers (serverless compute), R2 (object storage), KV, Durable Objects, and a long tail of Zero Trust and WAF products on the same network.

It sits in the same lane as Surge, Render, and Fly.io—hosting for the public internet—but like Render it supports static single-page apps and marketing sites and Workers for edge compute. Unlike Render, the control plane is deeper and the free tier is more aggressive.

First-login trap: the product map reads like big cloud—Compute, Storage, Network, Security—so your brain files it next to GCP or AWS. Wrong drawer. There are no servers to SSH into. Workers are not EC2. Pages are not S3 plus a load balancer. Budget time for that reframe; that is why time-to-wow scores low even when the free tier is generous.

Why I reach for it first

DNS. When you point a domain at Cloudflare, propagation feels instant compared to registrar-default DNS. For founders who change landing pages, subdomains, and email records during a launch week, that speed matters.

Free tier. Unmetered DDoS mitigation, universal SSL, global CDN, Workers daily requests, R2 storage allowances—the free plan is not a teaser. It is production-shaped. Sugar-dad generous.

Static + Workers on one network. Astro on Pages for this site and stephansmith.me. React SPA for Fractional.tools product UI. Workers when you want edge logic without a always-on server bill.

What it is not for

Not everything belongs on Cloudflare.

I could not run the Fractional.tools API here—it uses Express, and Workers are not Express-friendly. Long-lived Node servers with middleware stacks, calendar webhooks, and persistent connections belong on Fly.io. Cloudflare owns DNS, static front ends, and CDN; Fly owns the API.

Know the fork before you commit:

• Workers — fetch handlers, edge logic, agents, lightweight APIs rewritten for the Workers runtime.
• Fly / Render Web Services — traditional Express, Docker, cron on a real server process.

Do not drag an Express monolith into Workers and wonder why it fights you.

Cloudflare vs Render vs Surge vs Fly

Render is easier to click through cold. Cloudflare is more powerful once you accept the UI—or delegate it to an AI copilot with the MCP wired.

How we use it

On Fractional.tools: marketing site and product UI on Cloudflare; API on Fly.io; Postgres and auth on Supabase. This site—playbook included—is Astro on Cloudflare Pages, push to main.

In my own stack I run CDN, Workers, DNS, Routes, and analytics on Cloudflare—not one feature, a braid. That is the lock-in story: each piece works, each piece is generous, and together they make leaving feel irrational even when you know better.

See the tech stack map for the full picture.

Lock-in — the addictive part

Cloudflare’s depth score is a five because entanglement is the business model dressed as convenience.

Getting in is frictionless: point DNS, turn on CDN, add a Worker, wire a Route rule, glance at analytics—all free or cheap, all fast. Migrating out means moving DNS and edge cache and worker logic and route transforms and the analytics baseline you have been reading for a year. That is not a weekend.

Their goodness is addictive. You add one more product because it is right there and it works. Before your co-founder notices, Cloudflare is not a vendor—it is the front door to the internet for your company.

Mitigation: split on purpose early. Keep the Express API on Fly. Keep throwaway demos on Surge. Treat Cloudflare as the edge layer you choose to deepen—not the only place your code can live. Document what would break if you moved DNS tomorrow.

Pro tip — Cloudflare MCP

The dashboard is dense. The Cloudflare MCP (cloudflare-lccto in this workspace) is how you get prompt-to-prod: DNS records, Pages projects, R2 buckets, route tweaks—without tab-hunting in the dash.

Token in .env, reload MCP, ask Cursor to ship. That is how non-techies make it rock.

At a glance

• What it is: Edge network for DNS, CDN, SSL, DDoS, Pages (static/SPA), Workers (compute), R2 (objects), and more—one vendor from domain to deploy.
• Best for: DNS you want fast, static sites and SPAs on Pages, edge logic on Workers, founders who will pair the dash with AI, stacks that split static (Cloudflare) + API (Fly).
• Not a fit: Express monoliths and long-lived Node APIs (use Fly), founders with no AI copilot and no patience for product-name soup (use Render first), hot throwaway demos (use Surge), teams that cannot afford high lock-in across DNS + CDN + Workers + Routes + analytics.
• Pairs with: Astro for static publishing, Fly.io for the API layer, Cursor + Cloudflare MCP for dashboard bypass.

When to reach for it

Reach for Cloudflare when DNS speed and a generous free tier are non-negotiable—and when you are willing to either learn the product map or wire the MCP and let an agent drive. Split the stack: Pages for static, Fly for Express, Cloudflare for everything that should sit in front of users at the edge.

If your co-founder will never touch the dashboard and you will not give them an AI helper, start on Render and migrate DNS to Cloudflare later. You can have blazing DNS without moving the whole app on day one.

In Stephan’s MCP workbench: Stephan’s MCP workbench — background context and reads in Cursor, not emergency DNS surgery.

Related playbook entries

• Surge — static hot deploy before git-backed Pages.
• Render — simpler all-in-one dashboard when Cloudflare feels like too much.
• Fly.io — where Fractional.tools runs the Express API Workers will not host.
• Astro — static-first publishing pattern on Cloudflare Pages.

Tech Stack Clarity Check (15 min) — Book a slot if you want help drawing the Cloudflare vs Fly vs Render line for your stack—not resume comfort, actual ship path.

AI prompts for vibe coding