Centralise message billing into platform pricing and add product-specific pricing pages

umair-ably · umair-ably · commit 031b0df037da · 2026-03-11T17:19:09.000Z
diff --git a/src/data/nav/chat.ts b/src/data/nav/chat.ts
@@ -220,8 +220,8 @@ export default {
       ],
     },
     {
-      name: 'Message billing',
-      link: '/docs/chat/message-billing',
+      name: 'Pricing',
+      link: '/docs/chat/pricing',
     },
     {
       name: 'Guides',
diff --git a/src/data/nav/platform.ts b/src/data/nav/platform.ts
@@ -125,6 +125,10 @@ export default {
           link: '/docs/platform/pricing/billing',
           name: 'Billing',
         },
+        {
+          link: '/docs/platform/pricing/message-billing',
+          name: 'Message billing',
+        },
         {
           link: '/docs/platform/pricing/limits',
           name: 'Limits',
diff --git a/src/data/nav/pubsub.ts b/src/data/nav/pubsub.ts
@@ -335,8 +335,8 @@ export default {
       ],
     },
     {
-      name: 'Message billing',
-      link: '/docs/pub-sub/message-billing',
+      name: 'Pricing',
+      link: '/docs/pub-sub/pricing',
     },
     {
       name: 'Guides',
diff --git a/src/pages/docs/chat/message-billing.mdx b/src/pages/docs/chat/message-billing.mdx
diff --git a/src/pages/docs/chat/pricing.mdx b/src/pages/docs/chat/pricing.mdx
@@ -0,0 +1,39 @@
+---
+title: "Pricing"
+meta_description: "Understand how Chat SDK features contribute to your message count, including messages, typing indicators, reactions, and cost optimization strategies."
+meta_keywords: "chat billing, message counting, typing indicators, reactions, chat pricing, cost optimization"
+intro: "How Chat SDK features contribute to your message count and strategies to optimize costs."
+redirect_from:
+  - /docs/chat/message-billing
+---
+
+The [Chat SDK](/docs/chat) is built on top of [Pub/Sub](/docs/pub-sub). All Chat operations generate Pub/Sub messages that follow the same billing rules.
+
+<Aside data-type="further-reading">
+For the complete reference on how all Ably operations count as messages, see [message billing](/docs/platform/pricing/message-billing). For package comparison and volume discounts, see the [pricing](https://ably.com/pricing) page.
+</Aside>
+
+## What counts as a message <a id="messages"/>
+
+Each Chat feature generates Pub/Sub messages. For example, 1 message sent in a room with 50 subscribers counts as **51 messages** (1 inbound + 50 outbound). Typing indicators are the most significant cost driver. In a room with 50 subscribers, one active typer generates approximately **306 messages per minute** from heartbeat events alone, plus a stop event.
+
+For the complete breakdown of how each Chat operation counts as messages, see the [Chat operations](/docs/platform/pricing/message-billing#chat-operations) table in the central message billing reference.
+
+## Channels and connection minutes <a id="channels-connections"/>
+
+Chat rooms map directly to Pub/Sub channels. Each room feature (messages, typing, reactions, presence, occupancy) uses underlying Pub/Sub channels. Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections) in the same way as Pub/Sub.
+
+## Cost optimization strategies <a id="optimization"/>
+
+The following strategies reduce Chat message costs:
+
+| Strategy | How it reduces costs |
+| --- | --- |
+| Increase `heartbeatThrottleMs` | Reduces typing indicator event frequency |
+| Disable typing indicators | Eliminates typing indicator messages in rooms where they are not needed |
+| [Server-side batching](/docs/guides/pub-sub/data-streaming#solution-server-side-batching) | Groups messages into single deliveries |
+| [Occupancy](/docs/presence-occupancy/occupancy) instead of presence | Avoids n-squared presence event fan-out when you only need member counts |
+
+<Aside data-type="further-reading">
+For the full list of message counting rules across all products, see [message billing](/docs/platform/pricing/message-billing).
+</Aside>
diff --git a/src/pages/docs/platform/pricing/message-billing.mdx b/src/pages/docs/platform/pricing/message-billing.mdx
@@ -1,45 +1,42 @@
 ---
 title: "Message billing"
-meta_description: "Understand how different Ably Pub/Sub operations contribute to your message count, including persistence, presence, and cost optimization strategies."
-meta_keywords: "message billing, message counting, pricing, persistence billing, presence billing, cost optimization"
+meta_description: "Understand how operations across all Ably products contribute to your message count, including Pub/Sub, Chat, LiveObjects, and Annotations."
+meta_keywords: "message billing, message counting, pricing, Pub/Sub billing, Chat billing, LiveObjects billing"
+intro: "How operations across all Ably products contribute to your message count."
 ---
 
-This page explains how different Ably operations contribute to your message count. Understanding message billing helps you optimize costs and choose the right features for your use case.
+All Ably products count messages for billing purposes. The following sections explain how operations across Pub/Sub, Chat, LiveObjects, and Annotations contribute to your message count.
 
 <Aside data-type="further-reading">
 For package comparison and volume discounts, see the [pricing](https://ably.com/pricing) page. For general billing information, see [billing](/docs/platform/pricing/billing).
 </Aside>
 
-## Basic message counting <a id="basic-counting"/>
+## How messages are counted <a id="basic-counting"/>
 
-Every message sent through Ably is counted for both publishing and delivery:
+Ably counts every message for both publishing and delivery:
 
 * 1 publish = 1 inbound message
 * Each subscriber delivery = 1 outbound message per subscriber
 * Each integration delivery = 1 outbound message per [integration](/docs/platform/integrations) target
 * Messages from metachannels (such as `[meta]log` and `[meta]stats`) follow the same counting rules
 
-For example, 1 publisher sends a message to a channel with 10 subscribers = **11 messages** (1 inbound + 10 outbound).
+For example, if 1 publisher sends a message to a channel with 10 subscribers, this counts as **11 messages** (1 inbound + 10 outbound).
 
 ## Message size <a id="message-size"/>
 
-Message size for Pub/Sub messages is calculated as the sum of the `name`, `clientId`, `data`, and `extras` [properties](/docs/api/realtime-sdk/messages#properties) before any compression or expansion occurs in the serialization process.
-
-<Aside data-type="note">
-LiveObjects and Annotations have different billing considerations. See [LiveObjects billing](/docs/liveobjects/concepts/billing) and [Annotations](/docs/messages/annotations) for details on their respective billing.
-</Aside>
+Ably calculates message size for Pub/Sub messages as the sum of the `name`, `clientId`, `data`, and `extras` [properties](/docs/api/realtime-sdk/messages#properties) before any compression or expansion occurs in the serialization process.
 
 * `name` and `clientId` are calculated as the size in bytes of their UTF-8 representation.
 * `data` is calculated as the size in bytes if it is binary, or its UTF-8 byte length if it is a string.
 * `extras` is calculated as the string length of its JSON representation.
 
-The [bandwidth](/docs/platform/pricing#bandwidth) allowance calculation uses an average message size of 5KiB. If your total bandwidth for the month exceeds this baseline, the overage is charged per GiB.
+The [bandwidth](/docs/platform/pricing#bandwidth) allowance calculation uses an average message size of 5KiB. If your total bandwidth for the month exceeds this baseline, Ably charges overage per GiB.
 
 See [maximum message size](/docs/platform/pricing/limits#message) for the size limits per package type.
 
-## Operations and their billing impact <a id="operations"/>
+## Pub/Sub operations <a id="pubsub-operations"/>
 
-The following table shows how different operations contribute to your message count:
+The following table shows how Pub/Sub operations contribute to your message count:
 
 | Operation | Messages counted | Notes |
 | --- | --- | --- |
@@ -51,21 +48,51 @@ The following table shows how different operations contribute to your message co
 | Rewind on attach | Rewound messages count as outbound | Up to 100 messages per [rewind](/docs/channels/options/rewind) |
 | Push notification | Counted separately per push platform | See [push notifications](/docs/push) |
 
+For Pub/Sub-specific cost optimization strategies, see [Pub/Sub pricing](/docs/pub-sub/pricing).
+
+## Chat operations <a id="chat-operations"/>
+
+The [Chat SDK](/docs/chat) is built on top of [Pub/Sub](/docs/pub-sub). All Chat operations generate Pub/Sub messages that follow the same counting rules.
+
+| Operation | Messages counted | Notes |
+| --- | --- | --- |
+| Chat message | 1 inbound + 1 per subscriber outbound | Same as a standard publish |
+| Typing indicator heartbeat | 1 inbound + 1 per subscriber outbound | Default interval is 10 seconds; approximately 6 events per minute per active typer |
+| Typing indicator stop | 1 inbound + 1 per subscriber outbound | Sent when a user stops typing |
+| Room reaction | 1 inbound + 1 per subscriber outbound | Same as a standard publish |
+| Presence enter/leave/update | 1 inbound + 1 per presence subscriber outbound | Same as Pub/Sub presence |
+| Occupancy | Uses metachannels | Follows standard metachannel counting rules |
+
+For Chat-specific cost optimization strategies, see [Chat pricing](/docs/chat/pricing).
+
+## LiveObjects operations <a id="liveobjects-operations"/>
+
+LiveObjects has a different billing scheme based on ObjectMessages. Each ObjectMessage counts as:
+
+* 1 outbound message per connected client (delivery)
+* 1 inbound message per connected client (acknowledgment)
+
+See the [LiveObjects billing](/docs/liveobjects/concepts/billing) page for details.
+
+## Annotations <a id="annotations"/>
+
+[Annotations](/docs/messages/annotations) have a different billing scheme from standard messages. See the [Annotations](/docs/messages/annotations) page for details on how annotation operations are counted.
+
 ## Persistence billing <a id="persistence"/>
 
-When persistence is enabled via [channel rules](/docs/storage-history/storage), each message stored to disk counts as an additional message.
+When persistence is enabled via [channel rules](/docs/storage-history/storage), Ably counts each message stored to disk as an additional message.
 
-If you persist all messages, a message published to 10 subscribers with persistence enabled = 1 (publish) + 10 (subscriber delivery) + 1 (persistence storage) = **12 messages**.
+If you persist all messages, a message published to 10 subscribers with persistence enabled counts as 1 (publish) + 10 (subscriber delivery) + 1 (persistence storage) = **12 messages**.
 
-If you persist last message only, the most recent message is stored. The storage cost is 1 additional message per new "last message" stored.
+If you persist the last message only, Ably stores the most recent message. The storage cost is 1 additional message per new "last message" stored.
 
 Retrieving persisted messages via the [history API](/docs/storage-history/history) also counts: each message returned in a history response = 1 additional message.
 
 To avoid additional costs for messages that do not need persistence, history, rewind, integrations, or resume, mark them as [ephemeral](/docs/pub-sub/advanced#ephemeral). Ephemeral messages are exempt from all of these features, reducing your billable message count.
 
 ## Presence event billing <a id="presence"/>
 
-Presence events (enter, leave, update) are billed as regular messages:
+Ably bills presence events (enter, leave, update) as regular messages:
 
 * 1 presence enter event with 100 presence subscribers = **101 messages** (1 enter + 100 deliveries)
 
@@ -79,19 +106,6 @@ To reduce presence costs:
 * Enable [server-side batching](/docs/presence-occupancy/presence#large-presence) to group presence events and support up to 20,000 members per channel.
 * Subscribe to presence updates only on channels where you need member-level detail.
 
-## Cost optimization strategies <a id="optimization"/>
-
-The following table summarizes strategies for reducing message costs:
-
-| Strategy | How it reduces costs | When to use |
-| --- | --- | --- |
-| [Ephemeral messages](/docs/pub-sub/advanced#ephemeral) | Exempt from persistence, rewind, resume, and integrations | Streaming data where history is not needed |
-| [echoMessages: false](/docs/pub-sub/advanced#echo) | Prevents self-delivery to the publisher | Optimistic UI patterns and server-side publishers |
-| [Conflation](/docs/guides/pub-sub/data-streaming#solution-message-conflation) | Delivers only the latest message per key in each time window | High-frequency updates where only the latest value matters |
-| [Server-side batching](/docs/guides/pub-sub/data-streaming#solution-server-side-batching) | Groups messages into single deliveries | High-throughput channels where slight delay is acceptable |
-| [Delta compression](/docs/channels/options/deltas) | Reduces payload size, lowering bandwidth costs | Large, structurally similar successive messages |
-| [Occupancy](/docs/presence-occupancy/occupancy) instead of presence | Avoids n-squared presence event fan-out | When you need member counts, not individual identities |
-
 <Aside data-type="further-reading">
 See the [pricing](https://ably.com/pricing) page for package comparison and volume discounts.
 </Aside>
diff --git a/src/pages/docs/pub-sub/pricing.mdx b/src/pages/docs/pub-sub/pricing.mdx
@@ -0,0 +1,41 @@
+---
+title: "Pricing"
+meta_description: "Understand how Pub/Sub operations contribute to your message count, including persistence, presence, and cost optimization strategies."
+meta_keywords: "message billing, message counting, pricing, persistence billing, presence billing, cost optimization"
+intro: "How Pub/Sub operations contribute to your message count and strategies to optimize costs."
+redirect_from:
+  - /docs/pub-sub/message-billing
+---
+
+Pub/Sub operations contribute to your message count based on publishing, delivery, and optional features like persistence and presence. The following sections explain how Ably counts these operations and how to optimize costs.
+
+<Aside data-type="further-reading">
+For the complete reference on how all Ably operations count as messages, see [message billing](/docs/platform/pricing/message-billing). For package comparison and volume discounts, see the [pricing](https://ably.com/pricing) page.
+</Aside>
+
+## What counts as a message <a id="messages"/>
+
+Every message published through Pub/Sub counts as 1 inbound message, with each subscriber delivery counting as 1 outbound message. Optional features like persistence, history retrieval, and integrations generate additional messages.
+
+For the complete breakdown of how each Pub/Sub operation counts as messages, see the [Pub/Sub operations](/docs/platform/pricing/message-billing#pubsub-operations) table in the central message billing reference.
+
+## Channels and connection minutes <a id="channels-connections"/>
+
+[Channels](/docs/channels) are the unit of message distribution. Each channel you use contributes to your [channel count](/docs/platform/pricing#channels). Ably bills [connection minutes](/docs/platform/pricing#connections) per minute of connection time for each connected client.
+
+## Cost optimization strategies <a id="optimization"/>
+
+The following table summarizes strategies for reducing message costs:
+
+| Strategy | How it reduces costs | When to use |
+| --- | --- | --- |
+| [Ephemeral messages](/docs/pub-sub/advanced#ephemeral) | Exempt from persistence, rewind, resume, and integrations | Streaming data where history is not needed |
+| [echoMessages: false](/docs/pub-sub/advanced#echo) | Prevents self-delivery to the publisher | Optimistic UI patterns and server-side publishers |
+| [Conflation](/docs/guides/pub-sub/data-streaming#solution-message-conflation) | Delivers only the latest message per key in each time window | High-frequency updates where only the latest value matters |
+| [Server-side batching](/docs/guides/pub-sub/data-streaming#solution-server-side-batching) | Groups messages into single deliveries | High-throughput channels where slight delay is acceptable |
+| [Delta compression](/docs/channels/options/deltas) | Reduces payload size, lowering bandwidth costs | Large, structurally similar successive messages |
+| [Occupancy](/docs/presence-occupancy/occupancy) instead of presence | Avoids n-squared presence event fan-out | When you need member counts, not individual identities |
+
+<Aside data-type="further-reading">
+For the full list of message counting rules across all products, see [message billing](/docs/platform/pricing/message-billing).
+</Aside>

Original file line number	Diff line number	Diff line change
`@@ -220,8 +220,8 @@ export default {`
`220`	`220`	`],`
`221`	`221`	`},`
`222`	`222`	`{`
`223`		`- name: 'Message billing',`
`224`		`- link: '/docs/chat/message-billing',`
	`223`	`+ name: 'Pricing',`
	`224`	`+ link: '/docs/chat/pricing',`
`225`	`225`	`},`
`226`	`226`	`{`
`227`	`227`	`name: 'Guides',`
Original file line number	Diff line number	Diff line change
`@@ -335,8 +335,8 @@ export default {`
`335`	`335`	`],`
`336`	`336`	`},`
`337`	`337`	`{`
`338`		`- name: 'Message billing',`
`339`		`- link: '/docs/pub-sub/message-billing',`
	`338`	`+ name: 'Pricing',`
	`339`	`+ link: '/docs/pub-sub/pricing',`
`340`	`340`	`},`
`341`	`341`	`{`
`342`	`342`	`name: 'Guides',`