Know about the Cloudflare overage before the invoice does — and optionally stop it

A sitemap gets crawled, a Durable Object alarm loops, a migration script reads a table with no index — and the bill is $800, $4,000, $34,000 before anyone looks. Usage Guard polls your account's usage metrics every 5–15 minutes, compares them with your own baseline, tells you which metric is spiking, and, if you let it, flips the switch you picked in advance.

Watch

Every 5–15 minutes, per metric, against your own last week: D1 rows read and written, Workers requests and CPU time, Durable Object requests and alarms, R2 Class A / B operations, KV writes, Queues operations, Workers AI neurons. A spike is relative to your baseline, not a fixed number.

Alert

Email plus Slack, Discord or Telegram — with the metric, the Worker or database, and the projected cost at the current rate. Several accounts in one view, so client work and side projects don't need separate logins.

Act (optional)

You choose the stop in advance: disable a Cron Trigger, remove a route, or flip a KV flag your Worker reads to degrade itself. Needs an API token you scope and can revoke. Not in the first version — Watch and Alert ship first.

What Cloudflare already does

Cloudflare added Budget alerts in April 2026 and turned them on by default in July. Per the docs they are “informational only” and send “a single email” when spend crosses a threshold. That covers the invoice total; it doesn't say which metric moved or act on your behalf. Usage Guard is the layer for that gap — if Cloudflare closes it, you'll hear it from me first.

Pricing (planned)

$12 / month single account · $29 / month up to 5 accounts.

Also exploring

Routing support@ through Cloudflare and reading it in Gmail? See Routed Inbox — a small shared inbox on Email Routing, no seat pricing.

Managing Cloudflare for many clients? See Zone Audit — config drift and baseline checks across accounts.