Documentation
Everything you need to cap a Cloudflare bill.
Start with the quickstart. It takes about ten minutes to go from nothing to an armed cap.
Open the quickstartStart
- Quickstart Connect a Cloudflare account, set a budget, and arm your first hard cap in about ten minutes.
- The read-only token The one Cloudflare permission SignalFlare needs to watch spend, and how it is stored.
- Staging and fire drills Mark a Cloudflare account as staging, run fire drills that execute a cap live and restore it automatically, and practise on a demo app.
Caps
- Hard caps How caps work, the write token and its scopes, dry runs, arming, what happens at 100%, and restoring.
- What caps can and can't stop The honest boundaries of a SignalFlare hard cap, and what to do about the gaps.
- Cap recipes Cloudflare-native ways to stop spend with SignalFlare caps, each with what it breaks, how to undo it, its blast radius and the token scopes it needs.
- Webhook integrations The outbound webhook cap action - signed cap.fired, cap.restored and cap.dry_run events you can relay to feature flags, other clouds or runbook automation.
Alerts
Reference
- Budget status API Read a budget's level from your own code to degrade features before a cap is needed.
- Security How SignalFlare handles your Cloudflare tokens, your data and access within your team.
- Accuracy and estimates Why every SignalFlare number is an estimate, and how close it is to your invoice.
- Plans, billing and your account Trials, upgrades, cancelling, what happens to caps when a plan changes, exporting and deleting data.