Zoho Cliq
Cliq 7.0 stops being a destination app and becomes a layer across Zoho
A side-by-side editorial comparison of Chatwoot and Dendrite — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Chatwoot | Dendrite |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | customer-support, ai-agents, voice, routing | matrix, homeserver, fork, federation |
| Last editorial update | 5h ago | 20d ago |
| Website | — | Visit → |
Chatwoot is making Captain something a support team can scope, schedule and hand back.
Captain, the AI agent, now has per-assistant Audience and Schedule settings: teams choose which customers it answers using contact and conversation attributes, and when it is available - anytime, during business hours, or outside them. Non-matching conversations route to the human Open queue instead. Voice, introduced in June, has its own Calls dashboard with filtering, per-call status and in-place recordings, and reporting charts lead from a metric to the conversations behind it.
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.
Captain, the AI agent, now has per-assistant Audience and Schedule settings: teams choose which customers it answers using contact and conversation attributes, and when it is available - anytime, during business hours, or outside them. Non-matching conversations route to the human Open queue instead. Voice, introduced in June, has its own Calls dashboard with filtering, per-call status and in-place recordings, and reporting charts lead from a metric to the conversations behind it.
The pattern is consolidation: each release takes something already shipped and adds the surface a daily operator needs. With Captain that has meant answer quality first, then self-maintaining documents, and now deployment controls - the settings that decide whether an AI agent can be switched on in production at all. The after-hours configuration is the telling one, positioning Captain as coverage for the hours a team is not staffed rather than as a replacement for it.
Voice remains the thread with a dashboard but no automation - neither workflow triggers nor Captain participation - and the Audience and Schedule model is the obvious shape to extend there next.
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.
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.
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.
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.
Cliq 7.0 stops being a destination app and becomes a layer across Zoho
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
Element Web is opening an extension surface while rebuilding its timeline underneath.
Signal's beta train keeps trickling small comfort settings between maintenance drops
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
Krisp is selling real-time voice manipulation to contact centers, and the defense against it too.
See all Chatwoot alternatives → · See all Dendrite alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Chatwoot is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Chatwoot is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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.
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.
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.