Initial setup for DO ft limits, WIP

Oxyjun · Oxyjun · commit de53f7ada01f · 2025-03-12T16:51:09.000Z
diff --git a/src/content/docs/durable-objects/get-started/tutorial-with-sql-api.mdx b/src/content/docs/durable-objects/get-started/tutorial-with-sql-api.mdx
@@ -26,15 +26,7 @@ The new beta version of Durable Objects is available where each Durable Object h
 
 <Render file="prereqs" product="workers" />
 
-## 1. Enable Durable Objects in the dashboard
-
-To enable Durable Objects, you will need to purchase the Workers Paid plan:
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
-2. Go to **Workers & Pages** > **Plans**.
-3. Select **Purchase Workers Paid** and complete the payment process to enable Durable Objects.
-
-## 2. Create a Worker project to access Durable Objects
+## 1. Create a Worker project to access Durable Objects
 
 You will access your Durable Object from a [Worker](/workers/). Your Worker application is an interface to interact with your Durable Object.
 
@@ -66,7 +58,7 @@ Move into your new directory:
 cd durable-object-starter
 ```
 
-## 3. Write a class to define a Durable Object that uses SQL API
+## 2. Write a class to define a Durable Object that uses SQL API
 
 Before you create and access a Durable Object, its behavior must be defined by an ordinary exported JavaScript class.
 
@@ -144,7 +136,7 @@ In the code above, you have:
 3. Returned an object representing the single row query result using `one()`, which checks that the query result has exactly one row.
 4. Return the `greeting` column from the row object result.
 
-## 4. Instantiate and communicate with a Durable Object
+## 3. Instantiate and communicate with a Durable Object
 
 :::note
 
@@ -201,7 +193,7 @@ In the code above, you have:
 
 Refer to [Access a Durable Object from a Worker](/durable-objects/best-practices/create-durable-object-stubs-and-send-requests/) to learn more about communicating with a Durable Object.
 
-## 5. Configure Durable Object bindings
+## 4. Configure Durable Object bindings
 
 [Bindings](/workers/runtime-apis/bindings/) allow your Workers to interact with resources on the Cloudflare developer platform. The Durable Object bindings in your Worker project's [Wrangler configuration file](/workers/wrangler/configuration/) will include a binding name (for this guide, use `MY_DURABLE_OBJECT`) and the class name (`MyDurableObject`).
 
@@ -221,7 +213,7 @@ The `[[durable_objects.bindings]]` section contains the following fields:
 - `class_name` - Required. The class name you wish to bind to.
 - `script_name` - Optional. Defaults to the current [environment's](/durable-objects/reference/environments/) Worker code.
 
-## 6. Configure Durable Object class with SQLite storage backend
+## 5. Configure Durable Object class with SQLite storage backend
 
 A migration is a mapping process from a class name to a runtime state. You perform a migration when creating a new Durable Object class, or when renaming, deleting or transferring an existing Durable Object class.
 
@@ -243,7 +235,7 @@ new_sqlite_classes = ["MyDurableObject"] # Array of new classes
 
 Refer to [Durable Objects migrations](/durable-objects/reference/durable-objects-migrations/) to learn more about the migration process.
 
-## 7. Develop a Durable Object Worker locally
+## 6. Develop a Durable Object Worker locally
 
 To test your Durable Object locally, run [`wrangler dev`](/workers/wrangler/commands/#dev):
 
@@ -253,7 +245,7 @@ npx wrangler dev
 
 In your console, you should see a`Hello world` string returned by the Durable Object.
 
-## 8. Deploy your Durable Object Worker
+## 7. Deploy your Durable Object Worker
 
 To deploy your Durable Object Worker:
 
diff --git a/src/content/docs/durable-objects/get-started/tutorial.mdx b/src/content/docs/durable-objects/get-started/tutorial.mdx
@@ -19,15 +19,7 @@ If you wish to learn more about Durable Objects, refer to [What are Durable Obje
 
 <Render file="prereqs" product="workers" />
 
-## 1. Enable Durable Objects in the dashboard
-
-To enable Durable Objects, you will need to purchase the Workers Paid plan:
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
-2. Go to **Workers & Pages** > **Plans**.
-3. Select **Purchase Workers Paid** and complete the payment process to enable Durable Objects.
-
-## 2. Create a Worker project
+## 1. Create a Worker project
 
 Durable Objects are accessed from a [Worker](/workers/).
 
@@ -59,7 +51,7 @@ Move into your new directory:
 cd durable-object-starter
 ```
 
-## 3. Write a Durable Object class
+## 2. Write a Durable Object class
 
 Durable Objects are defined by a exporting a standard JavaScript class which extends from the `DurableObject` base class.
 
