AFFiNE
A nightly canary train where the AI platform work hides between dependency bumps
A side-by-side editorial comparison of SiYuan and Teable — release velocity, themes, recent moves, and the top alternatives to consider.
SiYuan 3.8.0 ships: MCP, an AI agent and semantic search reach general availability
SiYuan is a self-hostable block-based notes application. The 3.8.0 line opened on 4 August with four features it had never shipped - an AI Agent, semantic search over embeddings, Model Context Protocol support and OIDC authentication - then spent eight prerelease builds stabilizing them. The final release landed on 12 August, adding LAN peer-assisted cloud sync and a long tail of cross-platform polish.
A daily release train grinding on BYODB reliability and large-table performance.
Teable ships a numbered release most days, and the current run is dominated by operational hardening rather than new surface. The recurring subject is bring-your-own-database: health statuses for read-only, unreachable and degraded connections, 409 conflicts on read-only writes, paused-and-resumed computed tasks, and tightened validation that now rejects private or internal network addresses. Alongside that sits a steady stream of large-table performance work — bulk deletes across tens of thousands of records, view duplication, lookup and cascade chains, field conversions.
SiYuan is a self-hostable block-based notes application. The 3.8.0 line opened on 4 August with four features it had never shipped - an AI Agent, semantic search over embeddings, Model Context Protocol support and OIDC authentication - then spent eight prerelease builds stabilizing them. The final release landed on 12 August, adding LAN peer-assisted cloud sync and a long tail of cross-platform polish.
The 3.8.0 cycle is the same pattern as 3.7.0: freeze a feature block early, then iterate builds for a week without changing what is in it. Where 3.7 was about the application's own extensibility - a kernel plugin system, a CLI, a redesigned interface - 3.8 points outward, making the knowledge base something external AI tools can query rather than something you only read yourself. Platform breadth continues underneath both, with HarmonyOS now getting the same attention as Android.
On the 3.7 precedent, expect a 3.8.x alpha train to open within days carrying fixes against the newly released AI features; the MCP surface is the most likely thing to widen, since it currently exposes the knowledge base rather than SiYuan's editing operations.
Teable ships a numbered release most days, and the current run is dominated by operational hardening rather than new surface. The recurring subject is bring-your-own-database: health statuses for read-only, unreachable and degraded connections, 409 conflicts on read-only writes, paused-and-resumed computed tasks, and tightened validation that now rejects private or internal network addresses. Alongside that sits a steady stream of large-table performance work — bulk deletes across tens of thousands of records, view duplication, lookup and cascade chains, field conversions.
The centre of gravity is self-hosted and admin-operated deployments: the Admin Outbox anomaly tooling, bulk incident recovery, license checkout fixes and BYODB remediation guidance all serve an operator, not an end user. The App Builder is developing in parallel, picking up publishing metadata and an instance-wide control over whether platform-managed AI keys reach apps. The new 10-minute floor on scheduled automations is the first sign of the platform imposing cost discipline on its own execution surface.
Expect the automation interval floor to be followed by further execution quotas or tiering, given it was introduced with existing configurations grandfathered in. BYODB looks close to feature-complete on health and recovery, so the next visible work is likelier on the App Builder.
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 SiYuan or Teable.
A nightly canary train where the AI platform work hides between dependency bumps
pagedown is down to one small fix a year, mostly absorbing changes from elsewhere.
After three quiet years, tufte 0.15 finally lets Tufte-style documents cross-reference.
xaringan has settled into theme upkeep and Pandoc-era compatibility patches.
Double is turning its accounting assistant into the way the work gets done
litedown grows from a lean renderer into a book and site generator
See all SiYuan alternatives → · See all Teable alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Collab. SiYuan is currently shipping more aggressively (velocity 6.3 vs 5.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. SiYuan is currently shipping more aggressively (velocity 6.3 vs 5.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 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.
Top Teable alternatives in Collab are ranked by recent ship velocity. Browse the "Teable alternatives" section above for the current picks, or visit /alternatives/teable for the full list with editorial commentary on each.