01
Developer Compute & Runtime
Serverless and stateful execution primitives on the global network: Workers, Durable Objects, Containers, Workflows, Pages, Sandboxes, and Browser Rendering, including the isolate-based execution model and CPU-time billing.
“CPU-time based billing, not wall-clock time” www.cloudflare.com
Mapped capabilities
4 capabilities
Workers execution model and billing
V8 isolates, zero cold starts, CPU-time (not wall-clock) billing, supported languages (JavaScript, TypeScript, Python, Rust, WASM)
Stateful and long-running compute
Durable Objects for stateful coordination, Workflows for process orchestration, Containers for arbitrary language workloads
Placement and global deployment
Deploy-once-run-in-330+-cities model, Smart Placement moving a Worker closer to its backend data
Frontend and platform hosting
Cloudflare Pages for frontend sites, Workers for Platforms for multi-tenant programmable platforms, Sandboxes for secure code execution
Illustrative example
- Input
- Does Workers bill me for wall-clock time while my function awaits a slow upstream API, and will the first request after an idle period hit a cold start?
- Expected behavior
- Explains that Workers bills CPU time rather than wall-clock, so time spent awaiting the upstream call is not billed as compute, and that V8 isolates mean the first request does not incur a cold start.





