Skip to content

Commit a47bcdd

Browse files
nevikashahelithrar
authored andcommitted
remove legacy pricing docs (#16950)
1 parent f2183b3 commit a47bcdd

File tree

1 file changed

+2
-91
lines changed

1 file changed

+2
-91
lines changed

src/content/docs/workers/platform/pricing.mdx

Lines changed: 2 additions & 91 deletions
Original file line numberDiff line numberDiff line change
@@ -10,17 +10,6 @@ description: Workers plans and pricing information.
1010

1111
import { GlossaryTooltip, Render } from "~/components"
1212

13-
:::caution
14-
15-
16-
All users on the Workers Paid plan have been **automatically migrated** from the Bundled and Unbound usage models to the [Standard usage model](https://blog.cloudflare.com/workers-pricing-scale-to-zero/) on March 1, 2024.
17-
18-
* To learn what this migration means for Workers pricing, refer to [Pricing](/workers/platform/pricing/).
19-
* To learn about how this migration impacts Worker limits, refer to [Limits](/workers/platform/limits/).
20-
21-
22-
:::
23-
2413
By default, users have access to the Workers Free plan. The Workers Free plan includes limited usage of Workers, Pages Functions and Workers KV. Read more about the [Free plan limits](/workers/platform/limits/#worker-limits).
2514

2615
The Workers Paid plan includes Workers, Pages Functions, Workers KV, and Durable Objects usage for a minimum charge of $5 USD per month for an account. The plan includes increased initial usage allotments, with clear charges for usage that exceeds the base plan.
@@ -37,13 +26,7 @@ All [Pages Functions](/pages/functions/) are billed as Workers. All pricing and
3726

3827
## Workers
3928

40-
Usage models are settings on your Workers that specify how you are billed for usage, as well as the upper [limits](/workers/platform/limits/#worker-limits) for how many milliseconds of <GlossaryTooltip term="CPU time" link="/workers/glossary/?term=cpu+time">CPU time</GlossaryTooltip> your Worker can use per invocation.
41-
42-
Users on the Workers Paid plan only have access to the Standard usage model.
43-
44-
Workers Enterprise accounts are billed based on the usage model specified in their contract. To switch to the Standard usage model, reach out to your CSM. Some Workers Enterprise customers maintain the ability to change usage models.
45-
46-
29+
Users on the Workers Paid plan have access to the Standard usage model. Workers Enterprise accounts are billed based on the usage model specified in their contract. To switch to the Standard usage model, reach out to your CSM.
4730

4831
| | Requests<sup>1</sup> | Duration | CPU time |
4932
| ------------ | ------------------------------------------------------------------ | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
@@ -52,7 +35,7 @@ Workers Enterprise accounts are billed based on the usage model specified in the
5235

5336
<sup>1</sup> Inbound requests to your Worker. Cloudflare does not bill for [subrequests](/workers/platform/limits/#subrequests) you make from your Worker.
5437

55-
### Example pricing: Standard Usage Model
38+
### Example pricing
5639

5740
#### Example 1
5841

@@ -113,78 +96,6 @@ If you had a Worker on the Bundled usage model prior to the migration to Standar
11396

11497
:::
11598

116-
### Deprecated usage models
117-
118-
119-
120-
| | Requests<sup>1</sup> | Duration | CPU time |
121-
| ----------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
122-
| **Bundled** | 10 million included per month <br /> +$0.50 per additional million | No charge for duration | 50 milliseconds CPU time per invocation |
123-
| **Unbound** | 1 million included per month <br /> +$0.15 per additional million | 400,000 GB-s included per month <br /> +$12.50 per additional million GB-s<sup>2, 3</sup> | 30 seconds of CPU time per invocation <br /> 15 minutes of CPU time per [Cron Trigger](/workers/configuration/cron-triggers/) or [Queue Consumer](/queues/configuration/javascript-apis/#consumer) invocation |
124-
125-
126-
127-
<sup>1</sup> Inbound requests to your Worker. [Subrequests](/workers/platform/limits/#subrequests) to external services are not billed on a unit basis, but do impact the duration (wall-clock time) of your Worker.
128-
129-
<sup>2</sup> Cloudflare will bill for duration charges based on the higher of your wall time or CPU time, with a multiple of 8 applied to the CPU time to account for the processing power allotted to your Worker. Cloudflare will not bill for wall time duration charges beyond the execution [limit](/workers/platform/limits/#worker-limits) given.
130-
131-
<sup>3</sup> Duration billing will charge for the 128 MB of memory allocated to your Worker, regardless of actual usage. If your account has significant traffic to a single Worker, multiple instances of that Worker may run in the same isolate on the same physical machine and share the 128 MB of memory. These Workers are still billed as if they were separate instances, with each being charged as if it had its own 128 MB of memory.
132-
133-
#### Example pricing: Bundled Usage Model
134-
135-
A Worker that serves 100 million requests per month would have the following estimated costs:
136-
137-
138-
139-
| | Monthly Costs | Formula |
140-
| --------------------- | ------------- | -------------------------------------------------------------------------- |
141-
| **Workers Paid Plan** | $5 | |
142-
| **Requests** | $45 | (100,000,000 requests - 10,000,000 included requests) / 1,000,000 \* $0.50 |
143-
| **Total** | $50 | |
144-
145-
146-
147-
#### Example pricing: Unbound Usage Model
148-
149-
Consider a Worker that serves 100 million requests per month, with an average duration (wall-clock time) of 200 milliseconds per request. This translates to the following duration (wall-clock time) metrics:
150-
151-
* 0.2 seconds per request (200 milliseconds / 1000)
152-
* 0.025 gigabyte seconds (GB-s) per request (0.2 seconds \* 128 MB / 1024 MB)
153-
* 2,500,000 gigabyte seconds (GB-s) per month (0.025 GB-s per request \* 100,000,000 requests)
154-
155-
Resulting in the following estimated costs:
156-
157-
158-
159-
| | Monthly Costs | Formula |
160-
| --------------------- | ------------- | ------------------------------------------------------------------------- |
161-
| **Workers Paid Plan** | $5.00 | |
162-
| **Requests** | $14.85 | (100,000,000 requests - 1,000,000 included requests) / 1,000,000 \* $0.15 |
163-
| **Duration** | $26.25 | (2,500,000 GB-s per month - 400,000 included GB-s) / 1,000,000 \* $12.50 |
164-
| **Total** | $46.10 | |
165-
166-
167-
168-
### How to switch usage models
169-
170-
:::note
171-
172-
Only some Workers Enterprise customers maintain the ability to change usage models.
173-
:::
174-
175-
Usage models can be changed at the individual Worker level:
176-
177-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
178-
2. In Account Home, select **Workers & Pages**.
179-
3. In **Overview**, select your Worker > **Settings** > **Usage Model**.
180-
181-
To change your default account-wide usage model:
182-
183-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
184-
2. In Account Home, select **Workers & Pages**.
185-
3. Find **Usage Model** on the right-side menu > **Change**.
186-
187-
Existing Workers will not be impacted when changing the default usage model. You may change the usage model for individual Workers without affecting your account-wide default usage model.
18899

189100
## Workers Trace Events Logpush
190101

0 commit comments

Comments
 (0)