Skip to content

Conversation

@JamieAbly
Copy link

Description

Adds four worked pricing examples to help customers estimate costs for common use cases:

  • Livestream chat – high-concurrency event chat with batching (Chat)
  • Support chat – 1:1 customer support with consumption vs MAU comparison (Chat)
  • Data broadcast – one-to-many updates with conflation (Pub/Sub)
  • Realtime dashboard – many-to-few device monitoring (Pub/Sub)

Each example includes assumptions, cost summary, message breakdown, and relevant optimisation notes (batching, conflation, etc).

Checklist

Adds four worked pricing examples to help customers estimate costs for common use cases:

- Livestream chat – high-concurrency event chat with batching (Chat)
- Support chat – 1:1 customer support with consumption vs MAU comparison (Chat)
- Data broadcast – one-to-many updates with conflation (Pub/Sub)
- Realtime dashboard – many-to-few device monitoring (Pub/Sub)

Each example includes assumptions, cost summary, message breakdown, and relevant optimisation notes (batching, conflation, etc).
@JamieAbly JamieAbly requested a review from a team January 9, 2026 09:39
@JamieAbly JamieAbly self-assigned this Jan 9, 2026
@JamieAbly JamieAbly added the review-app Create a Heroku review app label Jan 9, 2026
@coderabbitai
Copy link

coderabbitai bot commented Jan 9, 2026

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ably-ci ably-ci temporarily deployed to ably-docs-ftf-304-addin-rb6eth January 9, 2026 09:39 Inactive
Copy link
Contributor

@m-hulbert m-hulbert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really great thanks, Jamie. I've dropped a few comments and suggestions throughout and they are mostly all relevant to all 4 examples rather than me repeating myself 4 times 🙂

Copy link
Member

@paddybyers paddybyers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really found these pages confusing when I first read them. The summary costs table at the top has numbers and calculations that have no obvious relationship to the assumptions. Obviously when you scroll down it's clear where the numbers come from, but some hint upfront would help.

### Cost summary
The high-level cost breakdown for this scenario. Messages are billed for both inbound (published to Ably) and outbound (delivered to subscribers) – a single message to 100 subscribers generates 101 billable messages.

| Item | Calculation | Cost |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dollar results in this table are rounded to integer dollars so they look wrong. Eg 1.5 x $1 = $2. They shouldn't be rounded

JamieAbly and others added 7 commits January 14, 2026 14:20
Made several fixes to the pricing examples based on feedback.

- Updated the intro texts to be tied more closely to the technical use case (eg data broadcast) vs the specific use case (eg live sports betting)

- Added "pricing example" to all titles

- Updated titles to use ## instead of ###

- Ensured all messaging is in the second person perspective.

- Added a message breakdown to the data broadcast example

- Added some additional text to the "further reading section" to ensure bullets load correctly.

- Added some bridge text between Assumption & the Cost Summary to make the Cost Summary more clear on where the figures come from.

- Other minor amendments such as correcting rounding.
Updated the formatting in the docs for the pricing examples:
- Now use full numbers (e.g. 2,000,00 instead of 2M)
- Added links to the numbers in the connecting block of text between "Assumptions" and "Cost summary"
- Improved markdown formatting for readability
- Updated "See plans" links to /docs/platform/pricing
@JamieAbly JamieAbly requested a review from m-hulbert January 21, 2026 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-app Create a Heroku review app

Development

Successfully merging this pull request may close these issues.

5 participants