Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of Stalwart and Threema — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Threema's feed is privacy positioning, and this week it had to explain an outage
The feed carries essays far more often than releases. The newest entry is an incident post explaining a series of DDoS attacks that made the service partly unavailable across a Tuesday evening and Wednesday morning, plus the measures taken since. Around it sit position pieces — declining WhatsApp interoperability under the DMA, arguing anonymity belongs in system architecture — with one genuine Threema Work feature, easier tag management in the Management Cockpit.
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.
The feed carries essays far more often than releases. The newest entry is an incident post explaining a series of DDoS attacks that made the service partly unavailable across a Tuesday evening and Wednesday morning, plus the measures taken since. Around it sit position pieces — declining WhatsApp interoperability under the DMA, arguing anonymity belongs in system architecture — with one genuine Threema Work feature, easier tag management in the Management Cockpit.
Threema is competing on stance rather than feature velocity: most posts argue why its architecture is the right one, not what changed in the app. The DDoS post fits that pattern in a different register — availability is the one axis where an architecture argument is settled by operations rather than by essay. Actual product news continues to surface mainly on the Threema Work admin side.
Expect the next posts to return to privacy positioning, with any concrete shipping news most likely being another Management Cockpit administration feature. Whether the DDoS mitigations hold is not something the entries let you judge yet.
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 Threema.
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 Stalwart alternatives → · See all Threema alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Stalwart and Threema 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. Stalwart and Threema 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 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 Threema alternatives in Comms are ranked by recent ship velocity. Browse the "Threema alternatives" section above for the current picks, or visit /alternatives/threema for the full list with editorial commentary on each.