Teable
Teable ships Scheduled Routines, a four-tier AI model system, and multi-model image generation — three sparks in five days
A side-by-side editorial comparison of Contractbook and Wiki.js — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Contractbook | Wiki.js |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | contract-automation, ai-extraction, admin-controls, clm | wiki, self-hosted, enterprise-auth, sso |
| Last editorial update | 20d ago | 4d ago |
| Website | — | Visit → |
Contractbook hands the AI's extraction prompts over to the customer
Contractbook publishes short, emoji-headed notes, most of them arriving in same-day batches. The August 3 batch covered admin permission maps across spaces, OTP two-factor at login, calculations inside forms, a rebuilt search results page, and a new model behind AI data extraction. This release opens the default data fields themselves: the prompts behind each AI-detected field can be rewritten or renamed per contract type.
Wiki.js 3.0 beta closes enterprise auth and SEO gaps at sprint pace
Wiki.js is running a dual-track strategy: v2.5.x is in maintenance, collecting only security and bug fixes, while v3.0.0 moves through beta weekly with substantial new features. The v3 beta has concentrated recent drops on two converging pillars — enterprise authentication (Entra ID, LDAP, SAML, Discord with group-to-role mapping) and operations infrastructure (Audit Log, admin metrics, sitemap serving, prerendering for anonymous requests). All active development runs through a single committer, shipping multiple named features per weekly beta build.
Contractbook publishes short, emoji-headed notes, most of them arriving in same-day batches. The August 3 batch covered admin permission maps across spaces, OTP two-factor at login, calculations inside forms, a rebuilt search results page, and a new model behind AI data extraction. This release opens the default data fields themselves: the prompts behind each AI-detected field can be rewritten or renamed per contract type.
The AI extraction layer has been treated as a black box that Contractbook tunes and customers accept. Editable prompts break that — accuracy on a customer's own contract vocabulary becomes something they adjust rather than file a ticket about. It fits the wider pattern of the last few releases, where admin surfaces (space access maps, group permissions, contract-type management) are being built so companies can configure what used to be product defaults.
Once prompts are editable per contract type, per-field extraction quality becomes visible and arguable, so expect some form of confidence indicator or review step on extracted data next.
Wiki.js is running a dual-track strategy: v2.5.x is in maintenance, collecting only security and bug fixes, while v3.0.0 moves through beta weekly with substantial new features. The v3 beta has concentrated recent drops on two converging pillars — enterprise authentication (Entra ID, LDAP, SAML, Discord with group-to-role mapping) and operations infrastructure (Audit Log, admin metrics, sitemap serving, prerendering for anonymous requests). All active development runs through a single committer, shipping multiple named features per weekly beta build.
The v3 beta is systematically filling the gaps that have kept Wiki.js out of enterprise environments: SSO across major identity providers, compliance tooling, SEO readiness, and theme customization for whitelabeled deployments. Each week's build adds a category that a production deployment actually requires. The remaining areas not yet visible in the beta changelog are storage/sync providers and full editor-module parity with v2 — those gaps are the logical preconditions for an RC.
The next beta cycle will likely address storage backends and remaining editor modules. A release candidate becomes the natural next step once those surface areas are covered.
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 Contractbook or Wiki.js.
Teable ships Scheduled Routines, a four-tier AI model system, and multi-model image generation — three sparks in five days
GitHub Copilot tightens enterprise governance while AI security scanning drops its CodeQL prerequisite
Mattermost v11.11 adds data spillage exposure tracking as v12.0 breaking changes loom
SiYuan v3.8.4 beta cycle adds agent-controlled database fields, MiniMax image gen, and skill file management
Nextcloud runs three LTS branches in parallel, shipping bug fixes and quiet performance wins.
Happeo doubles down on SEO content to own intranet search terms for mid-market buyers.
See all Contractbook alternatives → · See all Wiki.js alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Wiki.js is currently shipping more aggressively (velocity 6.3 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. Wiki.js is currently shipping more aggressively (velocity 6.3 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 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.
Top Wiki.js alternatives in Collab are ranked by recent ship velocity. Browse the "Wiki.js alternatives" section above for the current picks, or visit /alternatives/wiki-js for the full list with editorial commentary on each.