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 🙂

Conflation intervals are configurable from 100ms to 500ms – lower intervals reduce latency; higher intervals reduce message volume and costs.
</Aside>

### Cost summary
Copy link
Contributor

Choose a reason for hiding this comment

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

It doesn't effect the output, but if could leave an empty line between headings, paragraphs and tables etc. it makes it a bit more readable for other editors.

| Full market (10+ selections) | 8 KiB | ~2 KiB | 75% |
| Live stats + odds bundle | 15 KiB | ~4 KiB | 73% |

<Aside data-type='further-reading'>
Copy link
Contributor

Choose a reason for hiding this comment

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

Unforunately these don't format well on their own. If you add a short intro line before the bullet list then they do.

Copy link
Author

Choose a reason for hiding this comment

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

I've implemented a fix for this, but I've sent you a DM to confirm if I've understood this ask correctly.

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

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