AFFiNE
A nightly canary train where the AI platform work hides between dependency bumps
A side-by-side editorial comparison of Teable and tufte — release velocity, themes, recent moves, and the top alternatives to consider.
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.
After three quiet years, tufte 0.15 finally lets Tufte-style documents cross-reference.
Almost every release before the latest is a Pandoc compatibility fix — sidenotes breaking on Pandoc 2.15, margin references misplaced on 2.11, table and citation handling in `tufte_handout()`, `--wrap preserve` for margin content on 2.19. Then 0.15.0 in May 2026 breaks the pattern: `tufte_handout2()`, `tufte_book2()` and `tufte_html2()` wrap the corresponding bookdown formats, enabling text references and cross-references in captions, and `margin_fig_pos` gives global control over margin-figure placement.
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.
Almost every release before the latest is a Pandoc compatibility fix — sidenotes breaking on Pandoc 2.15, margin references misplaced on 2.11, table and citation handling in `tufte_handout()`, `--wrap preserve` for margin content on 2.19. Then 0.15.0 in May 2026 breaks the pattern: `tufte_handout2()`, `tufte_book2()` and `tufte_html2()` wrap the corresponding bookdown formats, enabling text references and cross-references in captions, and `margin_fig_pos` gives global control over margin-figure placement.
The package spent years absorbing upstream Pandoc churn without adding anything, and has now moved to sit on top of bookdown rather than reimplement around it. That is the sustainable direction for a format package this small: inherit cross-referencing and text references instead of maintaining a parallel implementation. Release intervals remain long, so this is unlikely to become a fast-moving package.
Expect the bookdown-backed formats to absorb further fixes as the recommended path, with the plain `tufte_*()` formats staying frozen against Pandoc changes.
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 Teable or tufte.
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.
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
bookdown's output is mature; its free hosting destination is being switched off.
See all Teable alternatives → · See all tufte alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Teable is currently shipping more aggressively (velocity 5.0 vs 0.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. Teable is currently shipping more aggressively (velocity 5.0 vs 0.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 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.
Top tufte alternatives in Collab are ranked by recent ship velocity. Browse the "tufte alternatives" section above for the current picks, or visit /alternatives/tufte-r for the full list with editorial commentary on each.