Hive
Governance and cross-workspace plumbing, not new AI surface
A side-by-side editorial comparison of Document360 and Outline — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Document360 | Outline |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | api, oauth, mcp, knowledge base | knowledge-base, mcp, agent-write-access, document-permissions |
| Last editorial update | 1d ago | 5d ago |
| Website | — | — |
Document360 rebuilds its public API and turns docs into an agent-readable surface.
Document360 ships a dated release every two to four weeks and the last six months have been dominated by two threads: making the knowledge base machine-consumable, and hardening enterprise access control. The AI thread runs from the March MCP server through publishing and workflow tools in June and per-reader-group AI restrictions this month; the access thread runs SCIM provisioning, multiple JWT configurations, and reader permission inheritance. This release adds a ground-up API v3 with OAuth 2.0 and scoped keys.
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.
Document360 ships a dated release every two to four weeks and the last six months have been dominated by two threads: making the knowledge base machine-consumable, and hardening enterprise access control. The AI thread runs from the March MCP server through publishing and workflow tools in June and per-reader-group AI restrictions this month; the access thread runs SCIM provisioning, multiple JWT configurations, and reader permission inheritance. This release adds a ground-up API v3 with OAuth 2.0 and scoped keys.
The product is being rebuilt around programmatic access rather than portal usage. MCP made the knowledge base writable by an assistant, llms.txt made it discoverable to crawlers, copy-as-Markdown and open-in-ChatGPT made articles portable, and API v3 now gives all of that a permission-aware substrate the old v1/v2 endpoints could not support. The same permission model is showing up on the reader side too — Eddy AI features are now gated per reader group — so authorization is becoming the shared spine across API, AI, and reader access.
Expect the advanced API v3 endpoints to keep expanding as a paid add-on and the MCP server to be re-plumbed onto v3's scoped-key model, since MCP currently sits outside the new authorization scheme. A v1/v2 deprecation notice is the other likely follow-up.
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 Document360 or Outline.
Governance and cross-workspace plumbing, not new AI surface
A nightly canary train where the AI platform work hides between dependency bumps
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.
See all Document360 alternatives → · See all Outline alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Collab. Document360 is currently shipping more aggressively (velocity 6.3 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. Document360 is currently shipping more aggressively (velocity 6.3 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 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.
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.