CommaFeed
CommaFeed is patching its way through the attack surface a self-hosted reader inherits
A side-by-side editorial comparison of Document360 and Paperless-ngx — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Document360 | Paperless-ngx |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | api, oauth, mcp, knowledge base | document-management, self-hosted, paperless-ai, breaking-changes |
| Last editorial update | 1d ago | 17d ago |
| Website | — | Visit → |
Document360 rebuilt its API for agents; now it's turning the AI inward on authoring.
Monthly point releases on a steady 12.x line, each a themed bundle rather than a fix list. The last three releases rebuilt the developer-facing surface: an interactive API reference with an in-page Try It! console, a ground-up API v3 with OAuth 2.0 and scoped keys, and a Widget 2.0 embedding architecture now rolling out with a migration deadline. Around that, Eddy AI and the MCP server have been gaining governance controls — reader-group restrictions, workflow permissions, usage analytics — more often than new capabilities.
Paperless-ngx shipped its 3.0 rewrite, then spent a week putting out the fires.
3.0.0 landed on July 22 after a long beta, carrying both the largest feature set in the project's history and nine breaking changes. The five releases since are pure repair: a broken migration in 3.0.1 that forced an immediate 3.0.2, then three patch rounds covering OCR skipping, permission-filtered dedup, Gotenberg conversion, email date parsing, AI suggestion caching and search index edge cases. The pace tells you 3.0 shipped into real deployments fast.
Monthly point releases on a steady 12.x line, each a themed bundle rather than a fix list. The last three releases rebuilt the developer-facing surface: an interactive API reference with an in-page Try It! console, a ground-up API v3 with OAuth 2.0 and scoped keys, and a Widget 2.0 embedding architecture now rolling out with a migration deadline. Around that, Eddy AI and the MCP server have been gaining governance controls — reader-group restrictions, workflow permissions, usage analytics — more often than new capabilities.
Two threads run through the year. One makes the knowledge base machine-readable and machine-writable: MCP server, automatic llms.txt, open-an-article-in-ChatGPT-or-Claude, then API v3. The other fences that access with admin controls before enterprise buyers have to ask. The newest release turns the AI inward for the first time — the redesigned Publish dialog puts suggestions and validation in the author's path rather than the reader's, which is a different customer for the same capability.
The AI suggestions now sitting in the Publish dialog are the obvious candidate to move into the editor itself, and the advanced v3 endpoints sold as an add-on look like the seed of a higher API tier. The Widget 2.0 forced migration is the near-term execution risk, since it puts required technical work on existing customers to a fixed timeline.
3.0.0 landed on July 22 after a long beta, carrying both the largest feature set in the project's history and nine breaking changes. The five releases since are pure repair: a broken migration in 3.0.1 that forced an immediate 3.0.2, then three patch rounds covering OCR skipping, permission-filtered dedup, Gotenberg conversion, email date parsing, AI suggestion caching and search index edge cases. The pace tells you 3.0 shipped into real deployments fast.
The project has moved from a document scanner-and-tagger to a document platform with AI in the core: Paperless AI, remote OCR via Azure, a document parser plugin framework, tantivy replacing Whoosh for search, file versions and sharelink bundles. The breaking changes are the other half of that story — dropping API v1, Python 3.10, document encryption and the old consumer clears the decks for that platform. Recent patches keep touching LLM plumbing, including passing output language into chat and adding docstrings so the classifier reads better as an LLM tool.
The 3.0.x patch cadence looks set to run at least another round or two — 3.0.5 is still landing search-compatibility and AI-suggestion fixes rather than tapering. Feature work resuming before that queue empties would be the surprise.
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 Document360 or Paperless-ngx.
CommaFeed is patching its way through the attack surface a self-hosted reader inherits
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.
See all Document360 alternatives → · See all Paperless-ngx alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Document360 and Paperless-ngx are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. Document360 and Paperless-ngx are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
Top Document360 alternatives in Collab are ranked by recent ship velocity. Browse the "Document360 alternatives" section above for the current picks, or visit /alternatives/document360 for the full list with editorial commentary on each.
Top Paperless-ngx alternatives in Collab are ranked by recent ship velocity. Browse the "Paperless-ngx alternatives" section above for the current picks, or visit /alternatives/paperless-ngx for the full list with editorial commentary on each.