Teable
Secrets get encrypted at rest while the computed-field engine keeps getting shored up
A side-by-side editorial comparison of Flarum and HumHub — 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.
HumHub's public feed carries only betas, and 1.19's is still about surviving the upgrade.
The four releases visible here are all pre-release: 1.19.0-beta.2 and beta.1, and 1.18.0-beta.6 and beta.5 before them. The 1.19 line is dominated by upgrade-path and data-integrity repair — a foreign key violation aborting the comment content_id migration on databases with orphaned rows, fatal errors when purging content whose underlying record was gone, and in beta.2 a fatal SCSS build loop left behind when the 1.19 move of static/themes into protected/humhub stranded an empty theme skeleton. Beta.2 also fixes a real leak: activities from private spaces appearing in the summary mail and dashboard of users holding only a pending invite or join request.
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.
The four releases visible here are all pre-release: 1.19.0-beta.2 and beta.1, and 1.18.0-beta.6 and beta.5 before them. The 1.19 line is dominated by upgrade-path and data-integrity repair — a foreign key violation aborting the comment content_id migration on databases with orphaned rows, fatal errors when purging content whose underlying record was gone, and in beta.2 a fatal SCSS build loop left behind when the 1.19 move of static/themes into protected/humhub stranded an empty theme skeleton. Beta.2 also fixes a real leak: activities from private spaces appearing in the summary mail and dashboard of users holding only a pending invite or join request.
The 1.19 cycle is being spent making the migration survivable on real installations rather than adding capability, which is the usual shape when a schema and directory-layout change meets databases and webroots that have accumulated years of drift. Beta.2 extends that into the installer itself, where an unreachable database was offering to re-set-up a live instance during a transient outage. The permission and visibility fixes point the same way: tightening authorisation and content boundaries is cleanup of an existing model, not an extension of it.
Only beta tags appear in this feed, so a 1.19.0 stable is the obvious next milestone, but nothing here dates it. The beta.1-to-beta.2 gap of about a month is a faster rhythm than the roughly six months between the 1.18 and 1.19 betas.
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 HumHub.
Secrets get encrypted at rest while the computed-field engine keeps getting shored up
Security and governance controls catch up to the Copilot build-out
A social-networking engine in careful maintenance across two supported branches.
7.1.3 ships on the Mac, closing a release spent almost entirely on rebuilding Feedly sync.
Hive keeps tightening the same three seams: planned time, admin control, and AI review scope
A dated canary most days, with the beta line carrying the same commits later.
See all Flarum alternatives → · See all HumHub alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HumHub 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. HumHub 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 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 HumHub alternatives in Collab are ranked by recent ship velocity. Browse the "HumHub alternatives" section above for the current picks, or visit /alternatives/humhub for the full list with editorial commentary on each.