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 Joplin and Komga — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Komga is rewriting its web UI in the open, shipping the beta alongside the old one.
Komga's release cadence is dominated by NextUI, a ground-up rewrite of the web interface that landed in beta with 1.26.0 and is served next to the existing UI at /next rather than replacing it. The three patch releases that followed within 48 hours were almost entirely NextUI shakedown work — scroll restoration, selection behavior, stylesheets failing to load under Tomcat. Underneath the interface work the server keeps widening format support, with rar5 handling in plain Java and solid rar4 archives earlier in the summer.
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.
Komga's release cadence is dominated by NextUI, a ground-up rewrite of the web interface that landed in beta with 1.26.0 and is served next to the existing UI at /next rather than replacing it. The three patch releases that followed within 48 hours were almost entirely NextUI shakedown work — scroll restoration, selection behavior, stylesheets failing to load under Tomcat. Underneath the interface work the server keeps widening format support, with rar5 handling in plain Java and solid rar4 archives earlier in the summer.
The project is running a long, deliberately cautious frontend migration: both UIs ship in the same binary, the feature gap is tracked publicly in an issue, and users opt in by URL. That arrangement should persist across several minor versions before the old WebUI is retired. The parallel v2 referential API suggests the rewrite is also being used to revise the server contract rather than only restyle the client.
Near-term releases should keep closing the NextUI feature gap issue by issue, with patch releases landing within days of each other. The old WebUI is unlikely to be removed before NextUI reaches parity and browser refresh stops falling back to it.
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 Joplin or Komga.
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 Joplin alternatives → · See all Komga alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Joplin and Komga are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 and Komga are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
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.
Top Komga alternatives in Collab are ranked by recent ship velocity. Browse the "Komga alternatives" section above for the current picks, or visit /alternatives/komga for the full list with editorial commentary on each.