Cloudflare Cost Optimization
OhChimp reads your Cloudflare account and zone plans, sums a monthly run-rate, and surfaces Workers and R2 usage. Savings verified against your real bill.
How does OhChimp connect to Cloudflare?
With a read-only Cloudflare API token. OhChimp calls the token-verify endpoint to confirm the token is active, then reads your account and zone plan subscriptions and your Workers and R2 usage analytics. The token needs three read-only scopes: Account Settings:Read, Billing:Read, and Analytics:Read.
Does OhChimp need write access or see my data?
No. The token is read-only. OhChimp reads billing metadata (rate plan, price, currency, frequency) and aggregated usage volumes (Workers request counts, R2 stored GB and operation counts). It never stores application data, secrets, or workload contents.
What Cloudflare costs can OhChimp actually reduce?
The plan side is where dollars are explicit: account subscriptions and paid zone plans, summed to a monthly run-rate with billing frequency normalized and mixed currencies flagged. On usage, OhChimp surfaces Workers request volume and R2 storage and operation counts so you can see what is driving the meter, including R2's free egress versus S3 or GCS.
Who applies the changes, and can they be rolled back?
You do. Each fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and OhChimp applies the matching code and infrastructure changes together. It is never an autopilot.
How are the savings verified, and what does it cost?
Against your real Cloudflare bill. A plan is marked VERIFIED only after 7 or more days, a drop of at least 10%, and 3 consecutive positive checks. Until then it stays flagged "not implemented." Pricing is a flat monthly fee, OhChimp never takes a cut of your savings, and paid plans carry a year-one ROI guarantee: a full refund of subscription fees if it does not pay for itself in the first 12 months.