AFFiNE
AFFiNE just cut its AI loose from a fixed provider — bring your own keys, your own models, per workspace.
A side-by-side editorial comparison of Kagi Search and Read the Docs — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Kagi Search | Read the Docs |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 0.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | search-api, assistant, mobile-apps, user-control | documentation-hosting, build-infrastructure, ephemeral-builders, uv |
| Last editorial update | 2h ago | 5h ago |
| Website | — | Visit → |
Kagi is unbundling itself: search as an API, Assistant as an app, AI as a switch.
The dated part of this feed stops in April on housekeeping releases — reliability work, refinements, a Small Web expansion. Everything since sits in undated rows and is more substantial: the Search API went to public preview in May carrying each account's own lenses and blocklists, June started rebuilding search widgets, July added a global off-switch for AI in search, and July 30 put Kagi Assistant on iOS and Android as a standalone app.
Read the Docs deploys weekly, and almost all of it is rebuilding how builds run.
Read the Docs cuts a dated release every week, most of them thin — a dependency sweep, a docs correction, a CI bump. The substance in this window is concentrated in the build platform: ephemeral builders moving from experiment to implementation, uv installed and configured for generic builders, private-repo permissions plumbed through to the isolated builder, and a hardened tar extraction filter when unpacking doctools.
The dated part of this feed stops in April on housekeeping releases — reliability work, refinements, a Small Web expansion. Everything since sits in undated rows and is more substantial: the Search API went to public preview in May carrying each account's own lenses and blocklists, June started rebuilding search widgets, July added a global off-switch for AI in search, and July 30 put Kagi Assistant on iOS and Android as a standalone app.
Kagi is separating what used to be one subscription into distinct products with distinct surfaces: a search index other people can query, an assistant that lives on a phone, and a search page where the AI layer is optional. The through-line is user control — preferences that follow the API key, widgets that can be switched off individually, threads that can be exported or deleted in bulk — which is the one thing an ad-funded competitor cannot match on. Growth now depends on those surfaces rather than on convincing people to change their default search engine.
The Search API is the piece with launch details still outstanding, so expect it to leave preview with firm pricing and the beta users migrated; the mobile Assistant is described as a first step, which points to the missing platform features arriving next.
Read the Docs cuts a dated release every week, most of them thin — a dependency sweep, a docs correction, a CI bump. The substance in this window is concentrated in the build platform: ephemeral builders moving from experiment to implementation, uv installed and configured for generic builders, private-repo permissions plumbed through to the isolated builder, and a hardened tar extraction filter when unpacking doctools.
The through-line is the build layer being re-founded on isolation and speed. Ephemeral builders, an isolated builder that receives permissions explicitly rather than inheriting them, and uv replacing the older Python environment path all point at builds that start faster and share less. Around that, the product-facing changes are small and mostly clarifying: renaming External versions to Pull request in the interface, distinct commit statuses for skipped builds, a dropdown instead of free text when filtering redirects.
Ephemeral builders moved from a test to real wiring across these releases, so the next step is most likely rolling that path out more widely and continuing the uv migration, rather than user-facing feature work.
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 Kagi Search or Read the Docs.
AFFiNE just cut its AI loose from a fixed provider — bring your own keys, your own models, per workspace.
Asana's AI Teammates stopped answering questions and started writing the automation themselves.
Zoho Projects makes time tracking the product's center of gravity, and lets Zia build the schema.
SiYuan's 3.8 alpha turns the note vault into an agent surface: embeddings, reranking, MCP.
Discord is turning the chat client into a storefront and Nitro into a rewards program.
monday.com is building the control room for AI it already sold customers on.
See all Kagi Search alternatives → · See all Read the Docs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Read the Docs is currently shipping more aggressively (velocity 5.0 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. Read the Docs is currently shipping more aggressively (velocity 5.0 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 Kagi Search alternatives in Collab are ranked by recent ship velocity. Browse the "Kagi Search alternatives" section above for the current picks, or visit /alternatives/kagi for the full list with editorial commentary on each.
Top Read the Docs alternatives in Collab are ranked by recent ship velocity. Browse the "Read the Docs alternatives" section above for the current picks, or visit /alternatives/read-the-docs for the full list with editorial commentary on each.