Mattermost
Mattermost v11.11 adds data spillage exposure tracking as v12.0 breaking changes loom
A side-by-side editorial comparison of HumHub and Nextcloud — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Nextcloud runs three LTS branches in parallel, shipping bug fixes and quiet performance wins.
Nextcloud is simultaneously maintaining three major release lines (32.x, 33.x, 34.x), publishing patch updates every few weeks. Recent work fixes file-sharing edge cases, corrects share permission logic, and patches OCM federation bugs. Performance work targets group membership lookups, swapping full group-object fetches for leaner ID-only queries across branches.
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.
Nextcloud is simultaneously maintaining three major release lines (32.x, 33.x, 34.x), publishing patch updates every few weeks. Recent work fixes file-sharing edge cases, corrects share permission logic, and patches OCM federation bugs. Performance work targets group membership lookups, swapping full group-object fetches for leaner ID-only queries across branches.
The three-track maintenance cadence signals a hardening phase following v34's release, prioritizing stability over new surface area. OCM fixes accumulating across branches suggest cross-instance federation use is growing and generating real-world bug reports. If this pattern holds, a v35 feature push is the next inflection point — the current batch is largely invisible to end users.
The next meaningful surface change will likely come with v35 feature work; the cross-branch group-query performance push and OCM federation fixes hint that enterprise scale and cross-instance collaboration are the focus areas going into the next major.
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 HumHub or Nextcloud.
Mattermost v11.11 adds data spillage exposure tracking as v12.0 breaking changes loom
SiYuan v3.8.4 beta cycle adds agent-controlled database fields, MiniMax image gen, and skill file management
GitHub Copilot gets cost-aware inference tiers as enterprise AI tooling tightens across the platform.
Teable adds Composio integration and Scheduled Routines, pivoting from spreadsheet to agentic workflow platform.
Happeo doubles down on SEO content to own intranet search terms for mid-market buyers.
AFFiNE ships stable iOS Share Extension imports while patching editor correctness and selfhost deployment
See all HumHub alternatives → · See all Nextcloud alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HumHub and Nextcloud are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 and Nextcloud are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
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.
Top Nextcloud alternatives in Collab are ranked by recent ship velocity. Browse the "Nextcloud alternatives" section above for the current picks, or visit /alternatives/nextcloud for the full list with editorial commentary on each.