I Built 24 APIs on Cloudflare Workers — Here's What I Learned (And What I'd Do Differently)

Over the past several months, I built and shipped 24 production APIs on Cloudflare Workers. All are live on RapidAPI. Some get traffic. Some don't. Here's an honest breakdown of the architecture decisions, the surprising wins, the frustrations, and what I'd change if I started over. Why Cloudflare Workers? My constraint: I wanted zero fixed infrastructure costs while I validated whether anyone would actually pay for these APIs. Workers fit that perfectly: 100,000 free requests/day — enough to test and iterate without paying anything No cold starts (unlike Lambda) — requests wake in under 5ms Global edge — 300+ locations, sub-50ms P99 for most endpoints No server to maintain — deploy with wrangler deploy , done The tradeoff: Workers run in a V8 isolate, not Node.js. No native modules, no filesystem access, CPU time capped at 10ms (50ms on paid plans). If you need to run Puppeteer or ffmpeg, Workers isn't your answer. The API Portfolio Here's the full list across categories: Data & Looku