Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of mailcow and Matrix — release velocity, themes, recent moves, and the top alternatives to consider.
mailcow's release notes are almost entirely upstream security currency.
mailcow ships named seasonal releases with lettered revisions, and nearly every revision exists to pull in an upstream security fix - Redis, ClamAV, SOGo, Rspamd, nginx, unbound, Postfix. Revision B of the Mooly 2026 release updates Redis 7.4.10, ClamAV 1.4.6, and SOGo 5.12.10, adds minor web UI and nginx hardening, and removes a legacy DeltaChat sieve rule. The last release with genuinely new features was the March cut, which added forced 2FA, ACME DNS-01 challenges, and a passwordless autodiscover endpoint.
Matrix ships spec, not product — the MSC queue keeps filling while nothing reaches final comment
The weekly newsletter is the whole feed, and its shape barely varies: a Matrix Live episode, community events, and a spec roundup. This week brings three new MSCs — an incompatible-server error code, state event power levels, and OAuth 2.0 refresh token error handling — with nothing in final comment period and nothing accepted. The 08-14 issue leads on local-first Matrix and FrOSCon.
mailcow ships named seasonal releases with lettered revisions, and nearly every revision exists to pull in an upstream security fix - Redis, ClamAV, SOGo, Rspamd, nginx, unbound, Postfix. Revision B of the Mooly 2026 release updates Redis 7.4.10, ClamAV 1.4.6, and SOGo 5.12.10, adds minor web UI and nginx hardening, and removes a legacy DeltaChat sieve rule. The last release with genuinely new features was the March cut, which added forced 2FA, ACME DNS-01 challenges, and a passwordless autodiscover endpoint.
For a self-hosted mail stack that bundles a dozen upstream components, keeping current with their CVEs is the product, and mailcow has organized its release cadence around exactly that. The pattern is consistent: a named release with some feature content every few months, then lettered revisions that are pure security currency plus small web UI escaping and validation fixes. The web interface is where mailcow's own code gets hardened - HTML escaping in quarantine views and sieve editors recurs across several revisions.
Expect the next entry to be another lettered revision carrying upstream updates, with the next named release likely bundling whatever feature work has accumulated since March.
The weekly newsletter is the whole feed, and its shape barely varies: a Matrix Live episode, community events, and a spec roundup. This week brings three new MSCs — an incompatible-server error code, state event power levels, and OAuth 2.0 refresh token error handling — with nothing in final comment period and nothing accepted. The 08-14 issue leads on local-first Matrix and FrOSCon.
Proposals are accumulating faster than they are being resolved. Several consecutive issues now report new MSCs opened with an empty FCP list and no acceptances, which is what a spec process looks like when authorship outruns review capacity. The substantive engineering themes running underneath are local-first and peer-to-peer Matrix, and homeserver decentralisation — both discussed in talks rather than landed in the spec.
The next issues should keep adding MSCs at a similar rate; the thing to watch is whether any of the newer proposals reach final comment period, since none has in the recent run. Note that this feed truncates at 8000 characters, so server and client release news further down each issue may fall outside what is visible here.
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 mailcow or Matrix.
Chanty's feed is an HR statistics content mill, not a product changelog
Proton Bridge spends its first release in ten weeks on crashes, memory bounds and dead code
Stalwart is chasing mail RFCs and its own storage layer at the same time
Every manual control Mux ships now arrives with a Robots workflow that does it for you
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
Openfire keeps its XMPP server current without changing what it is.
See all mailcow alternatives → · See all Matrix alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mailcow and Matrix are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. mailcow and Matrix are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top mailcow alternatives in Comms are ranked by recent ship velocity. Browse the "mailcow alternatives" section above for the current picks, or visit /alternatives/mailcow for the full list with editorial commentary on each.
Top Matrix alternatives in Comms are ranked by recent ship velocity. Browse the "Matrix alternatives" section above for the current picks, or visit /alternatives/matrix for the full list with editorial commentary on each.