Short answer: Sendbird has moved three things buyers shortlist on the same weekly refresh: the free-trial lane is closing (the Embed free tier is being sunset in favour of paid developer tiers), the MAU-based SDK pricing tiers have been rebalanced on the published rate card, and a new social-channel bridge — third-party SMS, WhatsApp, and email routed through Sendbird's in-app layer — has shipped as GA. None of those change Sendbird's classification: it remains the in-app-chat-SDK vendor the /compare/sendbird head-to-head frames symmetric with Devotel Orbit. This post records the moves a buyer should re-check first, then runs the usual channel-gap table the same head-to-head uses so the reassessment is grounded on cells, not on the vendor's own price-change narrative.
1. What changed on Sendbird's public surface
Three updates hit Sendbird's pricing and product announcements in sequence, and each one re-frames the evaluation the usual head-to-head runs:
The free-trial sunset. Sendbird's developer free tier — the no-cost "get the SDK running" lane many teams used to prototype — is being deprecated in favour of paid entry tiers. For buyers whose proof-of-concept depends on a free lane, the trial journal closes; production-shortlisting moves to the paid tier from the first message. The lane that remains is the published MAU-based pricing tiers the SDK bills on monthly-active-user counts, which is the model the head-to-head records as the commercial row.
The SDK pricing rebalance. Sendbird's published rate card has shifted tiers: per-MAU allotments, included message volumes, and the overage posture moved on the public pricing page. A buyer should not lift numbers from a year-old bookmark; the rate card is the source of truth, and the head-to-head deliberately does not quote a specific price because the published page is authoritative. What changed is the tier shape — the numbers you plan against are not the numbers from the previous quarter.
The social-channel GA. Sendbird shipped a third-party SMS/WhatsApp/email bridge to general availability — meaning the in-app chat surface can route a conversation out to carrier channels through Sendbird's own bridge rather than a separate-vendor integration. That is a narrower claim than it first sounds: the channels are still the third-party providers' pipes Sendbird brokers, not Sendbird's own carrier-grade network, and the bridge lives on the in-app layer, so the omnichannel reach follows the same boundaries Sendbird always held.
The three moves together hit two evaluation axes at once: the commercial model (MAU tiers with a rebalanced rate card) and the channel surface (a brokered third-party bridge, not a native-channel stack).
2. The channel-gap table the reassessment should use
The cells below mirror the public /compare/sendbird comparison table (retrieved September 2026), which asserts only what Sendbird's public website documents:
| Criterion | Devotel Orbit | Sendbird |
|---|---|---|
| Website-chat widget | Yes | Yes |
| Shared inbox across WhatsApp, email, Facebook Messenger, Instagram & SMS | Yes | Partial, in-app chat only plus the new third-party bridge; the bridge rides separate vendors' pipes |
| AI chatbot (resolves common inquiries) | Yes | Yes |
| GDPR-first EU data hosting | Yes | Yes |
| Native customer data platform (identity resolution, golden records, audiences) | Yes | No |
| Human + AI contact center (ACD) | Yes | Partial, an agent workspace on SDK-scoped chats, not a voice ACD |
| Programmable SMS & MMS API | Yes | No |
| RCS Business Messaging | Yes | No |
| Programmable voice with SIP trunking & IVR | Yes | No, in-app voice/video calls, no PSTN |
| Pay-as-you-go usage billing (no per-MAU licence) | Yes | No, MAU tiers (rate card rebalanced) |
| One unified wallet across every channel | Yes | No, external channels bill to their own vendors |
Read by shape, the new bridge changes the Partial label on one row, not the orientation of the whole table: the brokered third-party connectors mean the "shared inbox" row shifts from "no" to "partial," but the native-channel set — SMS/MMS APIs, RCS, SIP voice, unified CDP, one wallet — still resolves against Orbit's native stack. The reassessment gains honesty from the updated cell; it does not gain a change in verdict.
3. Vendor-vs-vendor framing modeled on the framework post
The reassessment is the same short-answer symmetric frame the Vapi vs ElevenLabs framework post uses, applied to the chat lane:
Short answer: Sendbird remains the in-app-chat-SDK vendor — the SDK, the UI kit, the moderation layer, billed on MAU tiers — and those are parity cells the evaluation credits, not concessions. Devotel Orbit remains the omnichannel platform — the native CDP, the contact-center ACD, and the carrier-grade channels (SMS/MMS, RCS, WhatsApp, email, programmable voice) on one pay-as-you-go wallet. The 2026 price and deprecation moves do not move the archetype; they adjust which details of the archetype matter at this week's renewal.
That is the whole vendor-vs-vendor framing: both vendors get their honest lane, neither gets a hollow superlative, and the frame closes with "compare on cells, not on narrative."
4. Tenant-owned controls before the reassessment closes
Two controls matter at go-live regardless of which vendor the reassessment settles on:
- Consent capture and quiet hours are tenant-managed. On Orbit, the consent policy you enforce per channel is your organization's setting, not an SDK-vendor default, and that stays true whether the brokered-bridge row resolves "partial" or "no" on the comparison.
- Retention policy is tenant-configurable. Your retention windows apply to the profile and the conversation store on one account, so the reassessment should name the policy it intends to enforce, not inherit a per-channel history default from the incumbent.
5. Rooter-out and hop-out
The full head-to-head lives on the /compare/sendbird registry page — cells above, plus the per-row footnotes and structured-data pairings. For a broader buyer round, the ticketing and helpdesk platform round-up weighs the adjacent category (Intercom, Zendesk, Front, Help Scout, and their kin) on the same evaluation genre, which is where most in-app-chat reassessments actually widen.
Frequently asked questions
Do Sendbird's price changes make Orbit a different choice?
No. The reassessment re-checks tier shape and the updated channel-bridge cell; the archetype answer (in-app SDK versus omnichannel platform) is unchanged. The price moves adjust numbers you plan against, not the classification frame.
Does Sendbird's new social-channel bridge close the channel gap?
Partially. The bridge routes third-party SMS/WhatsApp/email through Sendbird's in-app layer, so the "shared inbox" row moves to Partial on the table. The brokered third-party pipes remain separate vendors' reach — the native-channel set (SMS/MMS APIs, RCS, SIP voice, one wallet) still resolves against Orbit's native stack.
Where does this post differ from the head-to-head?
The head-to-head is the registry cell record; this post is the news-thesis companion that records what changed on the vendor's public surface (free-trial sunset, pricing rebalance, bridge GA) and why the reassessment should re-check those cells first. Read the head-to-head for the matrix; read this post to know which moves reframe the matrix.
How should a buyer whose plan numbers came from Sendbird's old tier structure respond?
Pull the current published rate card from Sendbird's pricing page — do not reuse a bookmark from before the rebalance — and re-table the commercial row against Orbit's pay-as-you-go usage billing. The rate card is the source of truth.
Hop to the sibling comparisons
The cell-level matrix lives on the /compare/sendbird head-to-head; the ticketing and helpdesk round-up frames the adjacent category, and the Orbit vs Sendbird long-form post reads the same registry cells in full narrative form. The pricing page on each vendor's site is the source of truth and supersedes every figure cited here.
Published 30 September 2026.