← Back to home
Comparison · Comms

Maddy vs Salesmsg

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

Maddy vs Salesmsg: at a glance

FeatureMaddySalesmsg
SectorCommsComms
Velocity score0.06.3
Sparks · 30d00
Top themesmail-server, self-hosted, golang, zero-downtime-reloadsms-sales, ai-agents, customer-feedback, calling
Last editorial update1mo ago5d ago
WebsiteVisit →Visit →

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 →

What is Salesmsg?

Salesmsg now runs the entire sales-to-NPS loop in one thread — outbound, AI reply, booking, survey, and routing.

Salesmsg has expanded well past SMS messaging into a full-stack sales communication platform. AI agents handle text and voice, execute actions (send SMS, log notes, tag callers, escalate with context), and now route contacts based on NPS scores. The recent addition of native surveys closes a loop that previously required a separate CX tool.

Read the full Salesmsg trajectory →

Maddy vs Salesmsg: editorial side-by-side

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.

S6.3

Salesmsg now runs the entire sales-to-NPS loop in one thread — outbound, AI reply, booking, survey, and routing.

◆ Current state

Salesmsg has expanded well past SMS messaging into a full-stack sales communication platform. AI agents handle text and voice, execute actions (send SMS, log notes, tag callers, escalate with context), and now route contacts based on NPS scores. The recent addition of native surveys closes a loop that previously required a separate CX tool.

◆ Where it's heading

Every release reduces a manual touchpoint. AI agents now handle opt-outs, book meetings from warm replies, write handoff summaries, log post-call notes, and route contacts by survey score — all without rep intervention. The trajectory is toward a fully autonomous outreach-to-feedback cycle where humans review outcomes rather than manage steps.

◆ Prediction

The next move will likely be survey-score-triggered AI agent sequences — automatically enrolling detractors in win-back flows and promoters in referral asks based on NPS results. The routing logic already exists; wiring it to agent automation is the obvious completion.

Alternatives to Maddy and Salesmsg

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

See all Maddy alternatives → · See all Salesmsg alternatives →

Recent activity from Maddy and Salesmsg

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

  1. 6d agoSalesmsgSmarter routing, personalized links, AI opt-out handling
  2. 13d agoSalesmsgFull campaign lifecycle walkthrough (existing features)
  3. 20d agoSalesmsgGive Your Calling AI Agent More Ways to Act, Not Just Talk
  4. 27d agoSalesmsgEscalate Smarter, Notify Faster, and Track Every Handoff With Your AI Agents
  5. 1mo agoSalesmsgCollect and Act on Customer Feedback Right Inside Salesmsg with Surveys
  6. 1mo agoSalesmsgPer-workflow credit tracking, simultaneous call handling, and AI agent stats
  7. 3mo agoMaddymaddy 0.9.5 fixes nested pipeline logging and systemd reload reporting
  8. 4mo agoMaddymaddy 0.9.4 removes the maddyctl symlink and implicit run command
  9. 5mo agoMaddymaddy 0.9.3 patches an LDAP injection flaw in auth.ldap
  10. 5mo agoMaddymaddy 0.9.2 fixes an rspamd panic on unspecified tls_client
  11. 5mo agoMaddymaddy 0.9.1 flags libdns providers for removal in 0.10.0
  12. 5mo agoMaddymaddy 0.9.0 adds no-downtime configuration reloading

Frequently asked questions

What is the difference between Maddy and Salesmsg?

They serve adjacent needs but don't currently overlap on shipped themes. Salesmsg is currently shipping more aggressively (velocity 6.3 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 Maddy better than Salesmsg?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Salesmsg is currently shipping more aggressively (velocity 6.3 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 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.

What are the best alternatives to Salesmsg?

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