← Back to home
Comparison · Comms

Ergo vs Maddy

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

Shared themes:self-hosted

Ergo vs Maddy: at a glance

FeatureErgoMaddy
SectorCommsComms
Velocity score2.50.0
Sparks · 30d00
Top themesirc, ircv3, self-hosted, release-candidatesmail-server, self-hosted, golang, security
Last editorial update3mo ago1d ago
WebsiteVisit →Visit →

What is Ergo?

Ergo keeps tracking IRCv3 upstream while quietly opening its history layer to real databases.

Ergo ships roughly two releases a year, each announced as a release candidate about a week ahead of the final. The content is consistent: whatever IRCv3 specifications have firmed up since the last cycle, plus bug fixes and config-format adjustments. The one structural change in this window was pluggable history storage, which took Ergo off its embedded database as the only option.

Read the full Ergo trajectory →

What is Maddy?

maddy's latest release is a security fix, five months after its last feature work.

maddy is an all-in-one Go mail server for SMTP and IMAP. Its most recent release, 0.9.6 in October, requires explicit trust for PROXY protocol headers and closes an auth misconfiguration that could skip password checks. Before that, the 0.9 line ran from March to May: no-downtime config reload in 0.9.0, an LDAP injection fix, and removal of long-deprecated commands.

Read the full Maddy trajectory →

Ergo vs Maddy: editorial side-by-side

E
Ergo
COMMS
2.5

Ergo keeps tracking IRCv3 upstream while quietly opening its history layer to real databases.

◆ Current state

Ergo ships roughly two releases a year, each announced as a release candidate about a week ahead of the final. The content is consistent: whatever IRCv3 specifications have firmed up since the last cycle, plus bug fixes and config-format adjustments. The one structural change in this window was pluggable history storage, which took Ergo off its embedded database as the only option.

◆ Where it's heading

This is a project with a stable release ritual and a narrow remit: be a modern IRC server that implements the spec correctly and runs as a single binary. Feature work arrives as specification support rather than product invention. The exception is the operational surface — history backends and the HTTP API — where Ergo has been steadily making itself easier to run alongside existing infrastructure instead of as a self-contained island.

◆ Prediction

The v2.19.0 final should follow its release candidate within a week or two on the established pattern; the config-format break flagged in that RC is the main thing operators will need to handle on upgrade.

M
Maddy
COMMS
0.0

maddy's latest release is a security fix, five months after its last feature work.

◆ Current state

maddy is an all-in-one Go mail server for SMTP and IMAP. Its most recent release, 0.9.6 in October, requires explicit trust for PROXY protocol headers and closes an auth misconfiguration that could skip password checks. Before that, the 0.9 line ran from March to May: no-downtime config reload in 0.9.0, an LDAP injection fix, and removal of long-deprecated commands.

◆ Where it's heading

The project is moving from convenient defaults to safer ones, accepting breaking changes on the way. Older conveniences such as SASL LOGIN, STARTTLS plaintext fallback and the maddyctl symlink have been removed, and 0.9.1 flagged several DNS providers for removal in 0.10.0. Two of the last four releases were security fixes.

◆ Prediction

0.10.0 is scoped by the deprecations announced in 0.9.1: expect the flagged DNS providers to go and gandi to require Bearer tokens. The five-month gap gives no date for it.

Alternatives to Ergo 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 Ergo or Maddy.

See all Ergo alternatives → · See all Maddy alternatives →

Recent activity from Ergo and Maddy

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

  1. 1mo agoMaddymaddy 0.9.6 fixes PROXY trust and auth bypass misconfig
  2. 3mo agoErgov2.19.0-rc1: IRCv3 updates and a breaking config change
  3. 5mo agoMaddymaddy 0.9.5 fixes nested pipeline logging and systemd reload reporting
  4. 6mo agoMaddymaddy 0.9.4 removes the maddyctl symlink and implicit run command
  5. 6mo agoMaddymaddy 0.9.3 patches an LDAP injection flaw in auth.ldap
  6. 7mo agoMaddymaddy 0.9.2 fixes an rspamd panic on unspecified tls_client
  7. 7mo agoMaddymaddy 0.9.1 flags libdns providers for removal in 0.10.0
  8. 7mo agoErgov2.18.0-rc1 adds PostgreSQL and SQLite history backends ⚡
  9. 10mo agoErgov2.17.0-rc1 implements the IRCv3 metadata specification
  10. 1y agoErgov2.16.0-rc1: bug fixes and minor updates

Frequently asked questions

What is the difference between Ergo and Maddy?

Both compete on the same themes — self-hosted — within Comms. Ergo is currently shipping more aggressively (velocity 2.5 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 Ergo better than Maddy?

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

Top Ergo alternatives in Comms are ranked by recent ship velocity. Browse the "Ergo alternatives" section above for the current picks, or visit /alternatives/ergo-irc 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.