AI that proposes. People who decide. A record of both.
The model has no write tool. Every change to Cloudflare goes through an approval card and the execution core, is read back, and is logged with who approved it and how to undo it. Costs are your provider’s, itemised.
Who CTOs, VPs of Engineering, solutions architects
What gets in the way
- Handing an AI tool the keys to production DNS and WAF
- No answer to “who changed this, and why”
- Opaque per-seat AI pricing on top of the model bill
What Zonesteward does about it
- The gate
Nothing writes without a human; impact classified on the server; high-impact changes need an acknowledgement; viewers can’t approve; DNS and bulk changes are admin-only. See it →
- Audit and access
Every attempt recorded with actor, payload, response and revert. Roles enforced at three layers. Share links scoped per client. See it →
- Cost you can see
Your Cloudflare token, your model key. Every call itemised by feature and model; billed to you by the provider at cost, never marked up. See it →
Try asking What would this WAF rule actually block? · Did that change take effect? Undo it.
All roles Agencies & MSPs · Security & SOC · Ops & Reliability · Network & Edge · Developers · DNS & IT admin · Support