Brosix
Brosix follows its communities launch with a referral push and a private-room how-to.
A side-by-side editorial comparison of Rocket.Chat and Apache RocketMQ — release velocity, themes, recent moves, and the top alternatives to consider.
Rocket.Chat 9.0 puts LDAP, SAML and Custom OAuth behind a plan and removes seven logins.
The 9.0 candidate line opened on 27 October, and its lead is a licensing change: LDAP, SAML and Custom OAuth now require a premium plan, and seven login providers are removed, including Facebook, LinkedIn and X. rc.0 also drops anonymous write, the Atlassian Crowd integration, Gravatar and the raw MongoDB query parameters, while rc.3 moves REST refusals to a single 403 shape. 8.9.0 LTS, dated 5 October, is supported until 31 October 2027.
The RocksDB migration reaches native code as the legacy DLedger broker mode is marked for removal
The 5.x line continues to replace storage internals with RocksDB and to retire the mechanisms it supersedes. 5.5.1, the first release since April, swaps the pure-Java ConsumeQueue compaction filter for a native RocksDB CqCompactionFilter behind a cross-platform JNI shim, drops the shaded rocketmq-rocksdb dependency, and deprecates the legacy Broker DLedger mode. Lite Mode, introduced in 5.5.0, received stability work rather than the client-side adoption path it still needs. Alongside this sit fastjson 1.x removal and a long list of Proxy, Pop and Remoting fixes.
The 9.0 candidate line opened on 27 October, and its lead is a licensing change: LDAP, SAML and Custom OAuth now require a premium plan, and seven login providers are removed, including Facebook, LinkedIn and X. rc.0 also drops anonymous write, the Atlassian Crowd integration, Gravatar and the raw MongoDB query parameters, while rc.3 moves REST refusals to a single 403 shape. 8.9.0 LTS, dated 5 October, is supported until 31 October 2027.
Calling keeps maturing on its own track: rc.1 adds a noise cancellation choice to native LiveKit calls, with RNNoise served by the workspace itself. The bigger change sorts the install base. Community workspaces keep local login plus Google, GitHub, GitLab, Apple and Nextcloud, while directory sign-in moves to paid plans, with a free Starter plan for eligible organizations of up to 50 users. The rest of 9.0 reads as a clean-up, collecting deprecations announced in 8.9 and breaking REST clients that read the old error codes.
Expect more fix-and-bump candidates before 9.0.0 goes final, since rc.2 was a bare bump and rc.3 is mostly error-shape changes. How many Community workspaces hit the login change at upgrade is unclear; the notes already point admins to recovery steps.
The 5.x line continues to replace storage internals with RocksDB and to retire the mechanisms it supersedes. 5.5.1, the first release since April, swaps the pure-Java ConsumeQueue compaction filter for a native RocksDB CqCompactionFilter behind a cross-platform JNI shim, drops the shaded rocketmq-rocksdb dependency, and deprecates the legacy Broker DLedger mode. Lite Mode, introduced in 5.5.0, received stability work rather than the client-side adoption path it still needs. Alongside this sit fastjson 1.x removal and a long list of Proxy, Pop and Remoting fixes.
The storage convergence is now deep enough to cross the JNI boundary — RocksDB is no longer an alternate index but the substrate, and the project is willing to take on native build complexity across platforms to get its performance. In parallel, deprecating legacy Broker DLedger narrows the replication story toward the jRaft controller, cutting a maintenance branch rather than carrying both. Lite Mode remains the open bet: it is being maintained but not yet extended outward to clients.
With legacy DLedger deprecated rather than removed, a following release that deletes it outright is the natural next step. Whether Lite Mode gains the client and proxy support it needs is still unresolved — 5.5.1 fixed it without broadening it.
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 Rocket.Chat or Apache RocketMQ.
Brosix follows its communities launch with a referral push and a private-room how-to.
VerneMQ follows its year-in-the-making 2.2.0 with a quick round of subscription fixes.
Session survived its funding scare; now Pro is on hold and Protocol v2 is the bet.
Misskey moves to Sentry v11 and keeps shipping security fixes in its monthly releases.
Apprise 2 is out: notify() returns a result object, and 2.1 takes the catalog to 170 services.
RSS.com's changelog is back after ten months, with listener voicemail for podcasts.
See all Rocket.Chat alternatives → · See all Apache RocketMQ 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 2.5), 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 2.5), 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 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.
Top Apache RocketMQ alternatives in Comms are ranked by recent ship velocity. Browse the "Apache RocketMQ alternatives" section above for the current picks, or visit /alternatives/rocketmq for the full list with editorial commentary on each.