@@ -126,7 +118,7 @@ export class MyDurableObject extends DurableObject {
 
 </TabItem> </Tabs>
 
-## 4. Invoke methods on a Durable Object class
+## 3. Invoke methods on a Durable Object class
 
 As mentioned previously, methods on a Durable Object class are invoked by a Worker. This is done by creating an ID refering to an instance of the Durable Object class, getting a stub that refers to a particular instance of a Durable Object class, and invoking methods on that stub.
 
@@ -174,7 +166,7 @@ export default {
 
 </TabItem> </Tabs>
 
-## 5. Configure Durable Object bindings
+## 4. Configure Durable Object bindings
 
 To allow a Worker to invoke methods on a Durable Object, the Worker must have a [Durable Object binding](/workers/runtime-apis/bindings/) in the project's [Wrangler configuration file](/workers/wrangler/configuration/#durable-objects). The binding is configured to use a particular Durable Object class.
 
@@ -197,7 +189,7 @@ The `[[durable_objects.bindings]]` section contains the following fields:
 
 Refer to [Wrangler Configuration](/workers/wrangler/configuration/#durable-objects) for more detail.
 
-## 6. Configure Durable Object classes with migrations
+## 5. Configure Durable Object classes with migrations
 
 A migration is a mapping process from a class name to a runtime state. You perform a migration when creating a new Durable Object class, or when renaming, deleting or transferring an existing Durable Object class.
 
@@ -217,7 +209,7 @@ new_classes = ["MyDurableObject"] # Array of new classes
 
 </WranglerConfig>
 
-### 6.a Optional: Configure new Durable Object class for SQL storage
+### 5.a Optional: Configure new Durable Object class for SQL storage
 
 :::note[SQLite in Durable Objects Beta]
 
@@ -243,7 +235,7 @@ new_sqlite_classes = ["MyDurableObject"] # Array of new classes
 
 Refer to [Durable Objects migrations](/durable-objects/reference/durable-objects-migrations/) to learn more about the migration process.
 
-## 7. Develop a Durable Object Worker locally
+## 6. Develop a Durable Object Worker locally
 
 To test your Durable Object locally, run [`wrangler dev`](/workers/wrangler/commands/#dev):
 
@@ -253,7 +245,7 @@ npx wrangler dev
 
 In your console, you should see a`Hello world` string returned by the Durable Object.
 
-## 8. Deploy your Durable Object Worker
+## 7. Deploy your Durable Object Worker
 
 To deploy your Durable Object Worker:
 
diff --git a/src/content/docs/durable-objects/platform/limits.mdx b/src/content/docs/durable-objects/platform/limits.mdx
@@ -8,7 +8,7 @@ sidebar:
 
 import { Render, GlossaryTooltip } from "~/components";
 
-Durable Objects are only available on the [Workers Paid plan](/workers/platform/pricing/#workers). Durable Objects limits are the same as [Workers Limits](/workers/platform/limits/), as well as the following limits that are specific to Durable Objects:
+Durable Objects limits are the same as [Workers Limits](/workers/platform/limits/), as well as the following limits that are specific to Durable Objects:
 
 | Feature                                  | Limit for class with key-value storage backend                   | Limit for class with SQLite storage backend [^1] |
 | ---------------------------------        | ---------------------------------------------------------------- | ----------------------------------------------- |
diff --git a/src/content/docs/workers/platform/pricing.mdx b/src/content/docs/workers/platform/pricing.mdx
@@ -174,6 +174,8 @@ Refer to [D1 Pricing](/d1/platform/pricing/) to learn more about how D1 is bille
 
 ## Durable Objects
 
+Durable Objects are available on both the [Workers Free](#workers) and [Workers Paid](#workers) plans.
+
 <Render file="durable_objects_pricing" />
 
 :::note[Durable Objects billing examples]
diff --git a/src/content/docs/workers/tutorials/deploy-a-realtime-chat-app/index.mdx b/src/content/docs/workers/tutorials/deploy-a-realtime-chat-app/index.mdx
@@ -16,8 +16,6 @@ In this tutorial, you will deploy a serverless, real-time chat application that
 
 This chat application uses a Durable Object to control each chat room. Users connect to the Object using WebSockets. Messages from one user are broadcast to all the other users. The chat history is also stored in durable storage. Real-time messages are relayed directly from one user to others without going through the storage layer.
 
-To continue with this tutorial, you must purchase the [Workers Paid plan](/workers/platform/pricing/#workers) and enable Durable Objects by logging into the [Cloudflare dashboard](https://dash.cloudflare.com) > **Workers & Pages** > select your Worker > **Durable Objects**.
-
 <Render file="tutorials-before-you-start" />
 
 ## Clone the chat application repository
diff --git a/src/content/partials/durable-objects/durable-objects-pricing.mdx b/src/content/partials/durable-objects/durable-objects-pricing.mdx
@@ -7,17 +7,14 @@ import { Markdown } from "~/components"
 
 ## Durable Objects
 
-Durable Objects are only available on the [Workers Paid plan](/workers/platform/pricing/#workers).
-
-
+Durable Objects are available on both Workers Free and [Workers Paid plans](/workers/platform/pricing/#workers).
 
 |                      | Paid plan                                         |
 | -------------------- | ------------------------------------------------- |
 | Requests<sup>1</sup> | 1 million, + $0.15/million                        |
 | Duration<sup>2</sup> | 400,000 GB-s, + $12.50/million GB-s<sup>3,4</sup> |
 
 
-
 <sup>1</sup> Requests include all incoming HTTP requests, WebSocket messages, and alarm invocations. There is no charge for outgoing WebSocket messages, nor for incoming [WebSocket protocol pings](https://www.rfc-editor.org/rfc/rfc6455#section-5.5.2).
 
 <sup>2</sup> Application-level auto-response messages handled by [`state.setWebSocketAutoResponse()`](/durable-objects/best-practices/websockets/) will not incur additional wall-clock time, and will not be charged.
diff --git a/src/content/partials/workers/durable_objects_pricing.mdx b/src/content/partials/workers/durable_objects_pricing.mdx
@@ -4,7 +4,7 @@
 
 import { Markdown, GlossaryTooltip } from "~/components";
 
-[Durable Objects](/durable-objects/) are only available on the [Workers Paid plan](/workers/platform/pricing/#workers), and are billed while the Durable Object is active (including the <GlossaryTooltip term="request context"> request context</GlossaryTooltip>).
+[Durable Objects](/durable-objects/) are available on both the Workers Free and [Workers Paid plans](/workers/platform/pricing/#workers), and are billed while the Durable Object is active (including the <GlossaryTooltip term="request context"> request context</GlossaryTooltip>).
 
 |                      | Paid plan                                                                                                                               |
 | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
