ALERT — $8,000 Cloudflare bill detected — 03:47 UTC
Stop the
meltdown
before it starts.
Real-time Cloudflare cost monitoring. Workers AI, KV, D1, R2 — tracked live, alerted fast, before the invoice arrives.
// $0.011 / 1k neurons adds up faster than you think
Two ways in
Pick your setup
No account needed
We already made it.
You just say yes.
You just say yes.
Click below. Cloudflare opens with every permission pre-filled, named FlareUp, read-only. You tune it, accept it, or reject it — your call entirely. Copy the token, paste it in the dashboard. That's it. Close the tab after. Delete the token if you want. Zero strings.
1. click → CF opens, token pre-built
2. add, remove, or change anything
3. create → copy → paste here
4. close tab. delete token. done.
2. add, remove, or change anything
3. create → copy → paste here
4. close tab. delete token. done.
All permissions read-only — we pre-fill, you approve
Token in browser memory only — no database, no cookie, no log
Write access rejected on connect regardless of what you paste
Workers · KV · D1 · R2 · Workers AI · DO · Pages · Vectorize
Hosted alerts
We do it for you
Sign up once, connect your token. We handle the polling, the spike detection, the 3am alerts — all of it. Your token is encrypted in your browser before it ever reaches us. We store ciphertext. We run the numbers. You get paged. Delete your account and it's cryptographically gone — not policy-gone, gone.
→ token encrypted in your browser
→ we store ciphertext, never plaintext
→ we poll. we detect. we alert.
→ delete account = key unlocks nothing
→ we store ciphertext, never plaintext
→ we poll. we detect. we alert.
→ delete account = key unlocks nothing
Spike detection against your 7-day rolling average — fires at 3×
Budget tiers at 25% · 50% · 75% · 100% with per-tier webhooks
Slack · Discord · PagerDuty · any HTTP endpoint
Delete anytime — ciphertext gone, our key unlocks nothing
Prefer to run it yourself? Deploy to your own Cloudflare account. Your token never leaves your infra — not even a proxy hop. Runs on CF free tier. Costs you nothing except the setup.Self-host on GitHub →
What the token can actually read
Account AnalyticsUsage counts via GraphQL — not your data
BillingInvoice totals — how much you owe CF
Workers AINeuron counts per model
Workers KV StorageRead/write op counts — not key contents
Workers R2 StorageOp counts + storage GB — not file contents
D1Row read/write counts — not your rows
QueuesMessage op counts
StreamMinutes stored/delivered
Cloudflare ImagesImages stored + transformations
PagesBuild counts + deploy stats
Workers ScriptsScript names — not code
Workers ObservabilityCPU time, error rates
VectorizeQuery counts + dimensions stored
ContainersInstance counts + runtime
HyperdriveConnection counts
Browser RenderingSession counts
This is your accountant's view, not your admin's. Usage numbers and spend — not your DNS, not your code, not your stored data. You control every permission. Remove anything you're not comfortable with before creating the token. // write access of any kind is rejected on connect
Workers AI — the big one
Neurons bill at $0.011/1k. A busy llama-3.3-70b day can torch your free tier in minutes. FlareUp tracks by model, projects month-end, and fires before the damage is done.
Spike detection
Compares today's usage against your 7-day rolling average. If something 3× spikes — a runaway loop, a bot, a misconfigured retry — you hear about it in under 10 minutes.
Read-only by force
Your token is validated against the CF permissions API on connect. If it has write access — deploy, delete, DNS — FlareUp rejects it. Your infra stays untouchable.
KV · D1 · R2 · DO
Every billable Cloudflare product tracked. KV reads, D1 rows, R2 ops, Durable Object duration. One dashboard. One projection. No blind spots.
Alert tiers
Configure 25%, 50%, 75%, 100% budget tiers. Each tier fires its own webhooks, repeats on an interval, and can target different channels — #infra vs #on-call.
Zero infra overhead
Hosted alerts run on our infrastructure. Self-hosted runs on CF free tier. No database to manage, no relay to babysit, no monthly bill for the monitoring itself.
The incident that built this
SEV-1 BILLING INCIDENTdetected 03:47 UTC
serviceWorkers AI — @cf/meta/llama-3.3-70b-instruct
neurons_billed8,291,847,392
invoice_total$8,247.19
first_alert_sentnever
monitoring_toolnone
resolutionbuilt FlareUp
