Rspamd
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
A side-by-side editorial comparison of NanoMQ and Session — release velocity, themes, recent moves, and the top alternatives to consider.
NanoMQ follows its hardening run by moving onto Zephyr microcontrollers.
NanoMQ 0.25.7, published on 21 October and described as a beta, runs on the Zephyr RTOS after platform-layer work on memory allocation for microkernel environments. It also pushes the multi-tenant mountpoint logic down into the transport layer, gives each bridge its own cache with REST control, lets operators kick clients by ID over the API, and supports PKCS#11 hardware keys with certificate-to-username mapping. 0.25.6 in August had been a protocol-conformance and auth-race fix release.
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.
NanoMQ 0.25.7, published on 21 October and described as a beta, runs on the Zephyr RTOS after platform-layer work on memory allocation for microkernel environments. It also pushes the multi-tenant mountpoint logic down into the transport layer, gives each bridge its own cache with REST control, lets operators kick clients by ID over the API, and supports PKCS#11 hardware keys with certificate-to-username mapping. 0.25.6 in August had been a protocol-conformance and auth-race fix release.
0.25.5 dropped MIPS and ARMel binaries to concentrate on correctness, and 0.25.6 spent that effort on MQTT conformance. 0.25.7 points the broker at smaller and more locked-down hardware instead: an RTOS target, hardware security modules and per-device certificate identity. That is a move toward embedded, fleet-managed deployments rather than gateway servers.
Expect follow-up 0.25.x releases fixing Zephyr-specific issues, since 0.25.7 is labelled a first beta. The SipHash client ID question raised in 0.25.2 still has no resolution in these entries.
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 NanoMQ 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 NanoMQ 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 NanoMQ alternatives in Comms are ranked by recent ship velocity. Browse the "NanoMQ alternatives" section above for the current picks, or visit /alternatives/nanomq 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.