Cloudflare Recognizer
An open-source Workers + KV tool that polls Cloudflare analytics on a cron, tracks usage against a contract commit on a custom billing cycle, and alerts on surges, aimed at Enterprise accounts.
- Products
- WorkersKVR2Images
- Source
- Community resourceGitHub repository
- Author
- Bob Stolzberg (@BobStolzberg)
Key points
- The README says it runs on a scheduled cron, totals data transfer across zones, compares it with your commit, supports billing cycles anchored on a chosen day (for example the 15th to the 14th), and alerts by email or webhooks. It is Apache 2.0 licensed.
- The token it asks for is read-only: Account Analytics Read, Zone Analytics Read and Zone Read.
- The author’s blog adds surge detection comparing the current window with the previous one plus a volume noise floor, 50/80/100% commitment digests, five meters (bandwidth, Workers, R2, Images, Spectrum) and an MCP endpoint. He says it is not an official Cloudflare product, and that native billing alerts are currently disabled for Enterprise accounts (his claim).
Original sources
Undated
Cloudflare Recognizer
Open original sourceAn open-source Workers + KV tool that polls Cloudflare analytics on a cron, tracks usage against a contract commit on a custom billing cycle, and alerts on surges, aimed at Enterprise accounts.
The author’s write-up on why he built it and how the surge detection, alert routing and MCP server work.
Open original sourceThe author announces the open-source release on 𝕏.
Read on 𝕏Bob Stolzberg
@BobStolzberg · Original 𝕏 post
I built and open sourced a solution for a Fortune 5 to monitor their PB’s of Cloudflare holiday traffic and notify them Before the CDN bill blows up. Use Recognizer to tell you when your @Cloudflare bandwidth surges or you’re 50% away from your spend limits. Fully configurable. https://t.co/fMcox5Cjxm
The author’s reply lists the GraphQL datasets behind each meter: httpRequestsAdaptiveGroups, workersInvocationsAdaptive, r2OperationsAdaptive, imagesAdaptiveGroups and spectrumNetworkAnalyticsAdaptive.
Read on 𝕏Bob Stolzberg
@BobStolzberg · Original 𝕏 post
Multi-Product Grid Control (it’s in the blog post) and covers: 1. Bandwidth / Data Transfer: httpRequestsAdaptiveGroups (sum.edgeResponseBytes) 🌐 2. Cloudflare Workers Invocations: workersInvocationsAdaptive (sum.requests, CPU quantiles) ⚡ 3. Cloudflare R2 Object Storage: r2OperationsAdaptive (Class A writes, Class B reads, storage bytes) 🗄️ 4. Cloudflare Images & Transformations: imagesAdaptiveGroups (Resizing requests and delivery bytes) 🖼️ 5. Spectrum L4 Egress: spectrumNetworkAnalyticsAdaptive (TCP/UDP ingress/egress bytes) 📡
More to read
Why hard spending caps take time: Ashley Peacock on billing latency
Ashley Peacock (@ashleypeacock), who works on Durable Objects at Cloudflare, explains from experience why near-real-time spending caps are hard to build, says hard billing caps are coming soon, and suggests budget alerts plus issue alerts in the meantime.
A simulation game, a reported $4,483.74 in Durable Object reads.
Jonathan Mann (@songadaymann) reports spending $4,483.74 on Durable Object reads while building a simulation game. Rita Kozlov replies, “let us see what we can do”; Mann thanks her, and she replies that she is DMing him for details.
Lanshu: an AI-assisted Cloudflare billing risk checklist
Lanshu (@LufzzLiz) shares a six-step prompt for checking account ownership, usage, runaway consumption and budget alerts. Replies add alarm logging, email delivery checks and separate notifications.