GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
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 ships three patch lines in a day as 35.0.2 adds webhook metadata and a report API.
Nextcloud released 35.0.2, 34.0.5 and 33.0.10 on the same day, a month after the 35.0.0 major that swapped OnlyOffice for Euro-Office and added FrankenPHP support. The backports share a security-flavored core: a CSRF token on the share-accept endpoint, upload checks against session and share tokens, and logs that no longer leak sensitive data. 35.0.2 also adds richer node-webhook metadata, webhook-compatible comment events and an API for system-report sections.
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 released 35.0.2, 34.0.5 and 33.0.10 on the same day, a month after the 35.0.0 major that swapped OnlyOffice for Euro-Office and added FrankenPHP support. The backports share a security-flavored core: a CSRF token on the share-accept endpoint, upload checks against session and share tokens, and logs that no longer leak sensitive data. 35.0.2 also adds richer node-webhook metadata, webhook-compatible comment events and an API for system-report sections.
The patch stream is still dominated by sharing permissions, resharer caps and encryption cache fixes, now applied across three supported branches at once. The small additions in 35.0.2, webhooks and the 'Unified Sharing Legacy Sync' groundwork, point to sharing being rebuilt under the hood and to more automation hooks for integrators. The 35 line is absorbing regressions from the major at a steady monthly pace.
Expect a 35.0.3 within a month continuing sharing and encryption fixes, with more of the unified-sharing work surfacing; the entries do not say when that rework becomes user-visible.
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.
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
SiYuan 3.8.9 reaches RC, adding AI-agent extraction of images embedded in PDFs.
KACE extends its PHP2SHELL fix to the SDA deployment appliance, six days after disclosure.
Mattermost v12 puts user-scoped permissions, private models and audit trails on every agent action.
AFFiNE's canaries stay on upkeep: a Swift Collections bump follows CVE and migration fixes.
Teable's Structured Query v2 now reports across multi-hop relations, with a strict mode against SQL.
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. Nextcloud is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. Nextcloud is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 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.