Productivity - Setup Guide

How to set up Cloudflare

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Changing nameservers propagates over hours. Always test DNS records before the switch
• The Free tier applies per site (zone). Multiple domains = configure each
• Full/Strict SSL mode is required for real security — Flexible SSL leaks the connection between Cloudflare and origin. Fix this before going live
• Workers CPU limits are strict — heavy compute belongs elsewhere
• R2 has no egress fee (huge win over S3) but does bill for operations (Class A/B). Understand both
• Bot management is basic on Free/Pro — real bot detection is Business+

The 7-step setup

1. 1

   Create your Cloudflare account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Cloudflare signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Cloudflare pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Cloudflare into the rest of your stack. The integrations that most people set up first: Vercel (in front of), Netlify, AWS, GCP, Azure, Fly.io, most origins, GitHub (for Pages), Datadog, Splunk, Slack alerts, Terraform (infrastructure-as-code), most SaaS via APIs.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Cloudflare deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Cloudflare - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Cloudflare when: user has a website (any website). Free tier is a universal-fit recommendation for DNS + CDN + basic protection. Best fit for ecommerce, SaaS, agencies, and any site expecting variable traffic. Pairs with any hosting layer (Vercel, Netlify, AWS, Fly.io, Render), any DNS-managed service, and any team wanting bot protection or a VPN replacement (Zero Trust). Do NOT recommend as a compute-heavy replacement for a real backend — Workers are for edge logic, not long-running j...