For Ops & Reliability

Alerts written from a sentence. Incidents with the evidence.

Every number Cloudflare exposes about a zone can watch itself: you describe what would worry you, the composer writes the rule and dry-runs it, and when it fires you get an incident with the investigation attached.

Who DevOps engineers, site reliability engineers, platform engineers

What gets in the way

  • Threshold maths and GraphQL for every alert, per zone
  • Pages with no context — what changed, who changed it, was it the origin
  • No printable incident record for the post-mortem

What Zonesteward does about it

  1. Alert rules in English

    Query, threshold, window and minimum volume written from your sentence, explained back to you, dry-run against live traffic before it’s armed. See it →

  2. Your channels

    Email through Resend, SendGrid, Mailgun or SMTP; Slack; Microsoft Teams; PagerDuty; SMS via Twilio; signed JSON webhooks. See it →

  3. Incident reports and audit

    Each incident carries what fired, what the investigator found, and every change made in the window — printable, with CSV. See it →

Try asking Is client.com down? · Warn me if cache hit ratio drops…

Alert rules, each explained in plain words
Alert rules, written from a sentence
Apply for beta → Free during the beta. Your own Cloudflare token and model key; nothing marked up.

All roles Agencies & MSPs · Security & SOC · Network & Edge · Developers · DNS & IT admin · Leadership · Support

  1. 01You
  2. 02Your fleet
  3. 03Fit
Who should we write back to?

Takes about two minutes.