ZoneSteward: Cloudflare operations with a gate in front.
If you run many Cloudflare sites, you can ask questions in plain English and fix problems safely. The AI proposes changes, and a person approves each one.
- RoleProduct, architecture, design and engineering
- StatusPublic beta
- StackNext.js, React, TypeScript, Node, Claude API, SQLite
- PlatformCloudflare APIs, one VPS behind Caddy
The problem
Managing Cloudflare across many sites means a lot of dashboards, a lot of rules and a lot of risk. A wrong rule can take a site down, and an attack does not wait for someone to find the right page.
What it does
- Answers questions about traffic and attacks in plain language
- Shows live activity on a globe and helps investigate incidents
- Proposes WAF, rate-limit and cache rule changes
- Gives read-only share links for stakeholders
The design decision that matters
Every write needs human approval, an impact preview, read-back verification and a one-click revert. The model has no direct write path. It proposes, the server enforces approval, and the system checks the live ruleset afterward. This is the same pattern I recommend for any AI feature that can change something real.
How it runs
A single Node process on a server behind Caddy, supervised by PM2, with the origin sealed by Cloudflare Authenticated Origin Pulls. It is deliberately simple to operate.