Maddy
A one-binary mail server learning to behave like production infrastructure.
A side-by-side editorial comparison of mailcow and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
Six releases, and every one of them is a security update in some form.
mailcow ships on a monthly tag with lettered revisions, and this window contains no release that isn't security-driven. The May line ran to three revisions in two weeks — an unnamed fix with a CVE identifier withheld until later, SOGo 5.12.8 covering four upstream issues, an unbound CVE, HTML escaping added to the quarantine table, sieve filter editor and queue manager. July brought Rspamd 4.1.0 and later 4.1.4, nginx 1.30.3 and a CVE fix, Postfix moved off bookworm, and a release described only as hardening.
Stalwart keeps chasing standards nobody has implemented yet — DKIM2, DMARCbis, now JMAP email push.
Stalwart is a single-binary mail and collaboration server covering JMAP, IMAP, SMTP, CalDAV and CardDAV. The 0.16.x line ships roughly weekly and its additions cluster in one place: implementing IETF drafts and fresh RFCs ahead of the field, while a long tail of JMAP conformance and MTA edge-case fixes runs underneath. The latest release adds JMAP email delivery push notifications, completing a push stack built across the last three releases.
mailcow ships on a monthly tag with lettered revisions, and this window contains no release that isn't security-driven. The May line ran to three revisions in two weeks — an unnamed fix with a CVE identifier withheld until later, SOGo 5.12.8 covering four upstream issues, an unbound CVE, HTML escaping added to the quarantine table, sieve filter editor and queue manager. July brought Rspamd 4.1.0 and later 4.1.4, nginx 1.30.3 and a CVE fix, Postfix moved off bookworm, and a release described only as hardening.
Two distinct pressures are visible. One is upstream: mailcow bundles Postfix, Rspamd, SOGo, nginx, unbound and Dovecot, so every one of their advisories becomes a mailcow release, and the base image migration from bookworm to trixie is that same maintenance surfacing at the OS layer. The other is the project's own web UI, where output escaping is being retrofitted view by view — quarantine table, sieve editor, queue manager, quarantine overview — which reads as a systematic pass rather than isolated reports. Earlier releases in the feed show where feature work went when it happened: forced 2FA, ACME DNS-01 challenges, and admin controls over EAS and DAV access.
Expect the monthly-plus-revisions rhythm to continue with upstream component bumps driving most of it, and the web UI escaping pass to reach the remaining admin views.
Stalwart is a single-binary mail and collaboration server covering JMAP, IMAP, SMTP, CalDAV and CardDAV. The 0.16.x line ships roughly weekly and its additions cluster in one place: implementing IETF drafts and fresh RFCs ahead of the field, while a long tail of JMAP conformance and MTA edge-case fixes runs underneath. The latest release adds JMAP email delivery push notifications, completing a push stack built across the last three releases.
The push story is the clearest arc: Web Push payload and subscription fixes in 0.16.10, VAPID per RFC 9749 in 0.16.14, and the emailpush draft in 0.16.16. Parallel to it, 0.16.12 landed DKIM2 and the DMARCbis trio, and the fix lists keep narrowing toward strict-spec behaviour — DMARC alignment reporting, SMTP line-length limits, BDAT error codes. Stalwart is positioning as the reference implementation of modern mail standards rather than competing on features.
Expect the JMAP push work to keep filling in — subscription lifecycle, delivery semantics — alongside continued DKIM2 and DMARCbis refinement as those drafts move. The fix cadence suggests operational hardening around clustering and Redis locking is the other near-term thread.
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 mailcow or Stalwart.
A one-binary mail server learning to behave like production infrastructure.
Friendica keeps betting on being the fediverse node that speaks everyone else's protocols.
The original federated social network now ships roughly once every two years.
Renamed Element Classic, this client now ships one small fix every few months
Twilio is selling trust: branded calls, scoped keys, and stricter sender vetting.
Notion is turning Custom Agents into event-driven workers with their own runtime and billing.
See all mailcow alternatives → · See all Stalwart alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mail-server, self-hosted — within Comms. mailcow and Stalwart are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. mailcow and Stalwart are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top mailcow alternatives in Comms are ranked by recent ship velocity. Browse the "mailcow alternatives" section above for the current picks, or visit /alternatives/mailcow for the full list with editorial commentary on each.
Top Stalwart alternatives in Comms are ranked by recent ship velocity. Browse the "Stalwart alternatives" section above for the current picks, or visit /alternatives/stalwart for the full list with editorial commentary on each.