SOGo
SOGo's release notes have become a vulnerability disclosure channel with a version number attached.
A side-by-side editorial comparison of Komga and Mattermost — release velocity, themes, recent moves, and the top alternatives to consider.
Komga is rewriting its web UI in the open, shipping the beta alongside the old one.
Komga's release cadence is dominated by NextUI, a ground-up rewrite of the web interface that landed in beta with 1.26.0 and is served next to the existing UI at /next rather than replacing it. The three patch releases that followed within 48 hours were almost entirely NextUI shakedown work — scroll restoration, selection behavior, stylesheets failing to load under Tomcat. Underneath the interface work the server keeps widening format support, with rar5 handling in plain Java and solid rar4 archives earlier in the summer.
Access control keeps getting finer-grained for defense buyers, buried in a blog that mostly publishes essays.
Most of this feed is editorial aimed at defense, government, and critical-infrastructure audiences — air-gapped networking, Zero Trust gaps in collaboration tooling, sensitive-data translation, mobile data protection. The actual product news arrives as periodic version digests. The most recent, v11.9, adds channel-level ABAC policies, ranked attributes, and program masking, plus native Azure Blob Storage so files stay in the infrastructure a team already runs.
Komga's release cadence is dominated by NextUI, a ground-up rewrite of the web interface that landed in beta with 1.26.0 and is served next to the existing UI at /next rather than replacing it. The three patch releases that followed within 48 hours were almost entirely NextUI shakedown work — scroll restoration, selection behavior, stylesheets failing to load under Tomcat. Underneath the interface work the server keeps widening format support, with rar5 handling in plain Java and solid rar4 archives earlier in the summer.
The project is running a long, deliberately cautious frontend migration: both UIs ship in the same binary, the feature gap is tracked publicly in an issue, and users opt in by URL. That arrangement should persist across several minor versions before the old WebUI is retired. The parallel v2 referential API suggests the rewrite is also being used to revise the server contract rather than only restyle the client.
Near-term releases should keep closing the NextUI feature gap issue by issue, with patch releases landing within days of each other. The old WebUI is unlikely to be removed before NextUI reaches parity and browser refresh stops falling back to it.
Most of this feed is editorial aimed at defense, government, and critical-infrastructure audiences — air-gapped networking, Zero Trust gaps in collaboration tooling, sensitive-data translation, mobile data protection. The actual product news arrives as periodic version digests. The most recent, v11.9, adds channel-level ABAC policies, ranked attributes, and program masking, plus native Azure Blob Storage so files stay in the infrastructure a team already runs.
The product is pushing authorization granularity steadily downward — from server and team scope toward per-channel policy, with attribute ranking and masking to express which parts of a program a given user may see. That is a direct answer to the sovereignty argument the blog keeps making: perimeter and identity controls stop short of where the work happens. Storage is following the same logic, meeting customers inside their existing cloud tenancy rather than asking them to relocate data.
Expect the ABAC surface to keep extending into finer objects and administrative delegation, and further deployment-native storage and infrastructure integrations. The editorial run on agentic AI in mission-critical operations suggests agent governance is being positioned before it is shipped, though the release notes here do not yet show it.
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 Komga or Mattermost.
SOGo's release notes have become a vulnerability disclosure channel with a version number attached.
Steady weekly shipping, with Jira write-back the one release that changes what Hive is.
GitHub is standardising the agent layer it doesn't own, while the model roster churns underneath.
Staffbase's public feed is employer branding, not product — the release signal isn't here.
A nightly canary train where the AI platform work hides between dependency bumps
pagedown is down to one small fix a year, mostly absorbing changes from elsewhere.
See all Komga alternatives → · See all Mattermost alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Collab. Komga is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. Komga is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Komga alternatives in Collab are ranked by recent ship velocity. Browse the "Komga alternatives" section above for the current picks, or visit /alternatives/komga for the full list with editorial commentary on each.
Top Mattermost alternatives in Collab are ranked by recent ship velocity. Browse the "Mattermost alternatives" section above for the current picks, or visit /alternatives/mattermost for the full list with editorial commentary on each.