[Browser Rendering] pricing update (#23727)

* [Browser Rendering] pricing update

* Update src/content/docs/browser-rendering/platform/pricing.mdx

* Update src/content/docs/browser-rendering/platform/pricing.mdx

* Update src/content/docs/browser-rendering/platform/pricing.mdx

Co-authored-by: Kody Jackson <[email protected]>

* Fix ambiguity in table

* Changelog addition

---------

Co-authored-by: Kody Jackson <[email protected]>

Author: ToriLindsay

src/content/docs/browser-rendering/platform/pricing.mdx

@@ -5,4 +5,36 @@ sidebar:
   order: 31
 ---
 
-Browser Rendering service is currently available at no cost up to the [limits](/browser-rendering/platform/limits/) specified until billing begins. Pricing to be announced and we will provide advance notice before any billing begins.
+Browser Rendering is currently available at no cost up to the [limits](/browser-rendering/platform/limits/) specified, with billing beginning on August 20, 2025 at the following rates:
+
+| Plan           | Included duration                                                                 | Included concurrency                                                 | Price (beyond included) |
+|----------------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|----------|
+| **Workers Free** | 10 minutes per day | 3 concurrent browsers | N/A |
+| **Workers Paid** | 10 hours per month | 10 concurrent browsers (averaged monthly) | **1. REST API**: $0.09 per additional browser hour <br />**2. Workers Bindings**: $0.09 per additional browser hour <br /> $2.00 per additional concurrent browser |
+
+You can monitor your Browser Rendering usage in the [Cloudflare dashboard](https://dash.cloudflare.com). Go to **Compute (Workers)** > **Browser Rendering**.
+
+### Examples of Workers Paid pricing
+<br/>
+#### Example: REST API pricing
+If a Workers Paid user uses the REST API for 50 hours during the month, the estimated cost for the month is as follows.
+
+For **browser duration**:
+<br/>50 hours - 10 hours (included in plan) = 40 hours
+<br/>40 hours × $0.09 per hour = $3.60
+
+#### Example: Workers Bindings pricing
+If a Workers paid user uses the Workers Bindings method for 50 hours during the month, and uses 10 concurrent browsers for the first 15 days and 20 concurrent hours the last 15 days, the estimated cost for the month is as follows.
+
+For **browser duration**:
+<br/>50 hours - 10 hours (included in plan) = 40 hours
+<br/>40 hours × $0.09 per hour = $3.60
+
+For **concurrent browsers**:
+<br/>((10 browsers × 15 days) + (20 browsers × 15 days)) = 450 total browsers used in month
+<br />450 browsers used in month ÷ 30 days in month = 15 browsers (averaged monthly)
+<br/>15 browsers (averaged monthly) − 10 (included in plan) = 5 browsers
+<br/>5 browsers × $2.00 per browser = $10.00
+
+For **browser duration** and **concurrent browsers**:
+<br/>$3.60 + $10.00 = $13.60

src/content/release-notes/browser-rendering.yaml

@@ -5,14 +5,18 @@ productLink: "/browser-rendering/"
 productArea: Developer platform
 productAreaLink: /workers/platform/changelog/platform/
 entries:
+  - publish_date: "2025-08-20"
+    title: Pricing update to Browser Rendering
+    description: |-
+      * Billing for Browser Rendering starts on August 20, 2025, with usage beyond the included [limits](/browser-rendering/platform/limits/) charged according to the new [pricing rates](/browser-rendering/platform/pricing/).
   - publish_date: "2025-07-03"
     title: Local development support
     description: |-
       * We added local development support to Browser Rendering, making it simpler than ever to test and iterate before deploying.
   - publish_date: "2025-06-30"
     title: New Web Bot Auth headers
     description: |-
-      * Browser Rendering now supports [Web Bot Auth](/reference/automatic-request-headers/) by automatically attaching `Signature-agent`, `Signature`, and `Signature-input ` headers to verify that a request originates from Cloudflare Browser Rendering. 
+      * Browser Rendering now supports [Web Bot Auth](/reference/automatic-request-headers/) by automatically attaching `Signature-agent`, `Signature`, and `Signature-input ` headers to verify that a request originates from Cloudflare Browser Rendering.
   - publish_date: "2025-06-27"
     title: Bug fix to debug log noise in Workers
     description: |-