Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of Matrix and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Stalwart is chasing mail RFCs and its own storage layer at the same time
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
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.
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
Two threads run through every release. One is RFC coverage across IMAP, JMAP, CalDAV and WebDAV, implemented close to the specification including drafts. The other is a long tail of protocol-conformance fixes, many of them cases where JMAP and IMAP disagreed about the same state. The newest release adds a third: memory and scheduling limits, which is what a server codebase starts doing when deployments get large enough for defaults to hurt.
Expect continued RFC additions across the JMAP and IMAP surfaces, with more of the storage-tuning work that v0.16.18 started as RocksDB deployments scale.
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 Matrix or Stalwart.
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
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.
mailcow's release notes are almost entirely upstream security currency.
Openfire keeps its XMPP server current without changing what it is.
See all Matrix alternatives → · See all Stalwart alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Matrix and Stalwart 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. Matrix and Stalwart 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 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.
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.