What happened
If you had a surprise bill, we reconstruct it from your usage: which product, which path, when it started, and why nothing stopped it.
Risk review
Burned once is enough.
A one-off session for teams that got hit by a surprise Cloudflare bill, or don't want to be. We find what caused it, close the gaps, and set your caps with you.
Book a risk review Fixed fee, quoted up front · Read-only access
What we look at
Where it can happen again
Loop-prone code paths: Durable Object alarms, Queue retries, recursive fetches, cron schedules, D1 write patterns, crawler-facing dynamic routes.
Cloudflare settings
Caching, WAF and rate-limiting rules, CPU limits, workers.dev exposure and Custom Domains, checked against what your bill can tolerate.
Your caps, set with you
Budgets, dry-run-tested caps and status-API circuit breakers that match how your app is actually built, so a cap cuts the expensive path, not your whole product.
How it works
- 01
Tell us what happened
Email us a few lines. We reply with a fixed fee before any work starts.
- 02
Connect read-only
You connect a read-only token. We never need write access to review your account.
- 03
Walk through it together
A working session on a call, then a written report with every finding and fix.
- 04
Arm the caps
We help you set and test caps. You arm them yourself, with your own write token.
We'll tell you honestly if a bill looks like something to raise with Cloudflare support, and what to include. We can't promise a refund on their behalf, and we won't pretend to.