Simpplr
Simpplr's feed is research-backed internal-comms commentary, with no product releases in it.
A side-by-side editorial comparison of Passbolt and HumHub — release velocity, themes, recent moves, and the top alternatives to consider.
Passbolt made shared-resource permissions explicit, then spent a release calming the prompt.
The 5.14 line dominates the window. 5.14.0 introduced explicit confirmation dialogs before creating items in shared folders or editing shared resources, and fixed a security issue in MFA policy enforcement. 5.14.3 then narrowed that dialog, which had been firing on metadata-only edits such as renaming, and now appears only when a secret actually changes. Behind those, 5.13 added in-app switching between Community and Pro editions, and 5.12 took the Safari extension out of beta and added a PIN code resource type.
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.
The 5.14 line dominates the window. 5.14.0 introduced explicit confirmation dialogs before creating items in shared folders or editing shared resources, and fixed a security issue in MFA policy enforcement. 5.14.3 then narrowed that dialog, which had been firing on metadata-only edits such as renaming, and now appears only when a secret actually changes. Behind those, 5.13 added in-app switching between Community and Pro editions, and 5.12 took the Safari extension out of beta and added a PIN code resource type.
The recent arc is about making shared state legible before it changes, then tuning that intervention so it does not fire on edits that carry no risk — a confirmation prompt is only useful while users still read it. Around that thread the work is reach and packaging: Safari at parity with the other browsers, editions switchable without a manual migration, new resource types added one at a time. This is a product filling in the operational edges of team password management rather than moving into new territory.
The 5.14.3 correction suggests further tuning of which edit paths trigger the confirmation dialog as more cases are reported. Beyond that, the entries point to continued resource-type additions in the manner of the PIN code type.
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.
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 Passbolt or HumHub.
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.
LibrePhotos folded five repositories into one and started versioning like a real product.
Asana is bolting an agent layer and a docs surface onto work management.
See all Passbolt 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. Passbolt 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. Passbolt 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 Passbolt alternatives in Collab are ranked by recent ship velocity. Browse the "Passbolt alternatives" section above for the current picks, or visit /alternatives/passbolt 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.