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 HedgeDoc and Joplin — release velocity, themes, recent moves, and the top alternatives to consider.
A collaborative markdown editor on a security-driven maintenance cadence.
HedgeDoc's 1.x line ships every one to two months and is dominated by security response. Recent releases carry seven advisories between them — HTML injection via an email localpart, YAML frontmatter denial of service, CSRF in the Gist export, a rate-limit bypass through CF-Connecting-IP, a permission-value validation gap, missing upload security headers, and script execution in uploaded SVGs. Around those sit configuration knobs for the external-link warning, webp uploads, and rate limits.
Joplin 3.7 ships AI chat, semantic search, and MCP integration — all off by default, all controllable by the user.
Joplin 3.7 is the product's first real AI release: an in-app chat panel for querying the currently open note, semantic (meaning-based) search across notebooks, and an MCP server that lets external AI assistants connect to Joplin's note graph. The implementation is privacy-first by design — AI is disabled by default, local models (Ollama, LM Studio) are explicitly supported, and cloud AI services only receive the specific note content relevant to a request rather than the full notebook. A companion documentation post published September 14 lays out the privacy model explicitly.
HedgeDoc's 1.x line ships every one to two months and is dominated by security response. Recent releases carry seven advisories between them — HTML injection via an email localpart, YAML frontmatter denial of service, CSRF in the Gist export, a rate-limit bypass through CF-Connecting-IP, a permission-value validation gap, missing upload security headers, and script execution in uploaded SVGs. Around those sit configuration knobs for the external-link warning, webp uploads, and rate limits.
Two threads run in parallel. The perimeter work reduces attack surface and maintenance burden at once: old API endpoints and unused config are deleted, Node 18 support is dropped now that its security window has closed, and features added in one release tend to gain an off switch in the next. The second thread is realtime correctness — concurrent-editing data loss, connections dropped mid-handshake, operations discarded during revision gap recovery — which is the only work aimed at the core editing experience rather than its edges.
Expect the 1.x line to continue as security and correctness maintenance, with more legacy endpoints and configuration removed rather than new editing features added.
Joplin 3.7 is the product's first real AI release: an in-app chat panel for querying the currently open note, semantic (meaning-based) search across notebooks, and an MCP server that lets external AI assistants connect to Joplin's note graph. The implementation is privacy-first by design — AI is disabled by default, local models (Ollama, LM Studio) are explicitly supported, and cloud AI services only receive the specific note content relevant to a request rather than the full notebook. A companion documentation post published September 14 lays out the privacy model explicitly.
Joplin is repositioning from a sync-agnostic note-taking app into an AI-native knowledge base, differentiated by opt-in, local-first controls. The HMD Terra M preload partnership and the warrant canary point to a deliberate push toward privacy-conscious enterprise and professional users who distrust cloud-first tools. The MCP integration is particularly strategic: it makes Joplin's note graph accessible to external orchestration pipelines without locking into any particular AI provider.
The next major release will likely expand AI chat to multi-note context — currently limited to the open note — and add more configurable MCP tools. The HTR (handwritten text recognition) project from the 2024 French government partnership is also likely to appear in a near-term release.
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 HedgeDoc or Joplin.
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 HedgeDoc alternatives → · See all Joplin alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Joplin 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. Joplin 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 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.
Top Joplin alternatives in Collab are ranked by recent ship velocity. Browse the "Joplin alternatives" section above for the current picks, or visit /alternatives/joplin for the full list with editorial commentary on each.