About these scores

I’m James Ross — @CherryJimbo on X, and Cherry on GitHub. I have spent more than a decade running production infrastructure on Cloudflare — from the classic DNS-and-CDN basics through to building real products on Workers and the rest of the developer platform. That experience skews toward heavy, unglamorous workloads — the kind where a product’s sharp edges show up quickly.

Each product gets a single number: would I recommend it for production use today, out of 10? The score bundles together reliability, pricing honesty, developer experience, and how the product has trended over time. A low score doesn’t mean the engineering is bad — some of the lowest-scored products here are the most technically impressive. It means I’ve been burned operating it, or the pricing or maturity doesn’t hold up under real load.

How to read the numbers

• 8–10 — use it; I do, at scale, happily.
• 5–7 — genuinely useful, with caveats you should read first.
• 0–4 — fine for demos and experiments; I would not build production on it today.

Caveats, all of them

This is one operator’s anecdata. Your workload, plan tier, and tolerance for sharp edges will differ, and Cloudflare ships fast enough that any of these scores can be stale within a quarter — each page shows when it was last updated. Read these alongside Cloudflare’s own documentation, which is consistently excellent even for the products I score poorly.

This site is not affiliated with, sponsored by, or endorsed by Cloudflare, Inc. All product names are trademarks of their respective owners. No affiliate links, no sponsorships — just opinions.