Teable
Teable is spending this release cycle making computed fields and admin recovery trustworthy
A side-by-side editorial comparison of BookStack and Double — release velocity, themes, recent moves, and the top alternatives to consider.
BookStack's release stream is mostly security patches with feature drops in between.
Four of BookStack's last six releases are security releases. The newest closes five separate issues at once: external authentication could match the wrong user where IDs differ only by casing or accents, the login form leaked user existence through timing, exported content could load interactive content over file links, API errors exposed debug detail by default, and the default PDF renderer could probe files on the host. The one feature release, v26.05, added a page contents view in the editor, tag browsing API endpoints, a dedicated revision-viewing permission, in-UI MFA reset and new image and CSP controls.
Double is moving the whole bookkeeping workflow into a chat assistant, one billable task per week.
Double ships weekly, and for two months straight nearly every release has been another accounting task absorbed into Ask Double: transactions in late June, live spreadsheets, AI workpapers, metrics creation, voice input, and now Connections to outside tools. The assistant has gone from answering questions about the books to creating the artifacts accountants bill for. The most recent entry breaks the pattern — role-based restrictions on who can edit client properties — which is the administrative counterweight to everything else.
Four of BookStack's last six releases are security releases. The newest closes five separate issues at once: external authentication could match the wrong user where IDs differ only by casing or accents, the login form leaked user existence through timing, exported content could load interactive content over file links, API errors exposed debug detail by default, and the default PDF renderer could probe files on the host. The one feature release, v26.05, added a page contents view in the editor, tag browsing API endpoints, a dedicated revision-viewing permission, in-UI MFA reset and new image and CSP controls.
Cadence is set by responsible disclosures — a named researcher credited in nearly every patch — and the feature work leans the same way, toward finer permissions and content security controls. For a self-hosted wiki that users routinely expose publicly, hardening is the roadmap, with quarterly feature releases sitting between patch runs.
Expect another patch on the 26.05 line next. The permission and CSP work visible in v26.05 is the thread the following minor most plausibly continues, though the entries give no signal on timing.
Double ships weekly, and for two months straight nearly every release has been another accounting task absorbed into Ask Double: transactions in late June, live spreadsheets, AI workpapers, metrics creation, voice input, and now Connections to outside tools. The assistant has gone from answering questions about the books to creating the artifacts accountants bill for. The most recent entry breaks the pattern — role-based restrictions on who can edit client properties — which is the administrative counterweight to everything else.
The strategy is to make Ask Double the primary interface and reduce the app's tab-by-tab surface to a system of record behind it. Two constraints are being addressed in parallel: the assistant needed to reach data Double does not hold, which Connections solves, and firms needed guardrails before handing an assistant this much reach, which the permissions work starts. Exposing metrics through both Ask Double and an MCP/API endpoint suggests Double expects agents outside its own product to drive the platform too.
Connections should exit private beta and expand its connector list, since it is the dependency for the cross-tool briefings Double is pitching. Expect the permissions model to keep hardening in step with each new thing the assistant is allowed to create.
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 BookStack or Double.
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 BookStack alternatives → · See all Double alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — permissions — within Collab. Double is currently shipping more aggressively (velocity 7.5 vs 5.0), with 1 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. Double is currently shipping more aggressively (velocity 7.5 vs 5.0), with 1 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 BookStack alternatives in Collab are ranked by recent ship velocity. Browse the "BookStack alternatives" section above for the current picks, or visit /alternatives/bookstack for the full list with editorial commentary on each.
Top Double alternatives in Collab are ranked by recent ship velocity. Browse the "Double alternatives" section above for the current picks, or visit /alternatives/double for the full list with editorial commentary on each.