Element
Element rebuilds its timeline with MVVM architecture while cutting legacy OS support in v1.12.28.
A side-by-side editorial comparison of Threema and Rocket.Chat — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Rocket.Chat finishes the 8.8 calling work while the licence wall for SSO gets a date.
The 8.8 candidate line is winding down. rc.2 is a bare Meteor version bump with no user-visible change, following rc.1 which promoted Voice Call Screen Sharing to stable and turned on the in-room call interface for every call, screen sharing available or not, alongside repairs to a message list that could quietly load a whole room's history in the background. The release that still defines the line is rc.0: LDAP and SAML deprecated on non-Premium workspaces with 9.0.0 named as the cutoff, forced end-to-end encryption for new private rooms, classification banners for ABAC-managed rooms, and the apps-engine default runtime moved from Deno to Node.
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.
The 8.8 candidate line is winding down. rc.2 is a bare Meteor version bump with no user-visible change, following rc.1 which promoted Voice Call Screen Sharing to stable and turned on the in-room call interface for every call, screen sharing available or not, alongside repairs to a message list that could quietly load a whole room's history in the background. The release that still defines the line is rc.0: LDAP and SAML deprecated on non-Premium workspaces with 9.0.0 named as the cutoff, forced end-to-end encryption for new private rooms, classification banners for ABAC-managed rooms, and the apps-engine default runtime moved from Deno to Node.
Two threads run at once and point in different directions. The calling stack keeps maturing on its own — voice, then screen sharing, now a consistent in-room surface for both — which is Rocket.Chat absorbing functions its users would otherwise reach for a separate tool to get. Against that, the 9.0 licence requirement for LDAP and SAML sorts the install base: regulated and government deployments that will pay, and unlicensed self-hosted workspaces that were there for the absence of a per-seat bill. The rc train itself has settled into a familiar shape, one substantive rc.0 followed by bumps and fixes.
Expect 8.8 to go final once the message-list fixes settle, with the LDAP and SAML licence requirement, not any calling feature, as the story of 9.0. The open question is whether the Deno-to-Node runtime switch surfaces app compatibility reports before then.
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 Threema or Rocket.Chat.
Element rebuilds its timeline with MVVM architecture while cutting legacy OS support in v1.12.28.
Superhuman rebuilt its mobile apps and wired every inbox into AI assistants — the email client is becoming a suite.
Chatwoot is building an AI-first support platform, with Captain gaining audience targeting and macro automation reaching the keyboard-native workflow.
Signal adds granular notification controls: badge content, muted threads, restore defaults
Zoho Cliq 7.0 bets on AI conversation summaries and Neat hardware to close the gap with enterprise messaging platforms
Krisp adds deepfake detection and expands Voice Translation as its Call Center AI platform deepens enterprise compliance tools.
See all Threema alternatives → · See all Rocket.Chat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rocket.Chat is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. 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. Rocket.Chat is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
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.
Top Rocket.Chat alternatives in Comms are ranked by recent ship velocity. Browse the "Rocket.Chat alternatives" section above for the current picks, or visit /alternatives/rocketchat for the full list with editorial commentary on each.