Hive
Governance and cross-workspace plumbing, not new AI surface
A side-by-side editorial comparison of Kagi Search and Komga — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Kagi Search | Komga |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | search-api, assistant, mobile-apps, user-control | frontend-rewrite, beta, self-hosted, ebook-formats |
| Last editorial update | 6d ago | 1d ago |
| Website | — | Visit → |
Kagi is unbundling itself: search as an API, Assistant as an app, AI as a switch.
The dated part of this feed stops in April on housekeeping releases — reliability work, refinements, a Small Web expansion. Everything since sits in undated rows and is more substantial: the Search API went to public preview in May carrying each account's own lenses and blocklists, June started rebuilding search widgets, July added a global off-switch for AI in search, and July 30 put Kagi Assistant on iOS and Android as a standalone app.
After two years of quiet fixes, Komga puts a whole new web UI in front of users.
Komga's recent history is almost entirely maintenance — archive-format edge cases, EPUB table-of-contents parsing, Kobo and OPDS compatibility, and a long tail of dependency bumps and translations. Release 1.26.0 breaks that pattern by shipping NextUI, a rewritten web interface, in beta and served alongside the existing one from the same server. The old UI remains the default, and the new one is reached from a sidebar link or a /next path, with a published list of what is still missing.
The dated part of this feed stops in April on housekeeping releases — reliability work, refinements, a Small Web expansion. Everything since sits in undated rows and is more substantial: the Search API went to public preview in May carrying each account's own lenses and blocklists, June started rebuilding search widgets, July added a global off-switch for AI in search, and July 30 put Kagi Assistant on iOS and Android as a standalone app.
Kagi is separating what used to be one subscription into distinct products with distinct surfaces: a search index other people can query, an assistant that lives on a phone, and a search page where the AI layer is optional. The through-line is user control — preferences that follow the API key, widgets that can be switched off individually, threads that can be exported or deleted in bulk — which is the one thing an ad-funded competitor cannot match on. Growth now depends on those surfaces rather than on convincing people to change their default search engine.
The Search API is the piece with launch details still outstanding, so expect it to leave preview with firm pricing and the beta users migrated; the mobile Assistant is described as a first step, which points to the missing platform features arriving next.
Komga's recent history is almost entirely maintenance — archive-format edge cases, EPUB table-of-contents parsing, Kobo and OPDS compatibility, and a long tail of dependency bumps and translations. Release 1.26.0 breaks that pattern by shipping NextUI, a rewritten web interface, in beta and served alongside the existing one from the same server. The old UI remains the default, and the new one is reached from a sidebar link or a /next path, with a published list of what is still missing.
This is a staged frontend replacement rather than a cutover: two UIs on one web server, a v2 referential API landing in the same release to back the new client, and a hotfix a few hours later for NextUI CSS layers under Tomcat. The backend is simplifying in parallel — RAR5 support moved to plain Java and libarchive was dropped from the Docker image and the tray app, removing a native dependency from the build. Feature work outside the UI stays narrow and format-focused.
Expect a run of point releases closing the gaps in NextUI's feature list and hardening the two-UI serving path, with the beta label staying on until parity is reached. A default switch is unlikely before the missing features land.
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 Kagi Search or Komga.
Governance and cross-workspace plumbing, not new AI surface
A nightly canary train where the AI platform work hides between dependency bumps
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
A self-hosted RSS reader that now spends most of its release notes on security.
SiYuan's v3.8.0 train restates one AI feature set across seven consecutive builds.
Jellyfin renumbers to 12.0 and spends the whole cycle paying down its backend rewrite.
See all Kagi Search alternatives → · See all Komga alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Komga 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. Komga 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 Kagi Search alternatives in Collab are ranked by recent ship velocity. Browse the "Kagi Search alternatives" section above for the current picks, or visit /alternatives/kagi for the full list with editorial commentary on each.
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.