Built by the person who needed it.
I run Cloudflare for an agency. Dozens of client sites, across several Cloudflare accounts, on a mix of Free and Pro plans, and a support queue that doesn't care which zone the problem is in. The dashboard is very good at one zone at a time, and I have never once had one zone at a time.
So I built the thing I wanted: somewhere I could ask "who is attacking us right now?" and get an answer across every zone, see traffic on one globe instead of forty tabs, and change a WAF rule on a client's production site without the sick feeling that comes from having no preview and no way back.
The part I'm proudest of is the part that says no. The model can only propose. It has no write tool to be talked out of. Every change goes through a human, gets checked against reality at execution time, gets read back from Cloudflare, and can be undone with a click. That's not a feature layered on afterwards — the architecture wouldn't work any other way.
Where it is
In production, running my own fleet daily, and being opened to a private beta of twenty agencies and MSPs who have the same problem. It is founder-built and founder-run. There is no team page because there is no team yet, and I'd rather tell you that than pretend.
The security page lists what's finished and what isn't. The writing is where I explain the decisions.
Get in touch
hello@zonesteward.com. I read all of it.