starter.wiki

Messaging

Embedded Product Chat

Choose conversation infrastructure for chat embedded in a product without confusing it with help-desk cases or realtime media.

Recommendation

Choose how much of the chat product to own.

Stream fits a developer-led platform route, Sendbird a broader enterprise chat route, and TalkJS a prebuilt UI route.12

For: Product and engineering teams embedding participant-to-participant text conversation in an application

Main trade-off

Managed chat accelerates conversation features while coupling participant identity, messages, moderation, media, retention, regions, pricing, and migration to provider models.123

Three chat ownership routes

The routes trade product control against platform and UI ownership.

  1. Conversation model

    Define channels, participants, roles, membership, messages, threads, unread state, presence, and search.12

  2. Safety and data

    Confirm moderation, attachments, retention, export, deletion, encryption claims, regions, and prohibited use.12

  3. Scale and ownership

    Model MAU, concurrency, messages, SDK/UI control, support, migration, and build-versus-managed operations.12

Route by product ownership

Select the smallest platform whose conversation and operating model fits.

Developer-led configurable chat

Choose Stream Chat

Configurable channel, message, moderation, and SDK primitives fit a team owning the product experience.

Verify: Confirm MAU/concurrency, messages, retention, moderation, regions, export, and plan boundaries.1

Enterprise chat platform

Choose Sendbird Chat

A broader enterprise chat and operations surface fits scale, moderation, and commercial requirements.

Verify: Confirm product scope, users, concurrency, retention, add-ons, regions, support, and exit.2

Prebuilt chat UI

Choose TalkJS

Ready UI and a more opinionated product reduce implementation surface for a bounded chat experience.

Verify: Confirm active users, customization, retention, moderation, attachments, data, and migration.3

Boundary: This page excludes AI chatbot logic, team messaging apps, help-desk selection, and WebSocket tutorials.

Conversation is not a support case

Product chat, customer support, and realtime media use different records and operating teams.

Chat versus support
Chat owns product conversations; support owns agent-managed cases and service workflows.12
Text versus media
Realtime audio/video requires a media plane, quality controls, recording, and participant-minute economics.12
UI versus primitives
Prebuilt UI shortens implementation while constraining interaction and migration control.3

Official resources

Verify current product scope, policy, data, retention, delivery, regional, pricing, and account boundaries in first-party material before implementation.

Sources

Official product, standard, and policy sources supporting the bounded routes on this page.

  1. 1
    Stream Chat documentation

    Stream · Accessed Official

  2. 2
    Sendbird Chat documentation

    Sendbird · Accessed Official

  3. 3
    TalkJS documentation

    TalkJS · Accessed Official