Hive
Governance and cross-workspace plumbing, not new AI surface
A side-by-side editorial comparison of AFFiNE and Document360 — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | AFFiNE | Document360 |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | byok, copilot, canary-train, dependency-hygiene | api, oauth, mcp, knowledge base |
| Last editorial update | 5h ago | 1d ago |
| Website | Visit → | — |
A nightly canary train where the AI platform work hides between dependency bumps
AFFiNE ships near-daily canary builds alongside a slower beta line, and the two are not monotonic — version numbers move sideways as branches leapfrog. The bulk of any given week is Renovate-driven dependency maintenance and CI action upgrades. The substantive platform work, when it lands, arrives inside an ordinary-looking canary tag rather than a headline release.
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.
AFFiNE ships near-daily canary builds alongside a slower beta line, and the two are not monotonic — version numbers move sideways as branches leapfrog. The bulk of any given week is Renovate-driven dependency maintenance and CI action upgrades. The substantive platform work, when it lands, arrives inside an ordinary-looking canary tag rather than a headline release.
The direction is a workspace-scoped AI platform that customers configure themselves: BYOK provider profiles with model catalogs, capability validation and credential rotation, sitting alongside the MCP credential management shipped earlier. Copilot configuration is being simplified in the same motion, with provider-specific legacy settings removed from public responses. Underneath that, storage and sync are getting steady hardening.
Expect the BYOK and Copilot convergence work to keep landing in canary builds before any of it reaches the beta line, with more legacy provider fields removed as the new profile model becomes the only path.
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.
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 Document360.
Governance and cross-workspace plumbing, not new AI surface
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.
Teable is spending its release budget making bring-your-own-database failures survivable.
See all AFFiNE alternatives → · See all Document360 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. AFFiNE and Document360 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. AFFiNE and Document360 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 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 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.