12 engineers on Hacker News describe using Cloudflare Workers first-hand: 5 endorse it, 2 regret it, 1 are mixed.
“Exception is Cloudflare Workers, which is well done with generous quotas”
endorse · production · mythz · 2025-11-05 · source ↗ · wrong label?“Our stuff on CF Workers has been working non stop for years now.”
endorse · production · pier25 · 2024-11-26 · source ↗ · wrong label?“DX rather than money has been the biggest reason we moved off CF offerings.”
regret · production · epolanski · 2023-12-03 · source ↗ · wrong label?“Workers is so fast, the data and website is updated in milliseconds.”
endorse · production · dalicommerce · 2022-12-17 · source ↗ · wrong label?“i would say this reduced the operational complexity by 2 orders of magnitude”
endorse · production · jFriedensreich · 2022-08-01 · source ↗ · wrong label?“been using Cloudflare workers but it kept timing out (going over 10s).”
regret · personal · yawnxyz · 2021-12-22 · source ↗ · wrong label?“We run censorship resistant proxies on Workers neatly domain fronted (well, IP fronted) by Cloudflare IPs. It works so well.”
endorse · production · ignoramous · 2020-11-13 · source ↗ · wrong label?“As a platform, workers have great promise... the documentation being too light to resolve corner case issues yourself, and support draws a big zero when it comes to Workers.”
mixed · production · redm · 2020-07-27 · source ↗ · wrong label?“It's one Cloudflare Worker with Workers AI and one KV namespace.”
neutral · production · yaskyj · 2026-09-29 · source ↗ · wrong label?“Everything is built using Cloudflare. We use Workers, D1, R2, Browser Rendering, AI Gateway, etc.”
neutral · production · slobodan_ · 2026-08-07 · source ↗ · wrong label?“we moved to an edge-first pattern with Cloudflare Workers”
neutral · production · suthakamal · 2026-03-21 · source ↗ · wrong label?“We do use workers, but with hono so it's easy to deploy it on render with node.”
neutral · production · saxenaabhi · 2025-11-19 · source ↗ · wrong label?