Sendbird review

Sendbird is a communications API platform: a vendor-managed service for adding conversation infrastructure to an application, rather than a standalone chat app, CLI or self-hosted server. The vendor says its infrastructure powers billions of conversations every month. In a product stack, Sendbird sits behind the application experience as the communications layer; your product still needs its own UI and application logic.

The homepage presents two products. Sendbird communications API is for conversations, while delight.ai is described as an AI concierge providing personalized customer experiences across the customer journey. The homepage also includes a SendBirdCall example that places a call using a DialParams object and SendBirdCall.dial.

That is enough to identify the broad role, but not enough to plan a detailed integration. Teams should confirm the supported client platforms, API behavior and deployment model against Sendbird's docs before selecting it. The practical architectural tradeoff is clear: use a communications service rather than building the conversation infrastructure yourself, while accepting a dependency on the vendor's service and plan limits.

The homepage names a communications API and shows a voice-call example using DialParams and SendBirdCall.dial. That snippet is Swift-style syntax, but one example is not a complete SDK support matrix. Sendbird's homepage does not name API protocols, SDK packages, supported languages, a CLI, webhooks or integrations. Confirm SDK availability and documentation for each client and server language in Sendbird's developer docs before committing to an implementation.

The architecture decision is whether to build your own interface on top of Sendbird's communications infrastructure or use any client libraries and product components supported by the vendor. The vendor's homepage establishes the API and calling example, but does not provide enough detail to assess setup steps, authentication, event delivery, testing tools or versioning. Ask how clients connect, how server-side operations are authenticated, and what migration paths exist for messages and user data.

Sendbird also presents delight.ai as an AI concierge for customer experiences. Treat that as a separate product decision: verify its integration surface, data flows and pricing rather than assuming it comes with the communications API.

The Free trial plan costs $0 and allows up to 1,000 MAUs, up to 20 peak connections and unlimited messages per month. It does not allow overages, so it is a test tier with a hard usage boundary rather than a production buffer.

Starter is $399 per month with monthly billing or $349 per month with annual billing. It includes 5K MAUs, messaging essentials, basic moderation, ticketed support and 30K free in-app business messages. Pro is $599 monthly or $499 with annual billing, also at 5K MAUs; it adds Starter features, translation and data export, with the same 30K free in-app business messages. Enterprise pricing is custom for millions of MAUs.

The bill can grow when MAUs exceed plan allowances. The pricing information says MAU overage fees may apply, but does not publish the amount. Enterprise add-ons include Advanced Moderation and Data Export, and higher support levels can be purchased; their prices are also unpublished. Confirm overage calculations and any message charges before forecasting production spend.

Sendbird's homepage describes a communications API service but does not publish a source licence or a self-hosting option. We would not treat it as an open-source or self-hostable alternative without written confirmation from the vendor. A Reddit discussion about chat APIs includes a commenter saying most providers do not support self-hosting, but that is a general observation, not confirmation of Sendbird's deployment terms.

Data export is plan-dependent in the published pricing: Pro includes it, while Enterprise lists Data Export as an add-on. Starter does not list export. Ask what data can be exported, in what format, and whether export includes messages, attachments, user records and metadata. Those details affect the cost of leaving.

Using a vendor communications API also creates implementation work to migrate clients, data and application behavior if you switch providers. The effort depends on your integration and data model; Sendbird's published material here does not define a migration path or export format.

The main published capacity limits to model are MAUs and peak connections. The Free trial plan allows up to 1,000 MAUs and 20 peak connections, with no overages. Starter and Pro list 5K MAUs, and Enterprise is priced for millions of MAUs. The published pricing information does not publish peak-connection limits for paid plans, MAU overage rates, API rate limits or service-level commitments. Ask Sendbird for those numbers, plus incident response and availability terms, before launch.

The vendor says its infrastructure powers billions of conversations every month, but that scale claim does not replace plan-specific limits or an SLA. Security and compliance details also need review: confirm encryption, retention, access controls, data residency and deletion behavior for your use case.

Reddit discussions show both interest in outsourcing chat infrastructure and concerns about provider access to private messages. They do not establish Sendbird's data handling practices. One thread asks whether a provider can access private chat data; treat that as a reason to review Sendbird's privacy and security documentation, not as evidence of a specific exposure.