SiYuan
SiYuan stabilises 3.8.1 after a seven-build beta run, all of it widening the agent surface it opened in 3.8.0
A side-by-side editorial comparison of CommaFeed and Kagi Search — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | CommaFeed | Kagi Search |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 5.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | rss-reader, self-hosted, security-hardening, ssrf | search-api, assistant, mobile-apps, user-control |
| Last editorial update | 1h ago | 13d ago |
| Website | Visit → | — |
CommaFeed is patching its way through the attack surface a self-hosted reader inherits
CommaFeed's 7.x line has become a sustained security pass. The newest patch closes Host header injection on the password recovery endpoint and adds a commafeed.password-recovery-public-base-url setting so the email base URL is configured rather than taken from the request. Behind it: local address blocking made secure by default alongside Google Reader API support in 7.3.0, javascript: URLs filtered at parse time in 7.2.1, and SSRF limits on the image proxy in 7.2.0.
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.
CommaFeed's 7.x line has become a sustained security pass. The newest patch closes Host header injection on the password recovery endpoint and adds a commafeed.password-recovery-public-base-url setting so the email base URL is configured rather than taken from the request. Behind it: local address blocking made secure by default alongside Google Reader API support in 7.3.0, javascript: URLs filtered at parse time in 7.2.1, and SSRF limits on the image proxy in 7.2.0.
Every release in this stretch closes a path where content or a request from outside the instance was trusted too far - feed URLs reaching internal addresses, proxied images, javascript: links, and now a header shaping an outbound email. That is the checklist of a project being run as a multi-user hosted service rather than a single-user tool, and it follows directly from the 7.0.0 decision to sandbox filter expressions. Feature work continues in parallel but is clearly the smaller half.
The remaining untrusted-input surfaces - OPML import and the feed fetcher's redirect handling - are the likely next targets. The pattern of shipping each fix as its own patch release should continue rather than batching them.
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.
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 CommaFeed or Kagi Search.
SiYuan stabilises 3.8.1 after a seven-build beta run, all of it widening the agent surface it opened in 3.8.0
Hive ships in batches, and this one is all planning accuracy and admin control.
Teable ships daily, and the work has moved from grid features to platform governance.
Simpplr publishes the research that names the gap, then ships the product that closes it.
NetNewsWire's 7.1.3 train has moved from rebuilding sync to sweeping up what the rebuild disturbed.
Document360 rebuilt its API for agents; now it's turning the AI inward on authoring.
See all CommaFeed alternatives → · See all Kagi Search alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CommaFeed is currently shipping more aggressively (velocity 5.0 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. CommaFeed is currently shipping more aggressively (velocity 5.0 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 CommaFeed alternatives in Collab are ranked by recent ship velocity. Browse the "CommaFeed alternatives" section above for the current picks, or visit /alternatives/commafeed for the full list with editorial commentary on each.
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.