Teable
Teable is spending this release cycle making computed fields and admin recovery trustworthy
A side-by-side editorial comparison of SiYuan and Skedda — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | SiYuan | Skedda |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | note-taking, ai-agent, mcp, semantic-search | workplace-management, desk-booking, multi-venue-analytics, visitor-management |
| Last editorial update | 17h ago | 14d ago |
| Website | Visit → | — |
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.
Desk booking growing an org-level control layer for multi-site workplace teams.
Skedda's recent releases split cleanly in two: rule granularity in the booking engine (day-specific approvals, hour-precision booking windows, per-day priority access) and physical-space operations (tablet room terminals, bookable add-ons, issue reporting, visitor CSV import and richer visit exports). The Organization Hub, added in late July, aggregates utilization, bookings, and check-in rates across every venue in one view. Visitor management and reporting are both getting export-grade detail rather than headline features.
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.
Skedda's recent releases split cleanly in two: rule granularity in the booking engine (day-specific approvals, hour-precision booking windows, per-day priority access) and physical-space operations (tablet room terminals, bookable add-ons, issue reporting, visitor CSV import and richer visit exports). The Organization Hub, added in late July, aggregates utilization, bookings, and check-in rates across every venue in one view. Visitor management and reporting are both getting export-grade detail rather than headline features.
The product is moving up from a single-venue booking tool toward the operations layer for a portfolio of offices — cross-venue analytics, per-team priority rules, and terminals that work without an account all point at customers managing many sites and mostly non-logged-in occupants. Each new data-producing feature (visits, add-ons, issues, check-ins) has been followed by the reporting surface to read it back, which is how the Organization Hub got something worth aggregating.
Expect the Organization Hub to widen past utilization into the visitor, add-on, and issue data Skedda now collects, and for its setup to move from an account-manager request into self-serve configuration.
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 Skedda.
Teable is spending this release cycle making computed fields and admin recovery trustworthy
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
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.
See all SiYuan alternatives → · See all Skedda alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. SiYuan and Skedda 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. SiYuan and Skedda 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 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 Skedda alternatives in Collab are ranked by recent ship velocity. Browse the "Skedda alternatives" section above for the current picks, or visit /alternatives/skedda for the full list with editorial commentary on each.