Fonoster
Fonoster ships four releases in a day to make linking a Twilio number a single step.
Comparison · Comms
Chatwoot vs Ergo
A side-by-side editorial comparison of Chatwoot and Ergo — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:self-hosted
Chatwoot vs Ergo: at a glance
| Feature | Chatwoot | Ergo |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 7.5 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | ai-assistant, customer-support, whatsapp, voice-calling | irc, ircv3, self-hosted, release-candidates |
| Last editorial update | 1mo ago | 2mo 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 Ergo?
Ergo keeps tracking IRCv3 upstream while quietly opening its history layer to real databases.
Ergo ships roughly two releases a year, each announced as a release candidate about a week ahead of the final. The content is consistent: whatever IRCv3 specifications have firmed up since the last cycle, plus bug fixes and config-format adjustments. The one structural change in this window was pluggable history storage, which took Ergo off its embedded database as the only option.
Chatwoot vs Ergo: 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.
Ergo
2.5COMMS
Ergo keeps tracking IRCv3 upstream while quietly opening its history layer to real databases.
◆ Current state
Ergo ships roughly two releases a year, each announced as a release candidate about a week ahead of the final. The content is consistent: whatever IRCv3 specifications have firmed up since the last cycle, plus bug fixes and config-format adjustments. The one structural change in this window was pluggable history storage, which took Ergo off its embedded database as the only option.
◆ Where it's heading
This is a project with a stable release ritual and a narrow remit: be a modern IRC server that implements the spec correctly and runs as a single binary. Feature work arrives as specification support rather than product invention. The exception is the operational surface — history backends and the HTTP API — where Ergo has been steadily making itself easier to run alongside existing infrastructure instead of as a self-contained island.
◆ Prediction
The v2.19.0 final should follow its release candidate within a week or two on the established pattern; the config-format break flagged in that RC is the main thing operators will need to handle on upgrade.
Alternatives to Chatwoot and Ergo
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 Ergo.
Element
Element 1.12.33 ships: simpler recovery keys, mandatory verification, no libolm migration.
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.
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 Ergo alternatives →
Recent activity from Chatwoot and Ergo
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
- 3mo agoErgov2.19.0-rc1: IRCv3 updates and a breaking config change
- 7mo agoErgov2.18.0-rc1 adds PostgreSQL and SQLite history backends ⚡
- 10mo agoErgov2.17.0-rc1 implements the IRCv3 metadata specification
- 1y agoErgov2.16.0-rc1: bug fixes and minor updates
Frequently asked questions
What is the difference between Chatwoot and Ergo?
Both compete on the same themes — self-hosted — within Comms. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 2.5), 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 Ergo?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Chatwoot is currently shipping more aggressively (velocity 7.5 vs 2.5), 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 Ergo?
Top Ergo alternatives in Comms are ranked by recent ship velocity. Browse the "Ergo alternatives" section above for the current picks, or visit /alternatives/ergo-irc for the full list with editorial commentary on each.