Rspamd
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
A side-by-side editorial comparison of Misskey and Openfire — release velocity, themes, recent moves, and the top alternatives to consider.
Misskey 2026.11 ships: a leaner start script, and Node.js 22 no longer boots.
Misskey 2026.11.0 is out after an alpha, two betas and a release candidate in a week. The new start script stops extra processes from staying resident, saving about 50MB per server on the official Docker image, which uses it automatically. Node.js v22 support ends, the minimum is now 24.22.3 or 26.13.1, and NODE_OPTIONS paths now resolve from the repository root. Smaller changes include better display of Mastodon quotes and an autoplay setting for URL previews.
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.
Misskey 2026.11.0 is out after an alpha, two betas and a release candidate in a week. The new start script stops extra processes from staying resident, saving about 50MB per server on the official Docker image, which uses it automatically. Node.js v22 support ends, the minimum is now 24.22.3 or 26.13.1, and NODE_OPTIONS paths now resolve from the repository root. Smaller changes include better display of Mastodon quotes and an autoplay setting for URL previews.
Misskey's last two cycles are about making servers cheaper and safer to run: tighter Sentry data-collection defaults in 2026.10, lower memory and newer Node versions in 2026.11. Each one carries a breaking requirement that admins must check before upgrading.
Expect 2026.11.x patch releases for upgrade problems, especially around custom NODE_OPTIONS and systemd units. The entries do not show what the next feature cycle will target.
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.
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 Misskey or Openfire.
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.
SlickText's feed is all SMS buying guides; no product release has surfaced since RCS.
See all Misskey alternatives → · See all Openfire alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Misskey 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. Misskey 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 Misskey alternatives in Comms are ranked by recent ship velocity. Browse the "Misskey alternatives" section above for the current picks, or visit /alternatives/misskey for the full list with editorial commentary on each.
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.