Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of Element and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
Element Web is opening an extension surface while rebuilding its timeline underneath.
Element Web ships on a steady RC-then-final cadence, and two threads dominate the last month. The first is presence: custom user status has been landing piece by piece across releases — member list, room header, autocomplete, room summary — and now includes on-a-call state that users can set and clear themselves. The second is a module system, which reached v1.0.0 across four separate modules in early August and keeps gaining API surface.
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.
Element Web ships on a steady RC-then-final cadence, and two threads dominate the last month. The first is presence: custom user status has been landing piece by piece across releases — member list, room header, autocomplete, room summary — and now includes on-a-call state that users can set and clear themselves. The second is a module system, which reached v1.0.0 across four separate modules in early August and keeps gaining API surface.
The module work is the more consequential of the two. Banner, Widget Toggles, Widget Lifecycle, and Restricted Guests all hit v1.0.0 on the same day, and the following release adds a Module API for storage helpers plus a dedicated modules docker image — infrastructure for deployments to extend the client rather than fork it. Alongside that, Timeline MVVM has begun as a shared TimelineView, which reads as the opening step of a longer architectural refactor. Individual releases stay incremental; the pattern across them is Element Web becoming a platform its operators configure.
Expect Timeline MVVM to arrive in numbered stages across coming releases, and the Module API to keep widening beyond storage helpers as the four v1.0.0 modules run into what they can't yet reach.
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 Element 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 Element 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. Element 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. Element 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 Element alternatives in Comms are ranked by recent ship velocity. Browse the "Element alternatives" section above for the current picks, or visit /alternatives/element-web 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.