cloudflare-workers.html

Cloudflare Workers

V8 isolates on 300+ PoPs. Sub-millisecond cold starts, lowest cost at scale, the edge default.

Quick facts

CategoryV8 isolate
LanguageV8 / TS / WASM
PricingFreemium
LicenseProprietary
Created2017
GitHub starsclosed
Cold startinstant
PoPs300+
Node-compatYes

What it is

Cloudflare Workers runs JavaScript / TypeScript / WASM in V8 isolates across Cloudflare's 300+ PoPs. Sub-millisecond cold starts (no cold start, really — isolates are pre-warmed). Free tier of 100k requests/day, generous paid tiers. Tight integration with D1, R2, KV, Durable Objects, Queues. The default edge runtime in 2026.

Best for

Edge-rendered apps that need sub-50ms response globally
API gateways and middleware (auth, A/B routing, header rewriting)
Cost-sensitive workloads — Workers pricing is meaningfully kinder than Lambda
Apps that pair Workers with D1 / R2 / KV for the full Cloudflare stack

When not to pick it

Skip Workers if you need full Node API compatibility — Node compat works but is the workaround, not the native path. Skip if your team values single-vendor avoidance and Cloudflare lock-in matters.

My take

Cloudflare Workers is the right default for edge runtime in 2026. The performance-per-dollar is unmatched. The runtime constraint (V8 isolates, not full Node) is a real but worthwhile trade-off.

Compare Cloudflare Workers side-by-side

Cloudflare Workers vs Vercel Edge Functions → Cloudflare Workers vs AWS Lambda@Edge → Cloudflare Workers vs Deno Deploy → Cloudflare Workers vs Fastly Compute → Cloudflare Workers vs Fly.io Machines → Cloudflare Workers vs Bun → Cloudflare Workers vs Vercel Edge Functions → Cloudflare Workers vs Akamai EdgeWorkers →

Similar tools you should also consider

Vercel Edge Functions

V8 isolates inside Vercel. Tight Next.js integration, smaller PoP network than Cloudflare.

Read the take →

Deno Deploy

V8 isolates from the Deno team. Web-standard APIs, cleaner runtime than Node.