You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/pages/docs/ai-transport/pricing.mdx
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,9 +24,13 @@ The total cost depends on the [token streaming pattern](/docs/ai-transport/token
24
24
For how all Ably products count messages, see [message counting](/docs/platform/pricing/message-counting).
25
25
</Aside>
26
26
27
-
## Channels and connections <aid="channels-connections"/>
27
+
## Channels <aid="channels"/>
28
28
29
-
Each channel used for token streaming contributes to your [channel count](/docs/platform/pricing#channels). Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections) per minute of connection time.
29
+
Each channel used for token streaming contributes to your [channel count](/docs/platform/pricing#channels).
30
+
31
+
## Connections <aid="connections"/>
32
+
33
+
Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections). A connection-minute is counted for every minute a client maintains an open connection, regardless of activity. Clients that remain connected but idle still accrue connection minutes.
| Occupancy event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
41
-
|[Moderation](/docs/chat/moderation)||
42
-
| Moderation action | 1 inbound message; triggers a message update or delete which follows standard delivery |
36
+
|[Occupancy](/docs/chat/rooms/occupancy) event | 1 outbound message per subscriber (generated on membership changes, debounced up to 15s) |
37
+
|[Moderation](/docs/chat/moderation) action | 1 inbound message; triggers a message update or delete which follows standard delivery |
43
38
44
39
<Asidedata-type="further-reading">
45
40
For how all Ably products count messages, see [message counting](/docs/platform/pricing/message-counting).
46
41
</Aside>
47
42
48
-
## Rooms, channels, and connections <aid="rooms-connections"/>
43
+
## Roomsand channels <aid="channels"/>
49
44
50
-
Each Chat room maps to a set of underlying Pub/Sub channels. Each room feature (messages, typing, reactions, presence, occupancy) uses its own dedicated channel. The total number of channels used by a room depends on which features are active.
45
+
Each Chat [room](/docs/chat/rooms) maps to a set of underlying Pub/Sub channels. Each room feature (messages, typing, reactions, presence, occupancy) uses its own dedicated channel. The total number of channels used by a room depends on which features are active.
51
46
52
-
Channels contribute to your [channel count](/docs/platform/pricing#channels). The more rooms a client is attached to, and the more features enabled per room, the more channels are consumed.
47
+
Channels contribute to your [channel count](/docs/platform/pricing#channels). The more rooms a client is attached to, and the more features enabled per room, the more channels are consumed.[Detach](/docs/chat/rooms#detach) from rooms when they are no longer needed, and [release](/docs/chat/rooms#release) rooms that are no longer in use to reduce your channel count.
53
48
54
-
Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections). Ably counts a connection-minute for every minute a client maintains an open connection, regardless of activity. Clients that remain connected but idle still accrue connection minutes.
49
+
## Connections <aid="connections"/>
50
+
51
+
Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections). A connection-minute is counted for every minute a client maintains an open connection, regardless of activity. Clients that remain connected but idle still accrue connection minutes. Close connections when the client is done to stop accruing connection minutes.
55
52
56
53
## Cost optimization <aid="optimization"/>
57
54
@@ -63,10 +60,6 @@ Increase the `heartbeatThrottleMs` [room option](/docs/chat/rooms#typing) to red
63
60
64
61
[Server-side batching](/docs/messages/batch#server-side) groups messages into single deliveries. Use this for high-throughput rooms where slight delay is acceptable.
65
62
66
-
### Detach from unused rooms
67
-
68
-
[Detach](/docs/chat/rooms#detach) from rooms when they are no longer needed, and [release](/docs/chat/rooms#release) rooms that are no longer in use. This reduces your channel count and connection usage. Close connections when the client is done to stop accruing connection minutes.
69
-
70
63
### Use occupancy instead of presence
71
64
72
65
Use [occupancy](/docs/chat/rooms/occupancy) instead of [presence](/docs/chat/rooms/presence) when you only need member counts, not individual identities. This avoids the n-squared presence event fan-out. For example, 200 members joining and leaving generates approximately **80,400 messages**. See [large-scale presence sets](/docs/presence-occupancy/presence#large-presence) for details.
|[Synchronization](#synchronization)| 1 message per object synchronized |
24
24
|[REST API](#rest-api) fetch | 1 message per object in response |
@@ -30,11 +30,13 @@ Nested object creation generates additional messages for each nested object.
30
30
For how all Ably products count messages, see [message counting](/docs/platform/pricing/message-counting).
31
31
</Aside>
32
32
33
-
## Channels and connections <aid="channels-connections"/>
33
+
## Channels <aid="channels"/>
34
34
35
-
Each LiveObjects channel 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.
35
+
Each LiveObjects channel contributes to your [channel count](/docs/platform/pricing#channels). Subscribing to updates does not affect the number of messages received by a client. Any client attached to a channel with the `object-subscribe` capability automatically receives all object messages for that channel. Subscribing to updates on an object adds a listener that is called whenever the client receives updates for that object.
36
36
37
-
Subscribing to updates does not affect the number of messages received by a client. Any client attached to a channel with the `object-subscribe` capability automatically receives all object messages for that channel. Subscribing to updates on an object adds a listener that is called whenever the client receives updates for that object.
37
+
## Connections <aid="connections"/>
38
+
39
+
Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections). A connection-minute is counted for every minute a client maintains an open connection, regardless of activity. Clients that remain connected but idle still accrue connection minutes.
Copy file name to clipboardExpand all lines: src/pages/docs/livesync/pricing.mdx
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,13 @@ For example, if the database connector publishes 1 update and 3 clients are subs
22
22
For how all Ably products count messages, see [message counting](/docs/platform/pricing/message-counting).
23
23
</Aside>
24
24
25
-
## Channels and connections <aid="channels-connections"/>
25
+
## Channels <aid="channels"/>
26
26
27
-
Each channel that the database connector publishes to contributes to your [channel count](/docs/platform/pricing#channels). Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections) per minute of connection time.
27
+
Each channel that the database connector publishes to contributes to your [channel count](/docs/platform/pricing#channels).
28
+
29
+
## Connections <aid="connections"/>
30
+
31
+
Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections). A connection-minute is counted for every minute a client maintains an open connection, regardless of activity. Clients that remain connected but idle still accrue connection minutes.
|[Annotation summary](/docs/messages/annotations#annotation-summaries) delivery | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
58
58
|[Lifecycle event](/docs/metadata-stats/metadata) (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
59
59
|[`[meta]stats:minute`](/docs/metadata-stats/metadata) event | 1 message per event |
60
-
|[`[meta]log`](/docs/metadata-stats/metadata) subscription | Not counted |
60
+
|`[meta]log` subscription | Not counted |
61
61
62
62
For Pub/Sub-specific cost optimization strategies, see [Pub/Sub pricing](/docs/pub-sub/pricing).
63
63
@@ -76,16 +76,16 @@ The [Chat SDK](/docs/chat) is built on top of [Pub/Sub](/docs/pub-sub). All Chat
76
76
|[History](/docs/chat/rooms/history) retrieval | 1 message per retrieved message |
Live cursors use a [separate channel](/docs/spaces/cursors#foundations) from other space features due to their high update frequency. Registering multiple subscription listeners for the same event does not increase your message count, as these are [client-side filtered events](/docs/spaces/space#subscribe).
|[Annotation summary](/docs/messages/annotations#annotation-summaries) delivery | 1 outbound message per subscriber; multiple annotations may be rolled up into a single summary |
33
33
|[Lifecycle event](/docs/metadata-stats/metadata) (`[meta]connection.lifecycle`, `[meta]channel.lifecycle`) | 1 message per event |
34
34
|[`[meta]stats:minute`](/docs/metadata-stats/metadata) event | 1 message per event |
35
-
|[`[meta]log`](/docs/metadata-stats/metadata) subscription | Not counted |
35
+
|`[meta]log` subscription | Not counted |
36
36
37
37
<Asidedata-type="further-reading">
38
38
For how all Ably products count messages, see [message counting](/docs/platform/pricing/message-counting).
39
39
</Aside>
40
40
41
-
## Channels and connection minutes <aid="channels-connections"/>
41
+
## Channels <aid="channels"/>
42
42
43
-
[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.
43
+
[Channels](/docs/channels) are the unit of message distribution. Each channel you use contributes to your [channel count](/docs/platform/pricing#channels). Ably includes channels with each package and charges for additional channels beyond the included allowance.
44
+
45
+
## Connections <aid="connections"/>
46
+
47
+
Ably bills each connected client for [connection minutes](/docs/platform/pricing#connections). A connection-minute is counted for every minute a client maintains an open connection, regardless of activity. Clients that remain connected but idle still accrue connection minutes.
0 commit comments