Genesys
Genesys Cloud's weekly train widens channels and languages; the AI story stays in the blog.
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.
Chatwoot vs Ergo: at a glance
| Feature | Chatwoot | Ergo |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | ai-agents, customer-support, voice, help-center | irc, ircv3, self-hosted, release-candidates |
| Last editorial update | 2d ago | 3h ago |
| Website | — | Visit → |
What is Chatwoot?
Chatwoot added voice, then turned its AI agent loose on the conversations it already resolved.
Chatwoot spent years building text-first support — live chat, email, WhatsApp, social, help center — and in June added voice calls in beta, closing the last channel gap against the incumbent suites it competes with. Alongside that, Captain has moved from a reply assistant to something that acts: calling external APIs during a conversation, keeping its own document set fresh, and now proposing FAQs mined from resolved tickets. The rest of the release stream is agent-workflow polish — chatlist layouts, editor resizing, bulk help-center edits — shipped every two to four weeks.
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
6.3COMMS
Chatwoot added voice, then turned its AI agent loose on the conversations it already resolved.
◆ Current state
Chatwoot spent years building text-first support — live chat, email, WhatsApp, social, help center — and in June added voice calls in beta, closing the last channel gap against the incumbent suites it competes with. Alongside that, Captain has moved from a reply assistant to something that acts: calling external APIs during a conversation, keeping its own document set fresh, and now proposing FAQs mined from resolved tickets. The rest of the release stream is agent-workflow polish — chatlist layouts, editor resizing, bulk help-center edits — shipped every two to four weeks.
◆ Where it's heading
Two arcs are running in parallel. Channel completeness is nearly done, so the differentiation is shifting to Captain, which is being built as a closed loop: it answers from a knowledge base, watches which conversations humans resolve, and feeds the gaps back into that knowledge base without anyone curating it. The help center is being rebuilt to carry that weight — a documentation layout, bulk reorganisation, editor and published output brought into alignment — because it is the substrate Captain reads from, not just a customer-facing page.
◆ Prediction
The obvious next step is letting Captain publish approved FAQ suggestions straight into the help center rather than handing back a review list, which would complete the loop end to end. Voice is still in beta and has no Captain story yet, so expect the two arcs to meet — transcription and Captain handling on calls.
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.
MirrorFly
MirrorFly's feed sells the chat-SDK category; the SDK itself never appears in it.
Trumpia
Trumpia publishes SMS explainers weekly and product notes never — including the same post twice.
Matrix Bridge
A bridge library whose releases are mostly its dependencies moving underneath it.
The Lounge
The Lounge ships steadily but publishes release notes that say nothing.
Discord
Discord is turning the chat client into a storefront and Nitro into a rewards program.
See all Chatwoot alternatives → · See all Ergo alternatives →
Recent activity from Chatwoot and Ergo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoChatwootHelp Center: safer edits, easier organizing, and faster search
- 6d agoChatwootMeet the Improved Captain: Smarter Suggestions and a Better Assistant Overview ⚡
- 22d agoErgov2.19.0-rc1: IRCv3 updates and a breaking config change
- 1mo agoChatwootIntroducing voice calls in Chatwoot ⚡
- 2mo agoChatwootCaptain Documents Now Stay Up to Date
- 2mo agoChatwootA better layout for documentation-heavy help centers
- 2mo agoChatwootAI Assist on mobile
- 4mo agoErgov2.18.0-rc1 adds PostgreSQL and SQLite history backends ⚡
- 7mo 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?
They serve adjacent needs but don't currently overlap on shipped themes. Chatwoot is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
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 6.3 vs 2.5), 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.
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.