Ethico
The whistleblower hotline vendor is assembling a compliance suite, one module at a time.
A side-by-side editorial comparison of Kavita and Rocket.Chat — release velocity, themes, recent moves, and the top alternatives to consider.
A self-hosted reading server that spent two releases becoming infrastructure, then paid for it with a CVE.
Kavita ships two to four substantial releases a year with hotfixes trailing each one, and the last two years moved it well past a comic reader: OIDC login, an annotation system, a rebuilt epub reader, a reading-list overhaul, a stats system, and a scanner reported 50x faster. The most recent release is a critical security hotfix carrying CVE-2026-47202 that affects every prior version. Kavita+ remains the paid tier where metadata features land first.
A long RC train of dependency bumps, with the real work landing in the 8.7 branch opener.
Rocket.Chat publishes every release candidate, and the shape is consistent: the .rc.0 that opens a minor carries the substance, and every RC after it is a Meteor version bump with the occasional fix. The 8.7 line opened with server-side OAuth, PKCE and state validation under a phishing-resistant MFA banner, plus session identification in device management. The four RCs since have added one user-visible fix — seekable audio attachments.
Kavita ships two to four substantial releases a year with hotfixes trailing each one, and the last two years moved it well past a comic reader: OIDC login, an annotation system, a rebuilt epub reader, a reading-list overhaul, a stats system, and a scanner reported 50x faster. The most recent release is a critical security hotfix carrying CVE-2026-47202 that affects every prior version. Kavita+ remains the paid tier where metadata features land first.
The arc is a hobby-scale project taking on the obligations of infrastructure — standard auth, an external API contract for third-party clients, sync with other readers, and formal vulnerability disclosure. Each of those decisions expands the attack surface, and the 0.9.x line shows the bill arriving: security hardening now leads the release notes rather than following them. The team has also visibly grown from one maintainer to a named pair, which is what made the parallel reader and foundation rewrites possible.
The next release is likely the delayed scanner-improvement work that 0.8.7 displaced, with continued API hardening rather than new reader surfaces. Expect the CVE details to be published once adoption of 0.9.0.2 is high enough.
Rocket.Chat publishes every release candidate, and the shape is consistent: the .rc.0 that opens a minor carries the substance, and every RC after it is a Meteor version bump with the occasional fix. The 8.7 line opened with server-side OAuth, PKCE and state validation under a phishing-resistant MFA banner, plus session identification in device management. The four RCs since have added one user-visible fix — seekable audio attachments.
The feature direction is enterprise and regulated deployment: phishing-resistant authentication in 8.7, attribute-based access control with an external Virtru attribute store in 8.6, federation and personal-access-token correctness fixes throughout. These are the requirements of buyers who run Rocket.Chat themselves because they cannot use a hosted competitor, and the release notes read like a queue of their procurement checklists.
Expect 8.7 to reach general availability with the OAuth rework as its headline and little added beyond it, since the RC train has been quiet since rc.0. The unified presence engine whose backend landed in 8.6 has no user-facing surface yet, making it the likeliest candidate for the next minor.
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 Kavita or Rocket.Chat.
The whistleblower hotline vendor is assembling a compliance suite, one module at a time.
Contract automation grows up: admin permission maps, 2FA, and forms that do their own arithmetic.
The knowledge graph quietly turned itself into a meetings product.
A minimal RSS reader that made passkeys the only way in, then went back to polishing the reading experience.
A Go bookmark manager rebuilding itself around an API — and only ever shipping release candidates.
FreshRSS keeps turning a reader into a queryable archive — and hardening the parts that touch the web.
See all Kavita alternatives → · See all Rocket.Chat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Collab. Rocket.Chat is currently shipping more aggressively (velocity 6.3 vs 0.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. Rocket.Chat is currently shipping more aggressively (velocity 6.3 vs 0.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 Kavita alternatives in Collab are ranked by recent ship velocity. Browse the "Kavita alternatives" section above for the current picks, or visit /alternatives/kavita for the full list with editorial commentary on each.
Top Rocket.Chat alternatives in Collab are ranked by recent ship velocity. Browse the "Rocket.Chat alternatives" section above for the current picks, or visit /alternatives/rocket-chat for the full list with editorial commentary on each.