Start

Quickstart

Connect a Cloudflare account, set a budget, and arm your first hard cap in about ten minutes.

SignalFlare does two jobs. It watches your Cloudflare spend with a read-only token, and, if you opt in, it caps it: when a budget reaches 100%, it cuts the traffic behind the spend using a second, write-scoped token you control.

You can stop after step 3 and have alerts only. Steps 4 and 5 add the cap.

1. Create an account

2. Connect Cloudflare (read-only)

In Cloudflare, go to My Profile → API Tokens → Create Token → Custom token and add one permission:

Account · Account Analytics · Read

Scope it to the account you want watched, create it, and paste it into Accounts → Connect account. We verify it, keep only the last four characters for display, and start pulling usage from the start of the month. The first backfill can take a few minutes. More on the read-only token.

3. Set a budget

Under Budgets, set a monthly amount for the whole account or for one service (Workers, R2, KV, D1, Durable Objects). You get alerts at 50%, 80% and 100%, plus a forecast alert when the trend says you will cross 100% before month end. Add Slack, Discord or a webhook under Channels. Budgets and alerts.

4. Connect a write token for caps

Under Hard caps, add a second Cloudflare token with only the write scopes the actions need. It is stored apart from your monitoring token and used only when a cap runs, a dry run is tested, or you restore. Scopes per action.

5. Create, test and arm a cap

Pick a budget and an action (remove a Worker route, enable a WAF rule, pause cron triggers, or turn off workers.dev). The action starts as a dry run: run Test to see exactly which Cloudflare API calls would be made. When you are happy, Arm it by typing the confirmation. Hard caps.

That’s it. When estimated spend on that budget reaches 100%, the cap runs, your channels hear about it, and the dashboard shows a Restore button.

All spend figures are estimates from Cloudflare analytics: an early warning, not your invoice. Why.