Flame
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
A side-by-side editorial comparison of Document360 and NetNewsWire — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Document360 | NetNewsWire |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | api, oauth, mcp, knowledge base | rss, feedly-sync, rate-limiting, bug-fixes |
| Last editorial update | 22h ago | 14h ago |
| Website | — | Visit → |
Document360 rebuilds its public API and turns docs into an agent-readable surface.
Document360 ships a dated release every two to four weeks and the last six months have been dominated by two threads: making the knowledge base machine-consumable, and hardening enterprise access control. The AI thread runs from the March MCP server through publishing and workflow tools in June and per-reader-group AI restrictions this month; the access thread runs SCIM provisioning, multiple JWT configurations, and reader permission inheritance. This release adds a ground-up API v3 with OAuth 2.0 and scoped keys.
NetNewsWire rebuilt Feedly sync to stop getting its own users rate-limited.
The centerpiece of this window is a Feedly sync overhaul, shipped in parallel to iOS and Mac: syncing now backs off when Feedly reports rate limiting, fetches only what changed, caps downloads per refresh, and directly refreshes a few feeds each pass to backfill articles Feedly's aggregate stream omits. The mark-as-read backlog that could grow without bound and re-send the same statuses was fixed, and articles now use Feedly's reported publish dates instead of arriving all stamped today. Around it sits a dense stream of small point builds on both platforms, including a move to the current Sparkle framework and a filter-button style that was introduced and reverted within two days.
Document360 ships a dated release every two to four weeks and the last six months have been dominated by two threads: making the knowledge base machine-consumable, and hardening enterprise access control. The AI thread runs from the March MCP server through publishing and workflow tools in June and per-reader-group AI restrictions this month; the access thread runs SCIM provisioning, multiple JWT configurations, and reader permission inheritance. This release adds a ground-up API v3 with OAuth 2.0 and scoped keys.
The product is being rebuilt around programmatic access rather than portal usage. MCP made the knowledge base writable by an assistant, llms.txt made it discoverable to crawlers, copy-as-Markdown and open-in-ChatGPT made articles portable, and API v3 now gives all of that a permission-aware substrate the old v1/v2 endpoints could not support. The same permission model is showing up on the reader side too — Eddy AI features are now gated per reader group — so authorization is becoming the shared spine across API, AI, and reader access.
Expect the advanced API v3 endpoints to keep expanding as a paid add-on and the MCP server to be re-plumbed onto v3's scoped-key model, since MCP currently sits outside the new authorization scheme. A v1/v2 deprecation notice is the other likely follow-up.
The centerpiece of this window is a Feedly sync overhaul, shipped in parallel to iOS and Mac: syncing now backs off when Feedly reports rate limiting, fetches only what changed, caps downloads per refresh, and directly refreshes a few feeds each pass to backfill articles Feedly's aggregate stream omits. The mark-as-read backlog that could grow without bound and re-send the same statuses was fixed, and articles now use Feedly's reported publish dates instead of arriving all stamped today. Around it sits a dense stream of small point builds on both platforms, including a move to the current Sparkle framework and a filter-button style that was introduced and reverted within two days.
This is a maintenance-phase release train, and the work is concentrated where the app depends on someone else's service. Making sync well-behaved enough not to trigger bans is infrastructure debt being paid down rather than new capability, and the same is true of the Sparkle switch, which pre-empts breakage on macOS 27 betas. The parallel iOS and Mac numbering means most substantive changes land twice, so the feed reads busier than the change set actually is.
Expect 7.1.3 to converge to a shipping release on both platforms with no new capability, given the last several builds are fixes and one reverted style change. Further hardening of third-party account syncing is the most likely next area, since Feedly consumed this cycle.
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 NetNewsWire.
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.
Teable is spending its release budget making bring-your-own-database failures survivable.
Happeo's feed is a buyer-education funnel, not a changelog — no shipped work is visible.
See all Document360 alternatives → · See all NetNewsWire alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Document360 is currently shipping more aggressively (velocity 6.3 vs 5.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. Document360 is currently shipping more aggressively (velocity 6.3 vs 5.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 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 NetNewsWire alternatives in Collab are ranked by recent ship velocity. Browse the "NetNewsWire alternatives" section above for the current picks, or visit /alternatives/netnewswire for the full list with editorial commentary on each.