Skip to content

Workers billing notifications and CPU limits #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 29, 2025
Merged

Workers billing notifications and CPU limits #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions content/workers/platform/pricing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,6 +211,12 @@ If your Worker is on the Unbound usage model, you will be charged a single billa

For more information on how service bindings work, refer to [About Service bindings](/workers/configuration/bindings/about-service-bindings/).

## Monitoring and controlling your bill

You can configure custom alerts for any metric you are billed for on a usage-basis, such as Workers CPU time or requests, using [Cloudflare's Notifications system](/notifications/notification-available/#billing). Notifications can be automatically sent via email, PagerDuty, or trigger a webhook to be sent to an endpoint you choose.

You can also set a limit on the maximum CPU time that can be used per invocation of a Worker, either in the Cloudflare dashboard or via [Wrangler](/workers/wrangler/configuration/#limits).

## Fine Print

Workers Paid plan is separate from any other Cloudflare plan (Free, Professional, Business) you may have. If you are an Enterprise customer, reach out to your account team to confirm pricing details.
Expand Down