BookStack vs Claap
Side-by-side trajectory, velocity, and editorial themes.
BookStack opened a real theme extension surface, then spent six weeks patching CVEs.
BookStack shipped v26.03 in mid-March 2026 with a meaningful new theme module system and several theme events (page render, pre-save, OIDC URL customization) — the first time the project's customization surface has had real extension points rather than just template overrides. The next six weeks were almost entirely security work: four security-marked patch releases (v25.12.9, v26.03.1, v26.03.2, v26.03.4) addressing role-escalation via registration, hidden content leaking through markdown exports, style-code injection in revision diffs, and attachment/webhook URL validation gaps. Multiple researchers credited per release.
The arc is 'open up the platform, then defend it' — adding extension points was the v26.03 push, and the subsequent CVE volume reads as a coordinated audit response (often two researchers credited per advisory, suggesting public attention from pen-testers). The 25.12.x line is also still being patched in parallel, indicating the team is supporting both branches rather than forcing rapid upgrades.
Expect another v26.03.x patch release if the audit cycle isn't complete, then a return to feature work — likely more theme-event coverage and exposing more lifecycle hooks to match what the new module system can attach to. The dual-branch maintenance pattern probably continues until v25.12 hits its support cutoff.
Claap climbs from meeting analytics into deal and company reporting for revenue teams.
Claap shipped Deal Report and Company Report this week, attaching its conversation-intelligence data to higher-level revenue objects rather than individual meetings. Earlier in the cycle, the workspace got tighter admin controls (Members page, customization, cleaner CRM data flows), an automations engine refresh, three new VOIP integrations (lemlist, Allo, Ringover), and a Gong integration that lets Gong recordings flow into Claap. Claap AI was rebuilt under the 2.0 label.
The product is moving up the revenue-team stack: from 'record and recap a meeting' to 'tell us the full deal story across all conversations.' Reports keyed to deal and company entities mark that shift — revenue teams care about pipeline-level rollups, not call-level transcripts. Recent integrations (Gong, VOIP, CRM data hygiene) all extend Claap's data graph rather than its UI surface, which fits the same arc.
Expect Claap to push reports as a primary surface — likely forecasting, win/loss analysis, and rep coaching dashboards that consume the same Deal Report data. The Gong integration suggests Claap is willing to be the analytics layer on top of larger revenue-data graphs, not just the source of truth.
See more alternatives to BookStack →
See more alternatives to Claap →