Element
Element 1.12.33 ships: simpler recovery keys, mandatory verification, no libolm migration.
Comparison · Comms
Chatwoot vs Dendrite
A side-by-side editorial comparison of Chatwoot and Dendrite — release velocity, themes, recent moves, and the top alternatives to consider.
Chatwoot vs Dendrite: at a glance
| Feature | Chatwoot | Dendrite |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | ai-assistant, customer-support, whatsapp, voice-calling | matrix, homeserver, fork, federation |
| Last editorial update | 29d ago | 3mo ago |
| Website | — | Visit → |
What is Chatwoot?
Chatwoot retires Captain V1 and rebuilds its AI assistant as a structured, per-assistant behavior system.
Chatwoot is in the middle of a significant architectural transition for its AI assistant layer. The original Captain V1 (free-form instructions) is being retired in the next self-hosted release in favor of a structured model with scenarios, response guidelines, guardrails, and a testing playground. Cloud users are already on the new system. Alongside this, two substantial releases expanded Captain's control surface: per-assistant custom tools, inactivity handling, and audience/schedule targeting. WhatsApp BSUID support and improved call recording controls round out a busy month in the communications layer.
What is Dendrite?
A forked, relicensed Dendrite spent its first year catching up on Matrix protocol and security debt
The window opens with the first release after forking from matrix-org/dendrite under AGPLv3, which fixed long-standing state-reset bugs and added I2P and Onion listening. What follows is a security release closing a server-side request forgery vulnerability, then a release adding room version 12 support and two MSC implementations, and finally two quick patches for unresponsiveness, v12 room joins and malformed PDUs blocking whole transactions.
Chatwoot vs Dendrite: editorial side-by-side
Chatwoot
7.5COMMS
Chatwoot retires Captain V1 and rebuilds its AI assistant as a structured, per-assistant behavior system.
◆ Current state
Chatwoot is in the middle of a significant architectural transition for its AI assistant layer. The original Captain V1 (free-form instructions) is being retired in the next self-hosted release in favor of a structured model with scenarios, response guidelines, guardrails, and a testing playground. Cloud users are already on the new system. Alongside this, two substantial releases expanded Captain's control surface: per-assistant custom tools, inactivity handling, and audience/schedule targeting. WhatsApp BSUID support and improved call recording controls round out a busy month in the communications layer.
◆ Where it's heading
Chatwoot is shifting Captain from a chatbot add-on into a proper automation layer with auditable, testable behavior. Per-assistant tool isolation, audience segmentation, and schedule-based availability bring it closer to the model used by Intercom Fin and Zendesk AI. The V1 retirement removes a backward-compatibility constraint that was slowing this transition. The playground — which lets admins test assistant configurations before saving — removes the need to test in production, which was the practical barrier to iterating on Captain.
◆ Prediction
The next likely move is a reporting layer for Captain — tracking resolution rates, handoff rates, and scenario effectiveness per assistant. The playground's 'Run details' view (showing which scenario handled a message and which tools ran) is the building block for that kind of analytics.
Dendrite
0.0COMMS
A forked, relicensed Dendrite spent its first year catching up on Matrix protocol and security debt
◆ Current state
The window opens with the first release after forking from matrix-org/dendrite under AGPLv3, which fixed long-standing state-reset bugs and added I2P and Onion listening. What follows is a security release closing a server-side request forgery vulnerability, then a release adding room version 12 support and two MSC implementations, and finally two quick patches for unresponsiveness, v12 room joins and malformed PDUs blocking whole transactions.
◆ Where it's heading
This is a fork proving it can carry a homeserver. The order is telling: license and state correctness first, then a CVE, then protocol currency with room version 12, then the operational bugs that surface once people actually run it. Several fixes carry outside contributor credits, which is the fork's clearest sign of life.
◆ Prediction
Expect continued protocol catch-up on newer MSCs and room versions plus operational fixes, since federation compatibility is the constraint that sets this project's agenda.
Alternatives to Chatwoot and Dendrite
Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Chatwoot or Dendrite.
Tawk.to
tawk.to's widget 4.4.0 turns to keyboard and screen-reader fixes after a run of form work.
Krisp
Krisp 2.83.4 brings Voice Translation into conference calls and lightens Accent Conversion.
Fonoster
Fonoster jumps to v0.33 in a week, rebuilding its SIP and media edge and defaulting to HTTPS.
Pixelfed
Pixelfed 0.15.2 ships the PHP RCE patches and turns cached timelines on for everyone.
Salesmsg
Salesmsg Reviews can now trigger follow-ups automatically based on a customer's latest rating.
See all Chatwoot alternatives → · See all Dendrite alternatives →
Recent activity from Chatwoot and Dendrite
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoChatwootCaptain V1 is retiring: every account moves to the new Captain ⚡
- 1mo agoChatwootMore control over Captain Assistant behaviour ⚡
- 1mo agoChatwootImproved Help Center media uploads
- 1mo agoChatwootSupport for WhatsApp usernames and BSUIDs
- 1mo agoChatwootDecide when calls are recorded and transcribed
- 1mo agoChatwootGuided manual setup for WhatsApp inboxes
- 1y agoDendriteFixes startup crash on rooms lacking a create event
- 1y agoDendriteFixes v12 room joins, invites and stalled transactions
- 1y agoDendriteRoom version 12 support and NATS refactoring
- 1y agoDendriteFixes SSRF in gomatrixserverlib and speeds ACL loading
- 1y agoDendriteFirst release after the fork, relicensed under AGPLv3 ⚡
Frequently asked questions
What is the difference between Chatwoot and Dendrite?
They serve adjacent needs but don't currently overlap on shipped themes. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Chatwoot better than Dendrite?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
What are the best alternatives to Chatwoot?
Top Chatwoot alternatives in Comms are ranked by recent ship velocity. Browse the "Chatwoot alternatives" section above for the current picks, or visit /alternatives/chatwoot for the full list with editorial commentary on each.
What are the best alternatives to Dendrite?
Top Dendrite alternatives in Comms are ranked by recent ship velocity. Browse the "Dendrite alternatives" section above for the current picks, or visit /alternatives/dendrite for the full list with editorial commentary on each.