Simpplr
Simpplr's feed is research-backed internal-comms commentary, with no product releases in it.
A side-by-side editorial comparison of HumHub and LibrePhotos — release velocity, themes, recent moves, and the top alternatives to consider.
HumHub's public feed carries only betas, and 1.19's is mostly about surviving the upgrade.
The three releases visible here are all pre-release: 1.19.0-beta.1 in July, and 1.18.0-beta.6 and beta.5 before it. The 1.19 beta is dominated by upgrade-path and data-integrity repair — a foreign key violation that aborted the 1.19 comment content_id migration on databases with orphaned rows, a fatal error when deleting a user or running PurgeDeletedContents against content whose underlying record was gone, and a permissions fix where users with ManageSettings but not ManageModules were offered a Configure button on disabled modules. The 1.18 betas are ordinary polish: login screen layout, theme inheritance, validators, translations and installer fixes.
LibrePhotos folded five repositories into one and started versioning like a real product.
The project spent April through June on structural work rather than features. Backend, frontend, mobile app, docs, and Docker deployment were merged into a single repository with each project's git history preserved, and the versioning scheme moved to semver, producing the first 1.0.x releases. The releases since are consolidation: authorization hardening on the user API, a fix for the validation popups that hardening caused for non-admin users, and repeated pinning fights to keep the GPU image building.
The three releases visible here are all pre-release: 1.19.0-beta.1 in July, and 1.18.0-beta.6 and beta.5 before it. The 1.19 beta is dominated by upgrade-path and data-integrity repair — a foreign key violation that aborted the 1.19 comment content_id migration on databases with orphaned rows, a fatal error when deleting a user or running PurgeDeletedContents against content whose underlying record was gone, and a permissions fix where users with ManageSettings but not ManageModules were offered a Configure button on disabled modules. The 1.18 betas are ordinary polish: login screen layout, theme inheritance, validators, translations and installer fixes.
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 change meets databases that have accumulated orphaned rows over years. The permission fix points the same way: tightening the boundary between managing settings and managing modules is cleanup of an authorisation 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. Note that the gap between the 1.18 betas and the 1.19 beta is roughly six months, which is the only cadence signal available.
The project spent April through June on structural work rather than features. Backend, frontend, mobile app, docs, and Docker deployment were merged into a single repository with each project's git history preserved, and the versioning scheme moved to semver, producing the first 1.0.x releases. The releases since are consolidation: authorization hardening on the user API, a fix for the validation popups that hardening caused for non-admin users, and repeated pinning fights to keep the GPU image building.
This is a self-hosted project doing the unglamorous work that makes contribution and release possible at scale — one repo, unified CI and Dockerfiles, predictable version numbers. The backend changes running underneath it are about resilience rather than capability: retrying transient face-service drops, hardening metadata extraction against exif-service failures, preserving scan baselines during job cleanup. The recurring Renovate-versus-GPU-pin conflicts suggest the dependency story for the CUDA image is still fragile.
With the monorepo and semver in place, the next releases are likely to return to user-facing features on a 1.x line rather than more restructuring. The GPU image pins look like they will need a more durable fix than repeated Renovate overrides.
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 LibrePhotos.
Simpplr's feed is research-backed internal-comms commentary, with no product releases in it.
A self-hosted ebook library growing one reader feature and one format at a time.
A social-networking engine in careful maintenance across two supported branches.
NetNewsWire's release notes have become a log of other people's rate limits.
Asana is bolting an agent layer and a docs surface onto work management.
AFFiNE let workspaces bring their own model keys, then went back to dependency bumps.
See all HumHub alternatives → · See all LibrePhotos 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 2.5 vs 0.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. HumHub is currently shipping more aggressively (velocity 2.5 vs 0.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 LibrePhotos alternatives in Collab are ranked by recent ship velocity. Browse the "LibrePhotos alternatives" section above for the current picks, or visit /alternatives/librephotos for the full list with editorial commentary on each.