GitHub
GitHub killed its model-hosting product and shipped stacked PRs in the same week.
A side-by-side editorial comparison of Flarum and Rocket.Chat — release velocity, themes, recent moves, and the top alternatives to consider.
Flarum's 2.0 has been in release-candidate territory for most of a year.
Flarum is an open-source forum framework whose entire recent release history is the 2.0 train — beta.8 in March, then five release candidates from April through July. The candidates ship on a three-to-six week rhythm, and most of them publish nothing beyond a pointer to the changelog file in the tag. The last releases carrying visible detail were the earlier ones, where the work was database and rendering performance plus extension-compatibility fixes.
All the substance lands in rc.0 — this cycle it's phishing-resistant MFA
Rocket.Chat publishes a release candidate per patch, and the shape is consistent: rc.0 carries the actual changes and every candidate after it is a Meteor version bump with dependency updates. In the 8.7 cycle, rc.0 introduced phishing-resistant multi-factor authentication via a server-side OAuth flow, plus a current field on DeviceManagementSession so the sessions endpoint can flag the caller's own active session. The 8.6 candidates in this window carry nothing but version bumps. Engine versions are pinned across the line at Node 22, Deno 2.3 and MongoDB 8.
Flarum is an open-source forum framework whose entire recent release history is the 2.0 train — beta.8 in March, then five release candidates from April through July. The candidates ship on a three-to-six week rhythm, and most of them publish nothing beyond a pointer to the changelog file in the tag. The last releases carrying visible detail were the earlier ones, where the work was database and rendering performance plus extension-compatibility fixes.
The substance that is visible points at making large forums viable: eliminating N+1 queries on the discussion list, adding a composite index to fix slow unread-notification counts, and caching scheduler timestamps. Those are the changes a forum makes when instances have outgrown the original query patterns. The steady RC cadence with no beta regression suggests a stabilisation grind rather than continued feature work — but the opaque release notes make the remaining scope hard to read from outside.
A 2.0 stable release is the obvious next step, though five candidates without a published scope makes the timing unclear. Watch whether rc.6 arrives on the same three-to-six week spacing or the gap widens.
Rocket.Chat publishes a release candidate per patch, and the shape is consistent: rc.0 carries the actual changes and every candidate after it is a Meteor version bump with dependency updates. In the 8.7 cycle, rc.0 introduced phishing-resistant multi-factor authentication via a server-side OAuth flow, plus a current field on DeviceManagementSession so the sessions endpoint can flag the caller's own active session. The 8.6 candidates in this window carry nothing but version bumps. Engine versions are pinned across the line at Node 22, Deno 2.3 and MongoDB 8.
The work visible here is identity and session control rather than messaging features — who is authenticated, how strongly, and which device is asking. Phishing-resistant MFA and caller-session identification are both procurement concerns for the regulated and self-hosting buyers Rocket.Chat competes for, and they arrive together. The release-candidate pattern means the feed's cadence overstates activity: six entries in this window represent two substantive changes.
Expect the 8.7 line to reach general availability with the MFA flow as its headline, and further session and device-management controls to follow on the same identity track.
Other Collab 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 Flarum or Rocket.Chat.
GitHub killed its model-hosting product and shipped stacked PRs in the same week.
Notion is turning Custom Agents into event-driven workers with their own runtime and billing.
Slack is shipping its developer platform to coding agents, not only to developers.
SiYuan ships polish at alpha-train speed while turning database blocks into a core surface.
AI Proofing gets its manual controls back while Hive builds out creative review and resourcing.
AFFiNE ships twice a day on two trains, and it is all storage plumbing and window polish.
See all Flarum 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 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 Collab products to evaluate alongside.
Top Flarum alternatives in Collab are ranked by recent ship velocity. Browse the "Flarum alternatives" section above for the current picks, or visit /alternatives/flarum for the full list with editorial commentary on each.
Top Rocket.Chat alternatives in Collab are ranked by recent ship velocity. Browse the "Rocket.Chat alternatives" section above for the current picks, or visit /alternatives/rocket-chat for the full list with editorial commentary on each.