Rspamd
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
A side-by-side editorial comparison of Chatwoot and Rocket.Chat — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Chatwoot | Rocket.Chat |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 7.5 | 6.3 |
| Sparks · 30d | 0 | 0 |
| Top themes | ai-assistant, customer-support, whatsapp, voice-calling | team-chat, licensing, self-hosted, performance |
| Last editorial update | 1mo ago | 4d ago |
| Website | — | Visit → |
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.
Rocket.Chat 9.0 reaches rc.8 with a migration fix as candidates shrink to single patches.
The 9.0 candidate line opened on 27 October with a licensing change: LDAP, SAML and Custom OAuth now require a premium plan. Since rc.4 the candidates have been fixes, and rc.8 on 7 November carries a single one: servers that started during another server's database migration no longer keep stale settings until restart. On 6 November 8.9.1 LTS backported the 9.0 load fixes plus a security hotfix.
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.
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.
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.
The 9.0 candidate line opened on 27 October with a licensing change: LDAP, SAML and Custom OAuth now require a premium plan. Since rc.4 the candidates have been fixes, and rc.8 on 7 November carries a single one: servers that started during another server's database migration no longer keep stale settings until restart. On 6 November 8.9.1 LTS backported the 9.0 load fixes plus a security hotfix.
9.0 is in stabilization: each candidate is smaller than the last, and the load fixes are being carried to the LTS line rather than held for the major. Native LiveKit video is being promoted step by step, from alpha to beta and now as the named default provider option.
With rc.7 down to a handful of fixes, 9.0.0 GA is the next likely release, followed by further 8.9.x LTS patches carrying the same fixes.
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 Rocket.Chat.
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
Twilio's voice AI stops cutting callers off mid-sentence, using its own turn-taking model.
Salesmsg adds call-back requests and a one-click Emergency Stop for all outbound texts.
Element 1.12.35 follows the call picture-in-picture release with one desktop storage fix.
Krisp moves call transcripts and live captions to cloud transcription in KrispCX 2.84.4.
Misskey 2026.11 ships: a leaner start script, and Node.js 22 no longer boots.
See all Chatwoot alternatives → · See all Rocket.Chat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Comms. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 6.3), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 6.3), 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.
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 Rocket.Chat alternatives in Comms are ranked by recent ship velocity. Browse the "Rocket.Chat alternatives" section above for the current picks, or visit /alternatives/rocketchat for the full list with editorial commentary on each.