Cloudflare Workers

What it is

Cloudflare Workers runs JavaScript, TypeScript, Python and Rust apps on Cloudflare's network in hundreds of cities, with static assets, KV, D1 (SQLite), R2 storage, Durable Objects, queues and cron triggers alongside. Cloudflare Pages, the older static-site product, still works but Cloudflare now points new projects to Workers. Next.js apps deploy through the open-source OpenNext adapter (@opennextjs/cloudflare: App Router, SSR, ISR, middleware, 'use cache'; Node middleware experimental) or vinext, Cloudflare's Vite-based reimplementation of the Next.js API, which it recommends as the default but which is still in beta. Free: 100,000 requests a day, 10 ms of CPU time per request and 128 MB of memory, with requests to static assets free and unlimited. Workers Paid is $5 a month per account with 10 million requests and 30 million CPU milliseconds included, then $0.30 per million requests and $0.02 per million CPU milliseconds, with no charge for bandwidth or egress. Pages builds: 500 a month on Free, one at a time, 20-minute timeout. Checked on developers.cloudflare.com November 13, 2026.

Best for

• High-traffic sites where bandwidth bills are the problem
• APIs and apps that need low latency worldwide
• Teams already using Cloudflare for DNS and security

What we like

• No bandwidth or egress fees, and static asset requests are free
• Paid plan from $5 a month per account, not per seat
• Database, storage, queues and caching on the same network

What to watch

• Next.js is not native: it runs through the OpenNext adapter or vinext, which is still in beta
• Workers runtime is not full Node.js, so some npm packages need changes or do not work
• Free plan allows only 10 ms of CPU per request, too little for heavy server rendering
• Memory is capped at 128 MB per Worker on every plan