CryptPad
CryptPad ships by season, and spends most of it keeping OnlyOffice documents intact.
A side-by-side editorial comparison of Tana and HedgeDoc — release velocity, themes, recent moves, and the top alternatives to consider.
Tana is rebuilding itself around meetings — capture, present, and AI wrap-up, all native
Tana, once a supertag-driven knowledge base, now spends nearly all its release energy on a meeting layer: a pre-meeting hub card, one-click capture of external Zoom/Teams/Meet calls through system audio, live document presentation, and AI agents that summarize and extract outcomes. The Today page has become the product's home surface, organizing the day around calls and their generated artifacts. Recent work is dense and iterative — join nudges, permission recovery, presentation palettes, voice agents — all pointed at the same target.
HedgeDoc 1.x releases are now mostly advisories — security in, features rarely.
The 1.x line ships on a roughly six-to-eight-week rhythm, and almost every release leads with security fixes: HTML injection through an email localpart, YAML frontmatter denial-of-service, CSRF in the Gist export, a rate-limit bypass via the CF-Connecting-IP header, SVG upload script execution. Around that, the recent additions are operator controls — an external-link warning page with a whitelist, configurable login and signup rate limits, an option to restrict uploads to registered users or disable them entirely.
Tana, once a supertag-driven knowledge base, now spends nearly all its release energy on a meeting layer: a pre-meeting hub card, one-click capture of external Zoom/Teams/Meet calls through system audio, live document presentation, and AI agents that summarize and extract outcomes. The Today page has become the product's home surface, organizing the day around calls and their generated artifacts. Recent work is dense and iterative — join nudges, permission recovery, presentation palettes, voice agents — all pointed at the same target.
The direction is unambiguous: Tana wants to own the full arc of a meeting — before (hub, invites, calendar sync), during (capture, present, live AI digest), and after (summaries, outcomes, review queue) — and fold the results back into its typed knowledge graph. External-meeting capture moving to on-by-default and live doc presentation without screen sharing put it in direct competition with Granola and Fellow, not just as a notes tool. The knowledge-base roots are increasingly the substrate that meeting outputs land in, not the headline.
Expect the next releases to deepen the AI wrap-up loop — richer automatic outcome extraction, agent actions triggered from meeting content, and tighter linking of meeting artifacts into typed entities — since that is the recurring thread across these entries.
The 1.x line ships on a roughly six-to-eight-week rhythm, and almost every release leads with security fixes: HTML injection through an email localpart, YAML frontmatter denial-of-service, CSRF in the Gist export, a rate-limit bypass via the CF-Connecting-IP header, SVG upload script execution. Around that, the recent additions are operator controls — an external-link warning page with a whitelist, configurable login and signup rate limits, an option to restrict uploads to registered users or disable them entirely.
This reads as a mature collaborative editor in hardening mode. New settings appear where an administrator needed a lever, not where a user asked for a feature, and the one substantial correctness fix in the window — data loss when five or more people edited a document at once — was a repair to the existing operational-transform client rather than new ground. Node 24 support and the removal of dead config options point the same direction: keeping a working product current.
Expect the next 1.x release to follow the same shape — one or more advisories plus a small configuration option — since every release in this window has done so.
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 Tana or HedgeDoc.
CryptPad ships by season, and spends most of it keeping OnlyOffice documents intact.
GitHub is hardening the registry it owns while Copilot absorbs every new model.
Zoho Sign is wiring signatures into agents and into every country's stamp law.
Avoma's real work is happening in MCP; its feed is buried under competitor comparison pages.
Bloomfire's feed is a knowledge-management content mill, batch-publishing SEO on the day it ships.
Paperless-ngx shipped its 3.0 rewrite, then spent a week putting out the fires.
See all Tana alternatives → · See all HedgeDoc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tana is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Tana is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Tana alternatives in Collab are ranked by recent ship velocity. Browse the "Tana alternatives" section above for the current picks, or visit /alternatives/tana for the full list with editorial commentary on each.
Top HedgeDoc alternatives in Collab are ranked by recent ship velocity. Browse the "HedgeDoc alternatives" section above for the current picks, or visit /alternatives/hedgedoc for the full list with editorial commentary on each.