Hive
Governance and cross-workspace plumbing, not new AI surface
A side-by-side editorial comparison of CommaFeed and Outline — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | CommaFeed | Outline |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 5.0 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | rss-reader, self-hosting, security-hardening, api-interop | knowledge-base, mcp, agent-write-access, document-permissions |
| Last editorial update | 11h ago | 5d ago |
| Website | Visit → | — |
A self-hosted RSS reader that now spends most of its release notes on security.
CommaFeed is a self-hosted Google Reader replacement that has spent the 6.x-to-7.x stretch rebuilding its trust boundaries rather than its feature list. SSRF protection has been tightened in four consecutive releases, feed parsing now strips javascript: URLs before they reach the database, and OPML imports are filtered against import-time abuse. The 7.x line pairs that with client interop: Fever API, ReadKit compatibility, and now the Google Reader API.
Outline gave AI assistants write access to the wiki, then spent months on the human side.
The April MCP expansion is the structural change in this window: assistants can patch documents, move and delete documents and collections, work with attachments, and create and resolve inline comments. Everything since has been human-facing and smaller — request-access flows for documents members cannot open, email subscriptions to publicly shared documents with change summaries, task list and checkbox handling in the editor, and profile cards on avatar hover.
CommaFeed is a self-hosted Google Reader replacement that has spent the 6.x-to-7.x stretch rebuilding its trust boundaries rather than its feature list. SSRF protection has been tightened in four consecutive releases, feed parsing now strips javascript: URLs before they reach the database, and OPML imports are filtered against import-time abuse. The 7.x line pairs that with client interop: Fever API, ReadKit compatibility, and now the Google Reader API.
The project is positioning itself as a sync backend other people's apps talk to, not just a web reader. Each release adds another protocol or client fix while hardening the assumption that an instance may be publicly exposed with untrusted users on it. The 7.0.0 swap from JEXL to sandboxed CEL and the 7.3.0 flip of blockLocalAddresses to a secure default both trade self-hoster convenience for a safer out-of-the-box posture.
Expect continued client-protocol coverage and further SSRF narrowing; the recurring pattern in these entries is that every new fetch path gets a follow-up hardening release.
The April MCP expansion is the structural change in this window: assistants can patch documents, move and delete documents and collections, work with attachments, and create and resolve inline comments. Everything since has been human-facing and smaller — request-access flows for documents members cannot open, email subscriptions to publicly shared documents with change summaries, task list and checkbox handling in the editor, and profile cards on avatar hover.
Two audiences are being served in sequence. The MCP work moved assistants from reading the knowledge base to editing it, including the collection structure itself. The releases after it close ordinary gaps in how people find, follow and get into documents — which is what a wiki needs before more of its edits arrive from automation. Release cadence is roughly monthly with entries that describe outcomes rather than changelogs.
Expect the human-facing polish to continue at its current pace, with any next structural move likely extending the MCP surface further into permissions and collection management, since that is where the existing tools stop.
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 Outline.
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.
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.
Teable is spending its release budget making bring-your-own-database failures survivable.
See all CommaFeed alternatives → · See all Outline 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 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. CommaFeed 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 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 Outline alternatives in Collab are ranked by recent ship velocity. Browse the "Outline alternatives" section above for the current picks, or visit /alternatives/outline for the full list with editorial commentary on each.