Chat Pricing

We gracefully handle connection failures and recover as soon as the internet connection is back. The tech is based on Go, RocksDB, Raft and WebSockets.

We reuse a lot of the tech and best practices from activity feeds. For chat we currently have extensive QA and monitoring in place.

iOS and Android push notifications are supported out of the box. In case you need more flexibility webhooks are also available.

Stream allows you to build your own chat bots. You can use webhooks to parse messages and reply to them. You can also add custom attachments to messages to enable rich interactions such as picking a location or selecting a date.

Search is supported by the API and is included in the pricing.

MAUs are defined as any user that connected to chat in the last calendar month. If you show chat to all users of your app, your Stream Chat MAU will equal your total user base. If Chat is more hidden as a feature, your Stream Chat MAU will likely be a subset of your total user base.

You can add custom fields to messages and you can also attach different types of attachments. Common examples include sharing a product, a live score of a match, a date picker or any other type of interactive/rich interface.

Peak Concurrent Connections is measured as the point in the monthly billing cycle at which the most open WebSocket connections are established between devices and Stream for the organization.

The most common method of opening a WebSocket connection is using the connectUser() (or SDK equivalent) method described here.

A single user, or user_id, can have multiple open WebSocket connections. For example, if they are logged in on multiple devices or an integration error has occurred.