Maddy
A one-binary mail server learning to behave like production infrastructure.
A side-by-side editorial comparison of Friendica and mailcow — release velocity, themes, recent moves, and the top alternatives to consider.
Friendica keeps betting on being the fediverse node that speaks everyone else's protocols.
Friendica is a self-hosted decentralised social platform, released on calendar versions two or three times a year with codenames and a consistent structure: a handful of highlights, a security-fix credit, and a pointer to the changelog. The recent run — 2023.12, 2024.03, 2024.08, 2024.12, 2026.01, 2026.05 — shows the cadence thinning, with a full year between 2024.12 and 2026.01. Nearly every release credits externally reported security issues, most recently from Doyensec working with Mastodon.
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.
Friendica is a self-hosted decentralised social platform, released on calendar versions two or three times a year with codenames and a consistent structure: a handful of highlights, a security-fix credit, and a pointer to the changelog. The recent run — 2023.12, 2024.03, 2024.08, 2024.12, 2026.01, 2026.05 — shows the cadence thinning, with a full year between 2024.12 and 2026.01. Nearly every release credits externally reported security issues, most recently from Doyensec working with Mastodon.
Two lines of work dominate. The first is connectors: an initial Bluesky bridge in 2023.05 made bi-directional by 2023.12, Tumblr support maintained throughout, and ATproto account integration plus Bridgy Fed support improved in 2026.05. The second is Channels — the user-defined algorithm for sorting the network stream — introduced in 2023.12 and given performance and sorting work in every release since. Running against both is a deliberate pruning of legacy: OStatus dropped in 2024.12 after the project measured how few servers still needed it, and the fancybox addon deprecated alongside it.
Expect the next release to continue the ATproto and Bridgy Fed integration work and further Channels performance tuning, with the accessibility review started in 2026.01 producing more fixes. Given the year-long gap before 2026.01, the cadence itself is the uncertain part.
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.
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 Friendica or mailcow.
A one-binary mail server learning to behave like production infrastructure.
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.
Slack is shipping its developer platform to coding agents, not only to developers.
See all Friendica alternatives → · See all mailcow alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Comms. mailcow is currently shipping more aggressively (velocity 5.0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mailcow is currently shipping more aggressively (velocity 5.0 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.
Top Friendica alternatives in Comms are ranked by recent ship velocity. Browse the "Friendica alternatives" section above for the current picks, or visit /alternatives/friendica for the full list with editorial commentary on each.
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.