← Back to home
Comparison · Comms

Apprise vs Maddy

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

Apprise vs Maddy: at a glance

FeatureAppriseMaddy
SectorCommsComms
Velocity score6.30.0
Sparks · 30d10
Top themesnotifications, major-version, deprecation, routingmail-server, self-hosted, golang, zero-downtime-reload
Last editorial update15d ago1mo ago
WebsiteVisit →Visit →

What is Apprise?

The final v1.x release slipped by one patch, but the v2 deadline stands.

Apprise is a Python notification library that fans a single call out to more than 150 services. Weighted tagging in v1.11 turned that fan-out into ordered delivery with fallback, and the releases since have been service accretion and bug clearance. v1.13.0 was announced as the last of the v1.x line; v1.13.1 has now shipped anyway, adding Signalgrid and Lauther support and fixing a memory-backed attachment failure, with the maintainer repeating the end-of-line notice and adding that he means it this time.

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

Apprise vs Maddy: editorial side-by-side

A
Apprise
COMMS
6.3

The final v1.x release slipped by one patch, but the v2 deadline stands.

◆ Current state

Apprise is a Python notification library that fans a single call out to more than 150 services. Weighted tagging in v1.11 turned that fan-out into ordered delivery with fallback, and the releases since have been service accretion and bug clearance. v1.13.0 was announced as the last of the v1.x line; v1.13.1 has now shipped anyway, adding Signalgrid and Lauther support and fixing a memory-backed attachment failure, with the maintainer repeating the end-of-line notice and adding that he means it this time.

◆ Where it's heading

The v1 line is being closed out in patches rather than stopped cleanly, which is the normal shape of a maintainer-led project absorbing community pull requests faster than it can cut a major version. The ask to downstream projects has not changed — pin to >=1.0.0,<2.0.0 — and v1.x is stated to keep security support for a year or two after v2 lands. What v2 actually breaks is still not described in any of these entries.

◆ Prediction

The next release is likely another v1.x patch of the same shape — community service plugins plus attachment and protocol fixes — unless a v2 alpha appears first. Nothing in these entries indicates which.

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

See all Apprise alternatives → · See all Maddy alternatives →

Recent activity from Apprise and Maddy

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

  1. 15d agoAppriseFinal v1.x patch: attachment fix and two more services
  2. 26d agoAppriseLast release of the v1.x line — pin before v2 breaks
  3. 2mo agoApprisePast 150 services, with HTML-to-Markdown conversion built in
  4. 3mo agoAppriseTags gain weights, turning notification fan-out into failover
  5. 3mo agoMaddymaddy 0.9.5 fixes nested pipeline logging and systemd reload reporting
  6. 4mo agoMaddymaddy 0.9.4 removes the maddyctl symlink and implicit run command
  7. 5mo agoMaddymaddy 0.9.3 patches an LDAP injection flaw in auth.ldap
  8. 5mo agoMaddymaddy 0.9.2 fixes an rspamd panic on unspecified tls_client
  9. 5mo agoMaddymaddy 0.9.1 flags libdns providers for removal in 0.10.0
  10. 5mo agoMaddymaddy 0.9.0 adds no-downtime configuration reloading
  11. 5mo agoAppriseXMPP multi-user chat and the groundwork for the URL Builder
  12. 6mo agoAppriseIRC support arrives and XMPP returns via Slixmpp

Frequently asked questions

What is the difference between Apprise and Maddy?

They serve adjacent needs but don't currently overlap on shipped themes. Apprise is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Apprise better than Maddy?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Apprise is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Apprise?

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