← Back to home
Comparison · Comms

Chatwoot vs Maddy

A side-by-side editorial comparison of Chatwoot and Maddy — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:self-hosted

Chatwoot vs Maddy: at a glance

FeatureChatwootMaddy
SectorCommsComms
Velocity score7.50.0
Sparks · 30d00
Top themesai-assistant, customer-support, whatsapp, voice-callingmail-server, self-hosted, golang, zero-downtime-reload
Last editorial update1mo ago2mo 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.

Read the full Chatwoot trajectory →

What is Maddy?

A one-binary mail server learning to behave like production infrastructure.

maddy is an all-in-one SMTP and IMAP server written in Go, aimed at people who want a working mail host without assembling Postfix, Dovecot and a policy daemon themselves. The 0.9 line moved quickly — 0.9.0 through 0.9.5 between late March and late May — with the sequence following a recognisable shape: a feature release, an immediate patch for a broken integration, a security release, then cleanup. Configuration is directive-based, and much of the changelog concerns the behaviour of individual modules like auth.ldap, check.rspamd and check.dnsbl.

Read the full Maddy trajectory →

Chatwoot vs Maddy: editorial side-by-side

C7.5

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.

M
Maddy
COMMS
0.0

A one-binary mail server learning to behave like production infrastructure.

◆ Current state

maddy is an all-in-one SMTP and IMAP server written in Go, aimed at people who want a working mail host without assembling Postfix, Dovecot and a policy daemon themselves. The 0.9 line moved quickly — 0.9.0 through 0.9.5 between late March and late May — with the sequence following a recognisable shape: a feature release, an immediate patch for a broken integration, a security release, then cleanup. Configuration is directive-based, and much of the changelog concerns the behaviour of individual modules like auth.ldap, check.rspamd and check.dnsbl.

◆ Where it's heading

The project is systematically removing the compromises that made early versions convenient. Obsolete SASL LOGIN was disabled by default, the STARTTLS plaintext fallback was dropped, the maddyctl symlink behaviour and the implicit run command were deleted after four years of deprecation warnings, and libdns providers that have not kept up with 1.x are being cut. Running the other way is operational maturity: no-downtime config reload, queue-length metrics, OpenMetrics fixes, systemd readiness reporting, and SLSA build attestations on release artifacts. This is a project moving from hobbyist-friendly to operator-friendly, and accepting breakage to get there.

◆ Prediction

0.10.0 is already scoped by the deprecations announced in 0.9.1 — expect the flagged libdns providers to be removed and gandi to require Bearer tokens. Given the 0.9.x pattern, a feature release followed quickly by an integration fix is the likely shape.

Alternatives to Chatwoot and Maddy

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 Maddy.

See all Chatwoot alternatives → · See all Maddy alternatives →

Recent activity from Chatwoot and Maddy

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoChatwootCaptain V1 is retiring: every account moves to the new Captain ⚡
  2. 1mo agoChatwootMore control over Captain Assistant behaviour ⚡
  3. 1mo agoChatwootImproved Help Center media uploads
  4. 1mo agoChatwootSupport for WhatsApp usernames and BSUIDs
  5. 1mo agoChatwootDecide when calls are recorded and transcribed
  6. 1mo agoChatwootGuided manual setup for WhatsApp inboxes
  7. 5mo agoMaddymaddy 0.9.5 fixes nested pipeline logging and systemd reload reporting
  8. 6mo agoMaddymaddy 0.9.4 removes the maddyctl symlink and implicit run command
  9. 6mo agoMaddymaddy 0.9.3 patches an LDAP injection flaw in auth.ldap
  10. 7mo agoMaddymaddy 0.9.2 fixes an rspamd panic on unspecified tls_client
  11. 7mo agoMaddymaddy 0.9.1 flags libdns providers for removal in 0.10.0
  12. 7mo agoMaddymaddy 0.9.0 adds no-downtime configuration reloading ⚡

Frequently asked questions

What is the difference between Chatwoot and Maddy?

Both compete on the same themes — self-hosted — within Comms. 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 Maddy?

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 Maddy?

Top Maddy alternatives in Comms are ranked by recent ship velocity. Browse the "Maddy alternatives" section above for the current picks, or visit /alternatives/maddy for the full list with editorial commentary on each.