Zoho Sign
Zoho Sign adds the EU's highest signature tier, one week after wiring itself to agents.
Comparison · Collab
Document360 vs Kagi Search
A side-by-side editorial comparison of Document360 and Kagi Search — release velocity, themes, recent moves, and the top alternatives to consider.
Document360 vs Kagi Search: at a glance
| Feature | Document360 | Kagi Search |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | api, oauth, mcp, knowledge base | search-api, assistant, mobile-apps, user-control |
| Last editorial update | 1d ago | 13d ago |
| Website | — | — |
What is Document360?
Document360 rebuilt its API for agents; now it's turning the AI inward on authoring.
Monthly point releases on a steady 12.x line, each a themed bundle rather than a fix list. The last three releases rebuilt the developer-facing surface: an interactive API reference with an in-page Try It! console, a ground-up API v3 with OAuth 2.0 and scoped keys, and a Widget 2.0 embedding architecture now rolling out with a migration deadline. Around that, Eddy AI and the MCP server have been gaining governance controls — reader-group restrictions, workflow permissions, usage analytics — more often than new capabilities.
What is Kagi Search?
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.
Document360 vs Kagi Search: editorial side-by-side
Document360
6.3COLLAB
Document360 rebuilt its API for agents; now it's turning the AI inward on authoring.
◆ Current state
Monthly point releases on a steady 12.x line, each a themed bundle rather than a fix list. The last three releases rebuilt the developer-facing surface: an interactive API reference with an in-page Try It! console, a ground-up API v3 with OAuth 2.0 and scoped keys, and a Widget 2.0 embedding architecture now rolling out with a migration deadline. Around that, Eddy AI and the MCP server have been gaining governance controls — reader-group restrictions, workflow permissions, usage analytics — more often than new capabilities.
◆ Where it's heading
Two threads run through the year. One makes the knowledge base machine-readable and machine-writable: MCP server, automatic llms.txt, open-an-article-in-ChatGPT-or-Claude, then API v3. The other fences that access with admin controls before enterprise buyers have to ask. The newest release turns the AI inward for the first time — the redesigned Publish dialog puts suggestions and validation in the author's path rather than the reader's, which is a different customer for the same capability.
◆ Prediction
The AI suggestions now sitting in the Publish dialog are the obvious candidate to move into the editor itself, and the advanced v3 endpoints sold as an add-on look like the seed of a higher API tier. The Widget 2.0 forced migration is the near-term execution risk, since it puts required technical work on existing customers to a fixed timeline.
Kagi Search
0.0COLLAB
Kagi is unbundling itself: search as an API, Assistant as an app, AI as a switch.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Document360 and Kagi Search
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 Kagi Search.
Read the Docs
Read the Docs is rebuilding its build farm around uv and isolated builders, one week at a time.
CommaFeed
CommaFeed is patching its way through the attack surface a self-hosted reader inherits
SiYuan
SiYuan stabilises 3.8.1 after a seven-build beta run, all of it widening the agent surface it opened in 3.8.0
Hive
Hive ships in batches, and this one is all planning accuracy and admin control.
Teable
Teable ships daily, and the work has moved from grid features to platform governance.
See all Document360 alternatives → · See all Kagi Search alternatives →
Recent activity from Document360 and Kagi Search
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoDocument360Publish dialog folds in AI suggestions and pre-publish checks
- 9d agoDocument360API v3 rebuild adds OAuth 2.0 and scoped API keys ⚡
- 16d agoDocument360Interactive API reference with a rebuilt Try It! console
- 1mo agoDocument360Find and replace spans variables, snippets, and links
- 1mo agoDocument360Native Mermaid diagrams and automatic llms.txt generation
- 2mo agoDocument360MCP server gains publishing and workflow controls
- 4mo agoKagi Search- Tuning the Orchestra #
- 5mo agoKagi Search- Small Web Expansion and Translate goes viral # ⚡
- 5mo agoKagi Search- Smoothing the edges #
- 6mo agoKagi Search- Kagi Translate on Android & iOS: translate anything, anywhere # ⚡
- 6mo agoKagi Search- Assistant reliability upgrades and Search refinements #
- 7mo agoKagi Search- New Year tune-up: smoother everything! #
Frequently asked questions
What is the difference between Document360 and Kagi Search?
They serve adjacent needs but don't currently overlap on shipped themes. Document360 is currently shipping more aggressively (velocity 6.3 vs 0.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.
Is Document360 better than Kagi Search?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Document360 is currently shipping more aggressively (velocity 6.3 vs 0.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.
What are the best alternatives to Document360?
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.
What are the best alternatives to Kagi Search?
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.