Friendica
Friendica keeps betting on being the fediverse node that speaks everyone else's protocols.
A side-by-side editorial comparison of Synapse and Maddy — release velocity, themes, recent moves, and the top alternatives to consider.
The reference Matrix homeserver shipping protocol work on a tight release train
Synapse is moving through the 1.156–1.158 line at roughly weekly cadence, with release candidates preceding each stable. The functional work is protocol-level: MSC4140 cancellable delayed events with per-user scheduling limits, MSC4354 sticky events exposed over MSC4186 simplified sliding sync, and stabilized ephemeral event sending. Version 1.157.0rc1 removed the deprecated MSC3861 auth delegation, and 1.157.2 was an out-of-band security release addressing several vulnerabilities rated up to high severity.
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.
Synapse is moving through the 1.156–1.158 line at roughly weekly cadence, with release candidates preceding each stable. The functional work is protocol-level: MSC4140 cancellable delayed events with per-user scheduling limits, MSC4354 sticky events exposed over MSC4186 simplified sliding sync, and stabilized ephemeral event sending. Version 1.157.0rc1 removed the deprecated MSC3861 auth delegation, and 1.157.2 was an out-of-band security release addressing several vulnerabilities rated up to high severity.
Development tracks the Matrix spec process directly — features arrive as MSCs graduate, and deprecated experimental paths are removed once replacements stabilize. Sliding sync is the load-bearing effort, with sticky events and ephemeral sending both being routed through it. The security release and the config regression that followed 1.157.0 show the cost of that cadence: fast lines need fast patches.
Expect the 1.158 line to continue folding MSCs into sliding sync, and further removal of experimental_features flags whose MSCs have stabilized, following the MSC3861 precedent.
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.
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.
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.
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 Synapse or Maddy.
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.
Six releases, and every one of them is a security update in some form.
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 Synapse alternatives → · See all Maddy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Synapse 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. Synapse 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 Synapse alternatives in Comms are ranked by recent ship velocity. Browse the "Synapse alternatives" section above for the current picks, or visit /alternatives/synapse for the full list with editorial commentary on each.
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.