Infrastructure
Cloudflare Workers
The cheaper edge, as long as you stay inside its shape.
- Score
- 5.0
- Status
- Still using
- Reviewed
What I tested
One edge function, same code, deployed on both Cloudflare Workers and Vercel Edge, measured across a full quarter of real traffic rather than a hello-world benchmark.
What worked
- Roughly 2.5x cheaper for this workload at real request volume. The published pricing is honest: 5 dollars a month plus 30 cents per million requests.
- Performance was stable at p95 across the quarter, which is the number that actually shows up in user complaints.
- The runtime constraints push you toward small, fast functions that do one thing. That turned out to be a good influence on the code.
What did not
- The constraints are real. Anything that assumes a fat Node process needs rewriting, and the edge cases in libraries show up late.
- Debugging across a distributed runtime is still worse than debugging a single server, no matter what the dashboard claims.
Verdict
The default choice for a cost-sensitive product with global readers. Budget real time for the first migration, then it is simply cheaper.