Cloudflare Workers
Cloudflare · Also in Hosting and compute
Serverless functions on Cloudflare's global network, started in milliseconds with no cold-start containers.
100,000 per day
Requests
Resets daily
10 ms per request
CPU time
100 per account
Workers
- Card required
- Unknown
- Commercial use
- Yes
- Custom domain
- Yes
- Over the limit
- Pauses
Free limits
| Resource | Free amount | Resets | Type | Source |
|---|---|---|---|---|
| Requests | 100,000 per day | Daily | Free plan | developers.cloudflare.com · Verified 17 Nov 2026 |
| CPU time | 10 ms per request | Unknown | Free plan | developers.cloudflare.com · Verified 17 Nov 2026 |
| Workers | 100 per account | Unknown | Free plan | developers.cloudflare.com · Verified 17 Nov 2026 |
If you go over
Pauses. See the gotchas below for the details.
How it works
A Worker is a JavaScript, TypeScript, Python or WebAssembly function that runs in a lightweight isolate in every Cloudflare data centre. It handles HTTP requests, cron triggers and queue messages, and can call KV, D1, R2 and other Cloudflare services through bindings.
CPU time only counts the time your code is actually computing; waiting on a fetch or a database query does not count. Requests for static assets are free and unlimited.
What you can build
- APIs and webhooks at the edge
- Full-stack apps with static assets
- Redirects, A/B tests and header rewrites
Gotchas
- The 100,000 requests are per day, not per month, and reset at midnight UTC.
- Each request gets only 10 ms of CPU time on the free plan; heavy server-side rendering can hit it.
- Over the daily limit, requests fail with error 1027 unless the route is set to fail open.
Alternatives
- AWS Lambda · Run code in response to events or HTTP requests without managing servers; pay per request and per millisecond.
- Vercel Hobby · Free Vercel plan for personal projects: Git deploys, previews and serverless functions.