Ethico
The whistleblower hotline vendor is assembling a compliance suite, one module at a time.
A side-by-side editorial comparison of FreshRSS and AFFiNE — release velocity, themes, recent moves, and the top alternatives to consider.
FreshRSS keeps turning a reader into a queryable archive — and hardening the parts that touch the web.
Two major releases and their bug-fix follow-ups define this window. 1.28.0 added sorting and filtering by user-modified date with a matching search operator, sorting by article length, an advanced search form, an overview of dates with the most unread articles, and API-level sharing of feed visibility. 1.29.0 layered on sort-order preferences at global, category and feed level, feed-provided icons, and a purge CLI. Security work runs alongside throughout — cURL restricted to HTTP and HTTPS, reauthentication in sudo mode, Content-Security-Policy frame-ancestors, and compliance with HTTP 429 and 503 including Retry-After.
Dependency bumps dominate the canary train; the one real change is blob sync.
AFFiNE publishes two parallel release trains and this window catches both: date-stamped canary builds and a v0.27.x beta tag. Four of the six most recent entries are dependency chores — GitHub Actions bumps for setup-python and cache, and a RevenueCat iOS SPM version raise. The single substantive change is a server-side blob sync improvement that standardizes presigned URL configuration across AWS S3 and Cloudflare R2, and it appears twice because the same pull request lands on both trains.
Two major releases and their bug-fix follow-ups define this window. 1.28.0 added sorting and filtering by user-modified date with a matching search operator, sorting by article length, an advanced search form, an overview of dates with the most unread articles, and API-level sharing of feed visibility. 1.29.0 layered on sort-order preferences at global, category and feed level, feed-provided icons, and a purge CLI. Security work runs alongside throughout — cURL restricted to HTTP and HTTPS, reauthentication in sudo mode, Content-Security-Policy frame-ancestors, and compliance with HTTP 429 and 503 including Retry-After.
The feature line is consistently about retrieval rather than reading: search operators, sort dimensions, date overviews and per-level preferences all treat the archive as a queryable dataset instead of an inbox to clear. In parallel, the CLI surface keeps growing — purge policies, SQLite export with retention — which points at self-hosters automating maintenance rather than clicking through settings. Security fixes are steady and specific to the fact that a feed reader fetches arbitrary remote content, which is what makes the cURL protocol restriction and CSP work necessary rather than optional. Releases pair a feature drop with a fast bug-fix follow-up every time.
Given the pattern of a major release followed within weeks by a patch, and the steady expansion of CLI commands, expect the next major to continue extending search and automation surfaces rather than reworking the reading experience.
AFFiNE publishes two parallel release trains and this window catches both: date-stamped canary builds and a v0.27.x beta tag. Four of the six most recent entries are dependency chores — GitHub Actions bumps for setup-python and cache, and a RevenueCat iOS SPM version raise. The single substantive change is a server-side blob sync improvement that standardizes presigned URL configuration across AWS S3 and Cloudflare R2, and it appears twice because the same pull request lands on both trains.
The engineering attention in this window is on storage plumbing rather than the editor: configurable presigning versus server-mediated proxying, plus tightened upload and multipart validation. That is self-hosting work, giving operators control over how blobs move between the app and their own object storage. Everything else here is automated maintenance, so the canary cadence reflects CI activity more than product movement.
Expect the storage configuration work to continue toward broader self-hosted deployment options, and expect the beta line to absorb the current canary changes as 0.27.4 stabilizes.
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 FreshRSS or AFFiNE.
The whistleblower hotline vendor is assembling a compliance suite, one module at a time.
Contract automation grows up: admin permission maps, 2FA, and forms that do their own arithmetic.
The knowledge graph quietly turned itself into a meetings product.
A minimal RSS reader that made passkeys the only way in, then went back to polishing the reading experience.
A Go bookmark manager rebuilding itself around an API — and only ever shipping release candidates.
A self-hosted reading server that spent two releases becoming infrastructure, then paid for it with a CVE.
See all FreshRSS alternatives → · See all AFFiNE alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Collab. AFFiNE is currently shipping more aggressively (velocity 6.3 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. AFFiNE is currently shipping more aggressively (velocity 6.3 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 FreshRSS alternatives in Collab are ranked by recent ship velocity. Browse the "FreshRSS alternatives" section above for the current picks, or visit /alternatives/freshrss for the full list with editorial commentary on each.
Top AFFiNE alternatives in Collab are ranked by recent ship velocity. Browse the "AFFiNE alternatives" section above for the current picks, or visit /alternatives/affine for the full list with editorial commentary on each.