Readarr
Six releases of small fixes and translations, then nothing since June 2025.
A side-by-side editorial comparison of AFFiNE and Outline — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | AFFiNE | Outline |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 7.5 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | byok, copilot, self-hosting, dual-train | knowledge-base, mcp, agent-write-access, document-permissions |
| Last editorial update | 21h ago | 1h ago |
| Website | Visit → | — |
AFFiNE just cut its AI loose from a fixed provider — bring your own keys, your own models, per workspace.
AFFiNE publishes from two trains simultaneously — dated canary builds and 0.27.x betas — so the same pull request often appears twice with different version numbers. Most of the recent output is dependency automation: setup-python, actions/cache, RevenueCat SPM bumps. The substantive work sits on the server: blob sync with presigned URLs for S3 and R2, document garbage collection reliability, and now a rebuild of how Copilot gets its models.
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.
AFFiNE publishes from two trains simultaneously — dated canary builds and 0.27.x betas — so the same pull request often appears twice with different version numbers. Most of the recent output is dependency automation: setup-python, actions/cache, RevenueCat SPM bumps. The substantive work sits on the server: blob sync with presigned URLs for S3 and R2, document garbage collection reliability, and now a rebuild of how Copilot gets its models.
The server is where AFFiNE is investing, and the shape of that investment is self-hosting. Presigned upload URLs configurable per storage provider, doc GC hardening, and now workspace-level model profiles all point at the same customer: someone running AFFiNE on their own infrastructure who wants the AI features without routing content through AFFiNE's vendor of choice. Removing the legacy provider-specific settings in the same change says this is a replacement, not an option.
With provider catalogs and managed tiers now in the model, the next moves are likely on the governance side — surfacing which models a workspace permits and what they cost — since the change also stripped token-cost and provider metadata out of public responses.
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 AFFiNE or Outline.
Six releases of small fixes and translations, then nothing since June 2025.
Five repos became one, and the authorization model got a public-safe user view.
A mature media server whose releases are format edge cases and Kobo plumbing.
A steady indexer-maintenance cadence: fixes, definitions, translations, repeat.
noVNC ships about once a year, and its betas and finals carry identical notes.
Lidarr's release notes still tell you not to update Radarr — the fork's seams are showing.
See all AFFiNE alternatives → · See all Outline alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — knowledge-base — within Collab. AFFiNE is currently shipping more aggressively (velocity 7.5 vs 2.5), 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. AFFiNE is currently shipping more aggressively (velocity 7.5 vs 2.5), 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 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.
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.