Cloudflare Workers

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

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.

• 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

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.

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.

A Worker does not boot a container. Cloudflare keeps V8 isolates warm and drops your script into one, so the thing everyone else calls a cold start mostly stops existing. That single choice is what separates Workers from Lambda@Edge and Fly.io Machines, and it is also the source of every constraint you will hit. There is no filesystem. Long-lived TCP connections are the exception rather than the norm. CPU time is budgeted per request rather than wall-clock time, so a slow origin does not bill you but a tight loop does. Node compatibility covers a large slice of the built-ins and plenty of pure-JavaScript npm packages, but it is a compatibility layer, not the native path. Middleware, API routing, and server rendering fit comfortably. Anything that shells out, holds a socket open for minutes, or pulls in a native module does not. Write to the web platform first and treat Node compatibility as the escape hatch.

D1, R2, KV, Durable Objects, and Queues attach to a Worker as bindings, injected objects rather than network clients you have to authenticate against. It is the most pleasant data access on any edge platform, and it is also where the lock-in lives, because those are Cloudflare APIs with no direct equivalent elsewhere. Keep them behind a thin data module and the rest of your code stays portable. That matters, because the handler itself is genuinely portable: Workers, Vercel Edge, and Deno Deploy are all V8 with fetch-style handlers, so request-handling logic moves between them with modest effort. The storage layer is the part that does not move. Pricing is usage-based on requests and CPU time with a free tier, there is no capacity to provision, and the curve stays kinder than Lambda at volume. Durable Objects in particular have no clean counterpart, so weigh that before you build coordination logic on top of them.

• Official homepage →

The 30-min call is where your edge runtime choice becomes a real architecture, an integration plan with your data layer + auth + build pipeline, and a price range you can take to your stakeholders.