Flame
Self-hosted dashboard that finished its feature arc and stopped shipping in 2023.
A side-by-side editorial comparison of Komga and NetNewsWire — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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 Komga 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 Komga 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. Komga 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. Komga 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 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.
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.