Teable
Teable is spending this release cycle making computed fields and admin recovery trustworthy
A side-by-side editorial comparison of CommaFeed and Contractbook — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | CommaFeed | Contractbook |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | rss-reader, self-hosting, security-hardening, api-interop | contract-automation, permissions, two-factor-auth, ai-extraction |
| Last editorial update | 19h ago | 7d ago |
| Website | Visit → | — |
A self-hosted RSS reader that now spends most of its release notes on security.
CommaFeed is a self-hosted Google Reader replacement that has spent the 6.x-to-7.x stretch rebuilding its trust boundaries rather than its feature list. SSRF protection has been tightened in four consecutive releases, feed parsing now strips javascript: URLs before they reach the database, and OPML imports are filtered against import-time abuse. The 7.x line pairs that with client interop: Fever API, ReadKit compatibility, and now the Google Reader API.
Contract automation grows up: admin permission maps, 2FA, and forms that do their own arithmetic.
Contractbook released a batch of six changes on a single day covering three areas at once. Administration gets a company-wide Spaces access page answering who can reach which space and with what permission, plus OTP two-factor authentication at login. Contract creation gets calculation fields in forms that compute totals and pro-rated amounts and insert them into the document automatically. The AI side gets a new extraction model and a dedicated place to manage AI upload contract types, with built-in defaults now editable per company.
CommaFeed is a self-hosted Google Reader replacement that has spent the 6.x-to-7.x stretch rebuilding its trust boundaries rather than its feature list. SSRF protection has been tightened in four consecutive releases, feed parsing now strips javascript: URLs before they reach the database, and OPML imports are filtered against import-time abuse. The 7.x line pairs that with client interop: Fever API, ReadKit compatibility, and now the Google Reader API.
The project is positioning itself as a sync backend other people's apps talk to, not just a web reader. Each release adds another protocol or client fix while hardening the assumption that an instance may be publicly exposed with untrusted users on it. The 7.0.0 swap from JEXL to sandboxed CEL and the 7.3.0 flip of blockLocalAddresses to a secure default both trade self-hoster convenience for a safer out-of-the-box posture.
Expect continued client-protocol coverage and further SSRF narrowing; the recurring pattern in these entries is that every new fetch path gets a follow-up hardening release.
Contractbook released a batch of six changes on a single day covering three areas at once. Administration gets a company-wide Spaces access page answering who can reach which space and with what permission, plus OTP two-factor authentication at login. Contract creation gets calculation fields in forms that compute totals and pro-rated amounts and insert them into the document automatically. The AI side gets a new extraction model and a dedicated place to manage AI upload contract types, with built-in defaults now editable per company.
The pattern is a product being fitted for larger customers: the access-visibility page is gated to Accelerate and Enterprise plans, group-level company permissions landed earlier in the year, and 2FA closes the obvious procurement objection. Meanwhile the AI features are moving from fixed behaviour toward configurable behaviour — extraction types are now a company's own list rather than the vendor's. Calculations remove the last common reason to edit a generated .docx by hand.
The admin thread points toward more permission surface — audit trails or per-space delegation would follow naturally from a page that already explains where each permission comes from. Nothing in these entries indicates how much extraction accuracy actually improved.
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 CommaFeed or Contractbook.
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.
SiYuan's v3.8.0 train restates one AI feature set across seven consecutive builds.
See all CommaFeed alternatives → · See all Contractbook alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CommaFeed and Contractbook 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. CommaFeed and Contractbook 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 CommaFeed alternatives in Collab are ranked by recent ship velocity. Browse the "CommaFeed alternatives" section above for the current picks, or visit /alternatives/commafeed for the full list with editorial commentary on each.
Top Contractbook alternatives in Collab are ranked by recent ship velocity. Browse the "Contractbook alternatives" section above for the current picks, or visit /alternatives/contractbook for the full list with editorial commentary on each.