Rspamd
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
A side-by-side editorial comparison of Openfire and Session — release velocity, themes, recent moves, and the top alternatives to consider.
Openfire keeps its XMPP server current without changing what it is.
Openfire ships a maintenance release every one to two months, each a mix of dependency upgrades, MUC and pubsub correctness fixes, and occasional security hardening. 5.1.2 follows that shape exactly: Jetty, log4j2, and the PostgreSQL driver moved forward, three inapplicable Tomcat CVEs suppressed, and a set of MUC self-ping errors corrected to return the right XMPP error types. The last release with real feature content was 5.1.0 in June, which added channel binding and an admin console for failed server-to-server connections.
Session ships new app versions and node upgrades while Pro stays on hold.
Session's 2026 started with a funding scare, then community support restored its runway in June. Session Pro reached a beta in app stores in September before its launch was paused in October during talks with an allied privacy ecosystem. Since then the work is infrastructure: lighter Session Node software, an update on Protocol v2, and on November 9 new iOS, Android and Desktop releases with further voluntary node upgrades and progress on a unified client.
Openfire ships a maintenance release every one to two months, each a mix of dependency upgrades, MUC and pubsub correctness fixes, and occasional security hardening. 5.1.2 follows that shape exactly: Jetty, log4j2, and the PostgreSQL driver moved forward, three inapplicable Tomcat CVEs suppressed, and a set of MUC self-ping errors corrected to return the right XMPP error types. The last release with real feature content was 5.1.0 in June, which added channel binding and an admin console for failed server-to-server connections.
The project's direction is protocol conformance and operational currency rather than new capability. Recent cycles have gone into XEP compliance details - self-ping error semantics, XEP-0398 presence handling, base64 whitespace tolerance - and into keeping the dependency tree clean enough to pass a scanner. That is a reasonable posture for infrastructure a decade into deployment, and nothing in the last six releases suggests a change of scope.
Expect the same cadence: another patch in four to eight weeks carrying library bumps and MUC or pubsub conformance fixes, with anything larger held for a 5.2 line.
Session's 2026 started with a funding scare, then community support restored its runway in June. Session Pro reached a beta in app stores in September before its launch was paused in October during talks with an allied privacy ecosystem. Since then the work is infrastructure: lighter Session Node software, an update on Protocol v2, and on November 9 new iOS, Android and Desktop releases with further voluntary node upgrades and progress on a unified client.
With Pro paused, Session is spending its effort on the network and the client codebase: lighter nodes, Protocol v2 with forward secrecy and post-quantum encryption, and one client for all platforms. Monetization waits on the outside talks.
Expect a Protocol v2 alpha or the unified client to be the next visible release; Pro's timing depends on talks the entries do not detail.
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 Openfire or Session.
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
Twilio's voice AI stops cutting callers off mid-sentence, using its own turn-taking model.
Salesmsg adds call-back requests and a one-click Emergency Stop for all outbound texts.
Element 1.12.35 follows the call picture-in-picture release with one desktop storage fix.
Krisp moves call transcripts and live captions to cloud transcription in KrispCX 2.84.4.
Misskey 2026.11 ships: a leaner start script, and Node.js 22 no longer boots.
See all Openfire alternatives → · See all Session alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Session is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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. Session is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 Openfire alternatives in Comms are ranked by recent ship velocity. Browse the "Openfire alternatives" section above for the current picks, or visit /alternatives/openfire for the full list with editorial commentary on each.
Top Session alternatives in Comms are ranked by recent ship velocity. Browse the "Session alternatives" section above for the current picks, or visit /alternatives/session for the full list with editorial commentary on each.