Hive
Governance and cross-workspace plumbing, not new AI surface
A side-by-side editorial comparison of Document360 and SiYuan — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Document360 | SiYuan |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 0 |
| Top themes | api, oauth, mcp, knowledge base | note-taking, ai-agent, mcp, semantic-search |
| Last editorial update | 1d ago | 12h ago |
| Website | — | Visit → |
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.
SiYuan's v3.8.0 train restates one AI feature set across seven consecutive builds.
SiYuan is deep in a v3.8.0 preview train — four alphas and three betas since August 1 — and every build republishes the same four headline features: an AI Agent, semantic search over AI embeddings with reranking, Model Context Protocol support, and OIDC authentication. Two pairs of these builds carry byte-identical published notes, so the per-build delta is not visible from the feed at all. What does vary is a long enhancement list covering sync, mobile platforms and database views.
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.
SiYuan is deep in a v3.8.0 preview train — four alphas and three betas since August 1 — and every build republishes the same four headline features: an AI Agent, semantic search over AI embeddings with reranking, Model Context Protocol support, and OIDC authentication. Two pairs of these builds carry byte-identical published notes, so the per-build delta is not visible from the feed at all. What does vary is a long enhancement list covering sync, mobile platforms and database views.
The release notes are cumulative rather than incremental, which makes the train read as a single release delivered in installments. Beneath the repeated feature banner the actual work is platform breadth: LAN peer-assisted acceleration for cloud sync, audio recording on Android and HarmonyOS, custom font import on mobile, and configurable Stable, Beta and Alpha update channels. Reaching beta.3 within ten days of the first alpha says the train is converging.
A v3.8.0 stable release looks close given the move from first alpha to third beta inside ten days. The update-channel setting arriving in this same cycle suggests the project intends to keep running parallel preview streams once it ships.
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 SiYuan.
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.
Jellyfin renumbers to 12.0 and spends the whole cycle paying down its backend rewrite.
Teable is spending its release budget making bring-your-own-database failures survivable.
See all Document360 alternatives → · See all SiYuan alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — mcp — within Collab. Document360 and SiYuan are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 and SiYuan are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 SiYuan alternatives in Collab are ranked by recent ship velocity. Browse the "SiYuan alternatives" section above for the current picks, or visit /alternatives/siyuan for the full list with editorial commentary on each.