Maddy
A one-binary mail server learning to behave like production infrastructure.
A side-by-side editorial comparison of Stalwart and Element iOS — release velocity, themes, recent moves, and the top alternatives to consider.
Stalwart keeps chasing standards nobody has implemented yet — DKIM2, DMARCbis, now JMAP email push.
Stalwart is a single-binary mail and collaboration server covering JMAP, IMAP, SMTP, CalDAV and CardDAV. The 0.16.x line ships roughly weekly and its additions cluster in one place: implementing IETF drafts and fresh RFCs ahead of the field, while a long tail of JMAP conformance and MTA edge-case fixes runs underneath. The latest release adds JMAP email delivery push notifications, completing a push stack built across the last three releases.
Renamed Element Classic, this client now ships one small fix every few months
Element iOS was renamed Element Classic in v1.11.32, and the release log since then reads like a maintenance branch: single-PR releases spaced weeks to months apart, mostly dependency bumps, build-tooling changes and one user-visible change at a time. The one substantive thread is device verification — a permanent disclaimer banner for unverified sessions arrived in 1.11.35, was temporarily disabled in 1.11.37 because users had no way to reset from the verification screen, got the Reset flow wired up in 1.11.38, and was reinstated as mandatory in 1.11.39.
Stalwart is a single-binary mail and collaboration server covering JMAP, IMAP, SMTP, CalDAV and CardDAV. The 0.16.x line ships roughly weekly and its additions cluster in one place: implementing IETF drafts and fresh RFCs ahead of the field, while a long tail of JMAP conformance and MTA edge-case fixes runs underneath. The latest release adds JMAP email delivery push notifications, completing a push stack built across the last three releases.
The push story is the clearest arc: Web Push payload and subscription fixes in 0.16.10, VAPID per RFC 9749 in 0.16.14, and the emailpush draft in 0.16.16. Parallel to it, 0.16.12 landed DKIM2 and the DMARCbis trio, and the fix lists keep narrowing toward strict-spec behaviour — DMARC alignment reporting, SMTP line-length limits, BDAT error codes. Stalwart is positioning as the reference implementation of modern mail standards rather than competing on features.
Expect the JMAP push work to keep filling in — subscription lifecycle, delivery semantics — alongside continued DKIM2 and DMARCbis refinement as those drafts move. The fix cadence suggests operational hardening around clustering and Redis locking is the other near-term thread.
Element iOS was renamed Element Classic in v1.11.32, and the release log since then reads like a maintenance branch: single-PR releases spaced weeks to months apart, mostly dependency bumps, build-tooling changes and one user-visible change at a time. The one substantive thread is device verification — a permanent disclaimer banner for unverified sessions arrived in 1.11.35, was temporarily disabled in 1.11.37 because users had no way to reset from the verification screen, got the Reset flow wired up in 1.11.38, and was reinstated as mandatory in 1.11.39.
The rename is the clearest signal of direction: this is the legacy client, kept working rather than extended. Recent releases raise the minimum supported OS to satisfy a Jitsi dependency, keep the Xcode toolchain current, and adjust CI — the work of a codebase being maintained, not developed. The verification arc is the exception, and even that is about closing an encryption-hygiene gap rather than adding capability.
With mandatory verification now reinstated and its reset path in place, the remaining work in this branch looks like dependency and toolchain upkeep plus security patches. The entries give no indication of new feature work, so the cadence should stay sparse and single-item.
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 Stalwart or Element iOS.
A one-binary mail server learning to behave like production infrastructure.
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.
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 Stalwart alternatives → · See all Element iOS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Stalwart 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. Stalwart 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 Stalwart alternatives in Comms are ranked by recent ship velocity. Browse the "Stalwart alternatives" section above for the current picks, or visit /alternatives/stalwart for the full list with editorial commentary on each.
Top Element iOS alternatives in Comms are ranked by recent ship velocity. Browse the "Element iOS alternatives" section above for the current picks, or visit /alternatives/element-ios for the full list with editorial commentary on each.