← Back to home
Comparison · Comms

Synapse vs Maddy

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

Synapse vs Maddy: at a glance

FeatureSynapseMaddy
SectorCommsComms
Velocity score5.00.0
Sparks · 30d00
Top themesmatrix, federation, open-source, protocolmail-server, self-hosted, golang, zero-downtime-reload
Last editorial update1d ago2h ago
WebsiteVisit →Visit →

What is Synapse?

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.

Read the full Synapse 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 →

Synapse vs Maddy: editorial side-by-side

S
Synapse
COMMS
5.0

The reference Matrix homeserver shipping protocol work on a tight release train

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

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

See all Synapse alternatives → · See all Maddy alternatives →

Recent activity from Synapse and Maddy

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

  1. 1d agoSynapse1.158 release candidate opens
  2. 4d agoSynapseOut-of-band security release for federated homeservers
  3. 9d agoSynapseConfig regression on falsy experimental_features fixed
  4. 11d agoSynapseCancellable delayed events reach stable
  5. 16d agoSynapseMSC3861 auth delegation removed in 1.157 RC
  6. 25d agoSynapseSticky events exposed over simplified sliding sync
  7. 2mo agoMaddymaddy 0.9.5 fixes nested pipeline logging and systemd reload reporting
  8. 3mo agoMaddymaddy 0.9.4 removes the maddyctl symlink and implicit run command
  9. 3mo agoMaddymaddy 0.9.3 patches an LDAP injection flaw in auth.ldap
  10. 4mo agoMaddymaddy 0.9.2 fixes an rspamd panic on unspecified tls_client
  11. 4mo agoMaddymaddy 0.9.1 flags libdns providers for removal in 0.10.0
  12. 4mo agoMaddymaddy 0.9.0 adds no-downtime configuration reloading

Frequently asked questions

What is the difference between Synapse and Maddy?

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.

Is Synapse better than Maddy?

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.

What are the best alternatives to Synapse?

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.

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.