BookStack vs Claap
Side-by-side trajectory, velocity, and editorial themes.
Security-first wiki on a steady cadence; v26.05 lands the year's biggest feature batch
BookStack is a mature self-hosted wiki shipping on a near-monthly cadence dominated by security releases. The recent arc pairs a substantial v26.05 feature drop with a steady stream of patch releases hardening URL filtering, attachments, MFA, and permission checks. The project's priority is clearly locking down untrusted-editor and public-instance scenarios while keeping the feature surface moving.
The pattern is a feature-anchor release (v26.03, v26.05) followed by a run of point releases that are almost entirely security and dependency hardening. Feature work is trending toward finer-grained permissions (separate revision-view control), a broader API (tag browsing), and export/editor polish. Expect the same rhythm to continue: one meaty minor, then hardening.
The next release is likely another security/dependency point release (v26.05.3 or similar) continuing the attachment/URL-filtering hardening, with the following feature minor extending the API and permission model.
Claap expands from meeting recorder to the agent-readable deal-conversation layer
Claap records calls and meetings and generates AI insights for revenue teams, but recent releases widen both ends of the pipe. On the capture side it added mobile in-person recording and, most recently, contact-email ingestion; on the output side it exposes its smart tables and AI columns to MCP clients and pushes enrichment into HubSpot. The result is a single per-deal timeline rather than a pile of call recordings.
Claap is moving to sit above the CRM as the context layer for a deal: one timeline spanning calls, meetings, and emails, with AI grounded in the whole conversation and that context made readable by external agents through MCP. Deal and Company Reports push the same 'whole deal story, not just the CRM stage' framing.
The likely next steps are tighter two-way CRM sync and more agent tooling on top of the unified timeline—turning captured context into suggested next steps or deal-stage signals. This follows the observed MCP + HubSpot-enrichment + email-capture pattern.
See more alternatives to BookStack →
See more alternatives to Claap →