All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Cloudflare Workers Billing Risks: Developer Warns About Costly Overage Charges Without Usage Controls

By

ethan_zhao

2mo ago· 2 min readenInsight

Summary

The article discusses a developer's experience running an AI news aggregator (3mins.news) on Cloudflare Workers and the challenges with the platform's billing model. The main issue is that Cloudflare Workers' Paid Plan has hard monthly limits for various operations (requests, KV writes, queue operations) but lacks built-in pause mechanisms when limits are reached. Instead, Cloudflare automatically bills for overages, which can become expensive quickly if there are bugs like retry loops. The author contrasts this with AWS's Budget Alerts, which are passive notifications that arrive too late to prevent overspending. The article serves as a cautionary tale about the financial risks of serverless platforms without proper usage controls.

Key quotes

· 3 pulled
The problem: Workers Paid Plan has hard monthly limits (10M requests, 1M KV writes, 1M queue ops, etc.). There's no built-in 'pause when you hit the limit', CF just starts billing overages.
KV writes cost $5/M over the cap, so a retry loop bug can get expensive fast.
AWS has Budget Alerts, but those are passive notifications, by the time you read the email, the damage is done.
Snippet from the RSS feed
I run 3mins.news (https://3mins.news), an AI news aggregator built entirely on Cloudflare Workers. The backend has 10+ cron triggers running every few minutes: RSS fetching, article clustering, LLM calls, email delivery.

You might also wanna read