Netcore Cloud
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
A side-by-side editorial comparison of Roundcube and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
Roundcube is shipping matched security pairs across 1.7 and 1.6 LTS, roughly monthly.
Every release in this window is a security update, and they arrive in matched pairs — the same fix set landed on the 1.7 stable branch and backported to the 1.6 LTS branch minutes apart. The August pair closes eleven reported issues, including remote code execution through the markasjunk plugin's cmd_learn driver, IMAP command injection via LITERAL+ byte-count desynchronization, LDAP filter injection through unescaped substitution in search_filter, arbitrary Sieve script injection past managesieve_disabled_actions, multiple SSRF filter bypasses, and stored XSS. The June and July pairs follow the same structure with different findings.
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.
Every release in this window is a security update, and they arrive in matched pairs — the same fix set landed on the 1.7 stable branch and backported to the 1.6 LTS branch minutes apart. The August pair closes eleven reported issues, including remote code execution through the markasjunk plugin's cmd_learn driver, IMAP command injection via LITERAL+ byte-count desynchronization, LDAP filter injection through unescaped substitution in search_filter, arbitrary Sieve script injection past managesieve_disabled_actions, multiple SSRF filter bypasses, and stored XSS. The June and July pairs follow the same structure with different findings.
Roundcube is absorbing sustained external security-research attention and has settled into a repeatable response cadence: fix, pair the branches, ship. The recurring categories are telling — HTML and CSS sanitizer bypasses via SVG attributes, SSRF filters defeated by address-space and hostname tricks, and injection through plugin drivers — which means the same attack surfaces keep yielding new variants rather than being closed once. The 1.5 branch received its last pair in March; since 1.7.0 arrived in May, maintenance has narrowed to two branches instead of three.
Expect the next release to be another 1.7/1.6 security pair rather than a feature drop, and to include further sanitizer or URL-fetch bypass fixes, since those two categories have recurred in every pair in this window.
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 Roundcube or Stalwart.
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
Element Web is opening an extension surface while rebuilding its timeline underneath.
Signal's beta train keeps trickling small comfort settings between maintenance drops
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
Chatwoot is making Captain something a support team can scope, schedule and hand back.
Krisp is selling real-time voice manipulation to contact centers, and the defense against it too.
See all Roundcube 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. Roundcube 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. Roundcube 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 Roundcube alternatives in Comms are ranked by recent ship velocity. Browse the "Roundcube alternatives" section above for the current picks, or visit /alternatives/roundcube 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.