SiYuan
SiYuan's 3.8 line is eight builds deep and still stabilizing the same four features
A side-by-side editorial comparison of EGroupware and Teable — release velocity, themes, recent moves, and the top alternatives to consider.
EGroupware's feed has become a security treadmill, with the 23.1 branch days from end of life.
Almost every release in this window is a security release, and most ship as a pair — one build for 26.x, an identical-scope backport for 23.1. Feature work exists but arrives as single lines inside those security notes: WebAuthN two-factor moving out of the former EPL add-on, OpenID bumped to current upstream libraries, invoice XML gaining reverse-charge exemption codes. The recurring theme in the fixes themselves is authentication — OAuth bearer tokens, OpenID regressions, an inverted email_verified check, passkeys broken by a missing proxy config.
Teable is spending this release cycle making computed fields and admin recovery trustworthy
Teable ships several tagged releases a day, and this window is dominated by reliability work: computed field and rollup correctness after deletions and migrations, resumable lookup backfills for large tables, and an admin Outbox that consolidates repeated database errors so incidents can be recovered in bulk. Bring-your-own-database gained real health reporting, with read-only databases now returning conflicts instead of failing repeatedly.
Almost every release in this window is a security release, and most ship as a pair — one build for 26.x, an identical-scope backport for 23.1. Feature work exists but arrives as single lines inside those security notes: WebAuthN two-factor moving out of the former EPL add-on, OpenID bumped to current upstream libraries, invoice XML gaining reverse-charge exemption codes. The recurring theme in the fixes themselves is authentication — OAuth bearer tokens, OpenID regressions, an inverted email_verified check, passkeys broken by a missing proxy config.
The project is consolidating everyone onto 26.x and has put a date on it: security coverage for 23.1 ends August 15, 2026, repeated as a warning in every 23.1 build since July. After that the twin-release pattern should stop and the cadence should halve. The authentication stack is the least settled part of the codebase right now — the July and August releases keep re-fixing OpenID and WebAuthN regressions introduced by their own predecessors.
Expect 23.1 builds to cease after August 15 and the feed to become single-track 26.x. On the evidence of the last six releases, expect at least one more OpenID or WebAuthN regression fix to follow the recent upstream library bump.
Teable ships several tagged releases a day, and this window is dominated by reliability work: computed field and rollup correctness after deletions and migrations, resumable lookup backfills for large tables, and an admin Outbox that consolidates repeated database errors so incidents can be recovered in bulk. Bring-your-own-database gained real health reporting, with read-only databases now returning conflicts instead of failing repeatedly.
The pattern is a platform hardening for larger and self-hosted deployments rather than adding surface. Most releases touch the computed-field engine, task queues or admin tooling — the parts that break at scale and are expensive to diagnose. The App Builder gets occasional additions, including custom favicons and metadata and an instance-wide control over whether platform AI keys reach apps.
Expect the reliability grind to continue through the computed-field and BYODB stack, with App Builder features arriving in small increments alongside it.
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 EGroupware or Teable.
SiYuan's 3.8 line is eight builds deep and still stabilizing the same four features
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 EGroupware alternatives → · See all Teable alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosting — within Collab. EGroupware and Teable are shipping at a similar cadence (velocity 5.0 vs 5.0, 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. EGroupware and Teable are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
Top EGroupware alternatives in Collab are ranked by recent ship velocity. Browse the "EGroupware alternatives" section above for the current picks, or visit /alternatives/egroupware 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.