Workers
Your code, running at the edge — on demand or on a clock.
Per-tenant Cloudflare Workers your agent ships in a single upload. Each one runs as an isolate at every edge location, scales straight from zero, and can carry cron schedules for the background work no one wants to babysit a server for.
edge compute
Runs where your users are
Every invocation spins up an isolate at the nearest point of presence, so your handler executes a few milliseconds from the request instead of a round-trip to one home region. There is nothing to provision, autoscale, or keep warm.
- Served from every edge location, no region pinning
- Cold starts you won't notice, scales to zero
scheduled work
Cron without a crontab
Pin a Worker to a schedule and the platform fires its handler on your cadence — no box sitting idle between runs, no daemon to monitor. The scheduled invocation is fully detached from web traffic, so a slow nightly job never touches a live request.
- Standard cron expressions, multiple per Worker
- Background runs that never block your users
pricing
Pay for what runs
Workers come out of your plan's monthly bucket; past that, usage auto-buys from fluid credit. An idle Worker costs nothing — you only pay for what runs:
idle
$0 — nothing runs, nothing bills
active
metered per request, from your plan's bucket
A Workers offering hands your tenant its own Cloudflare Worker — a sandboxed JavaScript runtime that runs your handler at every edge location, not a single region. Your agent ships the script and the platform binds it to a managed route, so requests are served close to the visitor with no servers to keep warm.
Related
Edge runtime, Isolates, Per-tenant Worker, Managed route, V8
For more information, ask your agent.