Obsidian vs Logseq

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Obsidian—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Logseq—none0/10

   There is no llms.txt file (probe returned 404) and no evidence of agent-oriented docs formatted for LLM consumption; the docs are standard human-facing markdown/wiki pages.

   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Obsidian
   Obsidian!disputedcontradicted4/10

   Vendor docs claim an Obsidian Sync 'headless client' explicitly designed for CI pipelines and automated agent workflows, but the independent runtime probe found Obsidian ships no official CLI or vendor automation interface, with only community-built (unofficial) tooling for programmatic access — directly contradicting the headless-CI claim. Missing for 10: independent confirmation the headless Sync client actually exists and works, official CLI documentation, and evidence of real CI usage.

   • [claimed-docs] “Obsidian Sync offers a headless client to sync vaults without using the desktop app. Useful for CI pipelines, agents, and automated workflow…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq is a desktop/mobile Electron app with a local HTTP API and plugin system, but nothing in the evidence describes a headless mode, CLI, or CI-runnable binary for automation — the HTTP API requires the desktop app to be running interactively. Missing for 10: any documented headless/CLI mode, CI examples, or automation-oriented server mode.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Obsidian
   Obsidian~partialprobed3/10

   Obsidian has no first-party MCP client/server integration; the only evidence is a runtime probe noting that MCP support exists solely via unofficial community plugins, with no vendor-documented feature. missing for 10: official MCP client documentation, first-party plugin support, hands-on evidence of using MCP tools inside Obsidian.

   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq documents a plugin system, HTTP API, and URL protocol for third-party integration, but nothing in the evidence pack mentions MCP servers or any mechanism for Logseq to consume MCP tools. Community comments even lament that AI tools like Claude/Codex can't be used to update pages, reinforcing the absence of MCP support.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Obsidian—none0/10

   Obsidian is a note-taking platform (not itself an agent), so an official MCP server is a fair ecosystem question, but the evidence explicitly states Obsidian ships no official CLI or vendor MCP server, with MCP integrations existing only as community projects.

   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq documents a local HTTP API and a plugin ecosystem for third-party integrations, but there is no mention anywhere in the evidence of an official Model Context Protocol (MCP) server or endpoint. Since Logseq is a knowledge-base platform (not itself an AI agent), shipping an official MCP server is a fair axis to ask about, but no such capability is evidenced.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Obsidian—none0/10

   Evidence explicitly confirms Obsidian ships no official CLI (the probe notes only community MCP servers exist, and no CLI is mentioned anywhere in docs). Missing for 10: any official CLI tool, documentation of CLI commands, or first-party automation interface for AI-native/agentic workflows.

   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   No evidence of an official Logseq CLI; the product exposes a local HTTP API, a URL protocol scheme, and plugins, but nothing about a command-line interface for AI-native automation. Missing for 10: any mention of an official CLI tool, its command set, or installation/usage docs.

   ⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Obsidian~partialprobed6/10

   Obsidian exposes a documented TypeScript Plugin API (obsidian-api on GitHub, e.g. the Vault interface) and a custom URI protocol for triggering actions like opening/creating notes, giving programmatic control over the app. However this requires building/compiling a plugin rather than calling a simple REST/HTTP API, and the probe explicitly notes Obsidian ships no official CLI or vendor MCP server, with MCP integrations being community-built. Missing for 10: a first-party REST/HTTP or MCP API surface for external agent control, and evidence of AI-native workflows actually driving Obsidian via the documented API.

   • [claimed-docs] “Obsidian URI is a custom URI protocol supported by Obsidian that lets you trigger various actions, such as opening a note or creating a note…”
   • [github] “Vault, the interface that lets you interact with files and folders in the vault.”
   • [github] “`Vault`, the interface that lets you interact with files and folders in the vault.”
   • [claimed-docs] “Build plugins to extend the existing functionality in Obsidian using TypeScript.”
   • [claimed-docs] “Plugins let you extend Obsidian with your own features to create a custom note-taking experience.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq~partialprobed6/10

   Logseq documents a local HTTP APIs server explicitly for 'external access to the database through authorization' and a separate community-maintained plugin API reference, plus a logseq:// protocol for third-party invocation — all documented, public interfaces for programmatic control. However, there's no formal machine-readable spec (probes show 404s for openapi.json/llms.txt) and a community report explicitly states losing the ability to use Claude/codex to write/update pages after a version change, indicating real-world friction for AI-driven API use. Missing for 10: a formal OpenAPI/machine spec, first-party confirmation of AI-agent compatibility, and independent corroboration that the HTTP API reliably supports agentic write workflows.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Obsidian—none0/10

   No evidence of scoped/least-privilege API credential issuance for agents; Obsidian has no official API/credential system, and community plugins run with full filesystem/network access rather than restricted permissions (obsidian-comm-10). No mention of any credentialing or permission-scoping mechanism anywhere in the docs.

   • [community] “Confirmed via Obsidian's own docs: there is no sandboxing at all for community plugins - every plugin has full access to your computer's fil…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq's local HTTP API server requires a single authorization token for full graph access, but there is no evidence of scoped or least-privilege credential issuance (e.g., read-only vs write, per-agent scopes, or permission granularity) for AI agents.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “local HTTP server to access logseq's graph”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Obsidian~partialprobed6/10

   Obsidian ships an official, documented Plugin API/SDK (TypeScript) with a public GitHub repo (obsidian-api) and developer docs for building plugins, themes, and extensions, giving AI-native developers a real, first-party surface to build against. However, there is no official MCP server or AI-specific SDK/CLI (confirmed absent in the probe), plugins run with full filesystem/network access without sandboxing (community-verified), and Restricted Mode blocks third-party code by default — meaning agentic integration relies on community-built connectors rather than an official agent-facing SDK. Missing for 10: an official MCP server or AI/agent SDK, an official CLI, and evidence of first-party sandboxing suitable for autonomous agent code.

   • [claimed-docs] “In this tutorial, you'll compile a sample plugin from source code and load it into Obsidian.”
   • [claimed-docs] “Build plugins to extend the existing functionality in Obsidian using TypeScript.”
   • [claimed-docs] “you'll compile a sample plugin from source code and load it into Obsidian.”
   • [claimed-docs] “Plugins let you extend Obsidian with your own features to create a custom note-taking experience.”
   • [github] “Vault, the interface that lets you interact with files and folders in the vault.”
   • [github] “`Vault`, the interface that lets you interact with files and folders in the vault.”
   • [claimed-docs] “By default, Obsidian runs in Restricted Mode to prevent third-party code execution.”
   • [community] “Confirmed via Obsidian's own docs: there is no sandboxing at all for community plugins - every plugin has full access to your computer's fil…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq~partialprobed6/10

   Logseq exposes a genuine plugin API/SDK (marketplace with hundreds of packages, load-unpacked plugin support) plus a local HTTP APIs server and a logseq:// URL protocol for third-party integration, giving AI-native builders real programmatic surfaces. However, the plugin API documentation is explicitly community-driven rather than official, and probes found no OpenAPI/machine-readable spec or llms.txt for these APIs. Missing for 10: official (not community-maintained) SDK documentation, an OpenAPI/schema spec, and evidence of first-party AI-agent integration guidance.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Obsidian—none0/10

   No evidence in the pack of Obsidian offering webhooks or an event-subscription API; the plugin system exposes in-app events (e.g., Vault interface) but nothing about outbound webhook subscriptions, and the probe explicitly notes no official MCP/CLI or webhook-style integration exists, only community projects.

   • [github] “Vault, the interface that lets you interact with files and folders in the vault.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq offers a local HTTP API and a plugin system, but the evidence pack shows no webhook subscription mechanism (outbound event notifications) — only a local HTTP server for pull-based access and a custom URI protocol for inbound invocation. No documentation or community evidence describes subscribing to events via webhooks.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Obsidian—none0/10

   Obsidian's core product has no first-party AI-generated insights or suggestions feature; the only AI capability comes from third-party community plugins (e.g., Text-Generator), and community evidence explicitly notes 'no decent RAG functionality among Obsidian AI plugins,' indicating this is not a native, reliable capability of the product itself.

   • [community] “There's no decent RAG functionality among Obsidian AI plugins, but the Text-Generator plugin with links/backlinks pulled into inference cont…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq's docs describe queries, plugins, journaling, sync, and export, but nowhere document a native AI-generated insights or suggestion feature. The only AI-adjacent mention is a community complaint that a user could no longer use Claude/codex to write/update pages, which points to third-party integration loss, not a first-party AI feature.

   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Obsidian—none0/10

   The evidence pack shows Obsidian's plugin architecture, URI protocol for triggering actions, and a large community-plugin ecosystem, but nothing demonstrates autonomous background automation (e.g., scheduled/triggered agent-like workflows running without user interaction). The probe explicitly notes no official CLI or vendor MCP server, and Restricted Mode by default blocks third-party code execution unless manually enabled, further undercutting any 'runs autonomously in background' claim.

   • [claimed-docs] “Obsidian URI is a custom URI protocol supported by Obsidian that lets you trigger various actions, such as opening a note or creating a note…”
   • [claimed-docs] “By default, Obsidian runs in Restricted Mode to prevent third-party code execution.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Evidence shows Logseq has a plugin system, local HTTP API, and a custom URL protocol for third-party integration, but nothing describes autonomous, unattended background automations (e.g., schedulers, triggers, agent workflows) running without user action.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Obsidian—none0/10

   There is no evidence of a built-in AI assistant in Obsidian; all AI-related capability mentioned (e.g., Text-Generator plugin) is explicitly a third-party community plugin, not a native feature, and the probe confirms no official vendor MCP server or AI tooling. Community plugins requiring full filesystem access (obsidian-comm-10) are the only AI-adjacent route, but that's an ecosystem extension, not a delegated built-in assistant.

   • [community] “There's no decent RAG functionality among Obsidian AI plugins, but the Text-Generator plugin with links/backlinks pulled into inference cont…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”
   • [community] “Confirmed via Obsidian's own docs: there is no sandboxing at all for community plugins - every plugin has full access to your computer's fil…”

   proof ↗⚑ flag

   Logseq—none0/10

   No evidence in the docs or community pack of a built-in AI assistant inside Logseq; only third-party plugins, HTTP API, and protocol integrations exist, and one community comment references using external tools like Claude/Codex to edit pages, not a native assistant.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Obsidian—none0/10

   Obsidian's own docs describe a traditional Command Palette, keyboard shortcuts, and a plugin API, but there is no first-party natural-language command interface; the probe explicitly notes Obsidian ships no official CLI or vendor MCP server, with any LLM/NL functionality (e.g. Text-Generator plugin) coming from community plugins rather than the product itself.

   • [claimed-docs] “Tabs, Command Palette, plugins,”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”
   • [community] “There's no decent RAG functionality among Obsidian AI plugins, but the Text-Generator plugin with links/backlinks pulled into inference cont…”

   proof ↗⚑ flag

   Logseq—none0/10

   No evidence of a native natural-language command interface, chat-based control, or AI assistant in Logseq's docs; the product is described as a block/outline-based knowledge base with query syntax and plugin APIs, not NL commands. One community comment (logseq-comm-11) references losing the ability to use Claude/Codex to edit pages, implying such capability existed only via third-party plugin integration, not a first-party feature, and it's now broken in the new DB version.

   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Obsidian—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Logseq—none0/10

   There is a plugin API doc site and a local HTTP API, but no evidence of an interactive API reference with runnable examples; probes explicitly show no OpenAPI/swagger spec and no llms.txt found at the plugin docs site.

   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Obsidian—none0/10

   Obsidian has a plugin API and developer docs (TypeScript API reference), but no evidence of a downloadable machine-readable spec like OpenAPI/Swagger for any REST or programmatic interface; the probe explicitly notes no official CLI or vendor MCP server, and no OpenAPI spec is mentioned anywhere in the evidence pack.

   • [claimed-docs] “Build plugins to extend the existing functionality in Obsidian using TypeScript.”
   • [github] “Vault, the interface that lets you interact with files and folders in the vault.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq documents a local HTTP API server and a plugin API, but there is no evidence of a downloadable machine-readable spec (OpenAPI/Swagger) for either; explicit probes for openapi.json/swagger.json at the plugin docs site returned 404s.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Obsidian
   Obsidian!disputedcontradicted3/10

   Obsidian's docs claim a 'Restricted Mode' that prevents third-party code execution (obsidian-docs-27), which could be read as a sandbox safeguard, but hands-on community evidence directly contradicts this: 'there is no sandboxing at all for community plugins - every plugin has full access to your computer's filesystem and can make network requests' (obsidian-comm-10), and a third party built a separate sandboxed app specifically because Obsidian plugins run with full system access on sensitive data (obsidian-comm-11). There is no documented feature for spinning up an isolated test vault/sandbox distinct from a production vault for AI-agent testing. Missing for 10: an official sandbox/test-vault feature, evidence of isolated execution for agent actions, and resolution of the restricted-mode vs. no-sandboxing contradiction.

   • [claimed-docs] “By default, Obsidian runs in Restricted Mode to prevent third-party code execution.”
   • [community] “Confirmed via Obsidian's own docs: there is no sandboxing at all for community plugins - every plugin has full access to your computer's fil…”
   • [community] “A company wrote a sandboxed alternative app because community plugins are too risky running with full system access when working on sensitiv…”

   proof ↗⚑ flag

   Logseq—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Obsidian—none0/10

   Evidence covers Obsidian's plugin API, developer docs, and file formats, but there is no mention of a versioning scheme or documented deprecation policy for the Obsidian API. The developer docs describe building plugins but do not address API version guarantees or backward-compatibility commitments. Missing for 10: any documentation of API versioning, semver policy, or deprecation timelines/announcements.

   ⚑ flag

   Logseq—none0/10

   Logseq documents a local HTTP API and a plugin API, but there is no evidence of API versioning or a documented deprecation policy anywhere in the docs; probes for openapi/llms.txt specs return 404s, and community comments (e.g., DB-version migration breaking AI tool integrations) suggest breaking changes without clear versioning guarantees.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

Agent ops

1. ai-native userMy coding agent or assistant can read AND write my notes headlessly — through a documented local API, vendor API, or MCP server — without me touching the GUI

   weight 3 · round to Obsidian
   Obsidian~partialprobed4/10

   Obsidian stores notes as plain local Markdown files (obsidian-docs-20, obsidian-docs-23), which lets an agent read/write vault contents directly on disk without touching the GUI — but this is not a documented API or protocol, just an emergent property of the file format. The probe explicitly confirms Obsidian ships no official CLI or vendor MCP server, with MCP servers being community-only projects (obsidian-probe-rt-1), and the only documented headless integration (Obsidian URI, obsidian-docs-8) is for triggering GUI actions, not structured read/write. Missing for 10: an official vendor-documented local API or MCP server, first-party support for programmatic note read/write, and evidence of hands-on agent integration.

   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [claimed-docs] “Obsidian URI is a custom URI protocol supported by Obsidian that lets you trigger various actions, such as opening a note or creating a note…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq!disputedcontradicted5/10

   Logseq documents a local HTTP APIs server explicitly built 'to support external access to the database through authorization,' which would let an agent read/write notes headlessly, plus a plugin API and logseq:// protocol for third-party invocation. However, a hands-on community report directly contradicts this working capability, stating 'Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me' — indicating the API-based read/write access broke (likely in the newer DB version). Missing for 10: confirmation the HTTP API still supports write access post-DB-migration, an official MCP server, and independent corroboration that agent read/write works reliably today.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “local HTTP server to access logseq's graph”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

Ai assist

1. ai-native userConnect external LLMs and AI tools to my notes through first-party connectors or an ecosystem of AI plugins

   weight 2 · round drawn
   Obsidian~partialprobed5/10

   Obsidian has no first-party AI/LLM connector or vendor MCP server (confirmed by probe: 'no official CLI or vendor MCP server... MCP servers for Obsidian are community projects'), but its large community plugin ecosystem (7,275 plugins) does include AI tools like the Text-Generator plugin, cited by users as a productive LLM interface. This satisfies the 'ecosystem of AI plugins' half of the story but not the 'first-party connectors' half. Missing for 10: official first-party AI/LLM integration or vendor-maintained MCP server, broader documentation of AI plugin capabilities (e.g., RAG), and evidence these plugins are robust (community notes 'no decent RAG functionality among Obsidian AI plugins').

   • [community] “There's no decent RAG functionality among Obsidian AI plugins, but the Text-Generator plugin with links/backlinks pulled into inference cont…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”
   • [claimed-docs] “Use plugins to adapt Obsidian to fit your specific needs, such as support for additional file formats or integrating with a third-party serv…”
   • [claimed-docs] “Learn how to extend Obsidian with plugins built by the community.”

   proof ↗⚑ flag

   Logseq~partialprobed5/10

   Logseq has no documented first-party AI/LLM connector, but its open plugin marketplace (617 registered packages), local HTTP API for external graph access, and logseq:// protocol for third-party app integration provide an ecosystem pathway for AI plugins/tools to connect to notes. Community evidence confirms some users did integrate LLMs like Claude/codex to write/update pages, but also that this broke in the newer DB version, showing fragility rather than a robust first-party AI integration story. Missing for 10: an official AI/LLM connector or documented AI plugin category, first-party docs mentioning LLM integration, and confirmation that AI plugin workflows are stable across versions.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

2. ai-native userA built-in AI assistant can answer questions, summarize, and draft grounded in my own notes — with clear controls over what data it sees

   weight 2 · round drawn
   Obsidian—none0/10

   Obsidian's core product ships no built-in AI assistant; the only AI-related evidence describes third-party community plugins, and one commenter explicitly states 'there's no decent RAG functionality among Obsidian AI plugins,' undermining any grounded-in-notes assistant claim. There is no first-party documentation of an official AI feature with data-access controls.

   • [community] “There's no decent RAG functionality among Obsidian AI plugins, but the Text-Generator plugin with links/backlinks pulled into inference cont…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq's own docs describe journals, queries, plugins, HTTP API, and sync, but there is no evidence of a built-in first-party AI assistant that answers/summarizes/drafts grounded in notes with data-visibility controls. A community comment even references losing the ability to use Claude/Codex on notes after a version change, implying any AI usage was via external plugins/tools rather than a native assistant.

   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Logseq
   Obsidian—none0/10

   The evidence pack shows Obsidian's file-based storage, plugin/API extensibility (Vault interface, community plugins), and Bases for database-like views, but nothing documents a bulk-operation capability (e.g., batch rename, bulk tag/metadata edit, multi-note transform) that an AI-native user could invoke across many items at once. The generic plugin API and 7,275-plugin ecosystem are extensibility building blocks, not evidence of a delivered bulk-operations feature.

   • [claimed-docs] “Bases is a core plugin that lets you create database-like views of your notes.”
   • [github] “Vault, the interface that lets you interact with files and folders in the vault.”
   • [github] “`Vault`, the interface that lets you interact with files and folders in the vault.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq~partialclaimed4/10

   Logseq exposes a local HTTP API and plugin system that could be used to script bulk edits across many blocks/pages, and its query language ({{query}}) can surface many items at once, but there is no documented native bulk-operation feature (e.g., mass rename, bulk tag, batch move) demonstrated in the evidence pack. missing for 10: explicit bulk-edit/bulk-update API or UI feature, evidence of an AI agent actually performing bulk operations via the HTTP API, independent hands-on confirmation of scale.

   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Obsidian—none0/10

   Obsidian's evidence shows a plugin API, a URI protocol for triggering actions, and a large community plugin ecosystem, but there is no documented built-in rule engine or automation system that fires actions automatically on events (e.g., note-created, tag-added triggers). Obsidian URI (obsidian-docs-8) requires an external caller, not an internal event-trigger rule system, and no plugin or first-party feature is cited that implements conditional automation.

   • [claimed-docs] “Obsidian URI is a custom URI protocol supported by Obsidian that lets you trigger various actions, such as opening a note or creating a note…”
   • [claimed-docs] “Use plugins to adapt Obsidian to fit your specific needs, such as support for additional file formats or integrating with a third-party serv…”
   • [claimed-docs] “Plugins let you extend Obsidian with your own features to create a custom note-taking experience.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq's docs describe journaling, queries, plugins, HTTP APIs, and protocol handlers, but nowhere document a rules/trigger system where user-defined events automatically fire actions (e.g., 'when block tagged X, do Y'). The plugin API and marketplace could theoretically enable such automation, but no evidence shows a first-party or documented feature for event-triggered rules.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Obsidian—none0/10

   No evidence describes any Obsidian feature for scheduling recurring jobs or workflows; core plugins (daily notes, templates, bases) and the URI protocol are for triggering/creating notes, not for time-based recurring automation. The plugin ecosystem is large but no specific scheduling/automation plugin or native scheduler is documented.

   • [claimed-docs] “Daily notes is a core plugin that opens a note based on today's date, or creates it if it doesn't exist.”
   • [claimed-docs] “Obsidian URI is a custom URI protocol supported by Obsidian that lets you trigger various actions, such as opening a note or creating a note…”
   • [claimed-docs] “Use plugins to adapt Obsidian to fit your specific needs, such as support for additional file formats or integrating with a third-party serv…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq—none0/10

   No evidence of any scheduling, cron-like, or recurring workflow/automation capability in Logseq's docs or community discussion; the docs cover journaling, queries, plugins, HTTP API, and sync but nothing about triggering recurring jobs or automated workflows.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Obsidian—none0/10

   Obsidian offers file version history for notes (obsidian-docs-28) and third-party Git sync for backups (obsidian-comm-8), but there is no evidence of any built-in mechanism to version, review, or roll back 'automations' (e.g., plugin configs, Templater/QuickAdd scripts, or workflow definitions) — Obsidian has no native automation/workflow builder at all, only community plugins that could theoretically be automation-like but aren't documented with any versioning/rollback tooling. Missing for 10: any documented automation-specific versioning system, review/diff tooling for automation changes, or rollback mechanism tied to plugin/script configurations.

   • [claimed-docs] “Version history - View or restore previous versions of a note.”
   • [community] “The Git plugin is great for single-device backup but not great for device sync or collaboration; a real-time collaboration plugin using CRDT…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq's evidence covers notes, queries, plugins, HTTP API, and sync, but there is no mention of any 'automation' construct (workflows, macros, agent actions) that could be versioned, reviewed, or rolled back — plugins are installed/updated/removed, not versioned as automations, and markdown files aren't presented as an automation history mechanism.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “From this dashboard, third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the [[Marketplace]], can be searched, installed, upd…”
   • [claimed-docs] “third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”

   proof ↗⚑ flag

Capture

1. researcherClip web pages, articles, and highlights from my browser straight into my notes with an official clipper or capture flow

   weight 2 · round to Obsidian
   Obsidian✓fullclaimed9/10

   Obsidian ships an official free browser extension, the Web Clipper, explicitly documented to let users highlight pages and save web content directly into their vault, covering pages, articles, and highlights as described in the story. missing for 10: independent hands-on user reports specifically confirming the Web Clipper's reliability/quality beyond the vendor docs.

   • [claimed-docs] “Obsidian Web Clipper is a free browser extension that lets you highlight pages and save web content to your vault.”

   proof ↗⚑ flag

   Logseq~partialclaimed4/10

   Logseq documents a 'Quick capture' feature via the logseq:// protocol that can be added as a browser bookmarklet or invoked from command line, letting users capture short text and links into notes (logseq-docs-11, logseq-docs-17, logseq-docs-27, logseq-docs-22). However, this is a lightweight bookmarklet, not a dedicated official browser-extension web clipper capable of capturing full articles, page content, or highlights as many competing tools offer. Missing for 10: an official browser extension/clipper product, support for capturing full article content or highlighted text with metadata, and any independent/hands-on evidence of researchers using this capture flow for web clipping.

   • [claimed-docs] “logseq://x-callback-url/quickCapture? ... Quick capture for short text and links. Can be added as a bookmark link to modern browser”
   • [claimed-docs] “logseq://x-callback-url/quickCapture? - Quick capture for short text and links.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [claimed-docs] “Quick capture for short text and links. Can be added as a bookmark link to modern browser or opened from command line shell”

   proof ↗⚑ flag

Daily notes

1. power-userI get an automatic daily note for each day, pre-filled from a template, as the default landing place for journaling and capture

   weight 3 · round drawn
   Obsidian✓fullcommunity8/10

   Obsidian's core Daily Notes plugin opens/creates a note for today's date and can be paired with the Templates core plugin to pre-fill content, directly matching the story [obsidian-docs-4][obsidian-docs-5]. Community evidence corroborates daily notes as a common power-user workflow (mixed freely with folders/Zettelkasten) [obsidian-comm-4][obsidian-comm-17]. Missing for 10: explicit first-party documentation confirming daily note as the literal 'default landing/startup' page, and independent confirmation of template auto-fill reliability at scale.

   • [claimed-docs] “Daily notes is a core plugin that opens a note based on today's date, or creates it if it doesn't exist.”
   • [claimed-docs] “Templates is a core plugin that lets you insert pre-defined snippets of text into your active note.”
   • [community] “As an outliner, Logseq is too opinionated about usage; Obsidian is less strict, allowing mixing Zettelkasten, daily notes, and folder struct…”
   • [community] “Used Obsidian for organizing and running tabletop RPG sessions with folders of monsters, encounters, and world notes; also good enough to re…”

   proof ↗⚑ flag

   Logseq✓fullclaimed8/10

   Docs confirm Logseq opens to the Journals page every time you launch it ([logseq-docs-24]), that a new dated journal page is auto-created daily at midnight ([logseq-docs-2]), and that this page serves as the equivalent of a daily-notes capture landing page ([logseq-docs-1]). Missing for 10: explicit documentation of a customizable 'journal template' pre-fill mechanism and independent/hands-on confirmation that templates apply automatically to new daily notes.

   • [claimed-docs] “Every time you open Logseq, you start on the Journals page.”
   • [claimed-docs] “Every day at midnight a new Journals page is created with that day's date, making it easy to see when you've added what information.”
   • [claimed-docs] “For people familiar with Roam Research: the Journals page in Logseq is the same as the Daily Notes Page in Roam.”

   proof ↗⚑ flag

Editor

1. power-userDefine reusable templates (with variables like date and title) and apply them when creating recurring kinds of notes

   weight 2 · round to Obsidian
   Obsidian✓fullclaimed8/10

   Obsidian ships a first-party Templates core plugin for inserting reusable text snippets, and a Daily notes core plugin that creates date-based notes automatically, together covering variable-driven, recurring note templates (date/title insertion is a documented core feature of these plugins). Missing for 10: no explicit doc snippet showing custom variable syntax beyond date/title, and no independent hands-on report confirming template variable behavior in practice.

   • [claimed-docs] “Templates is a core plugin that lets you insert pre-defined snippets of text into your active note.”
   • [claimed-docs] “Daily notes is a core plugin that opens a note based on today's date, or creates it if it doesn't exist.”

   proof ↗⚑ flag

   Logseq—none0/10

   The evidence pack contains no documentation or community mentions of Logseq's template feature (e.g. `template::` property, `/template` command, or variable substitution like date/title) — only journals, page/block references, queries, plugins, sync, and publishing are covered. Since template creation is a plausible and well-known capability for a note-taking tool, its complete absence from the evidence means this axis cannot be credited as delivered.

   ⚑ flag

2. power-userWrite and format notes with headings, callouts, tables, code blocks, and embedded media in a fast keyboard-driven editor

   weight 2 · round to Obsidian
   Obsidian~partialclaimed5/10

   Evidence confirms Obsidian is a plain-text Markdown editor with linking, templates, mobile editing toolbar, and command palette (keyboard-driven), supporting the general shape of the story, but the pack never explicitly documents callouts, tables, code-block rendering, or embedded media handling. Missing for 10: explicit documentation/citations on callout syntax, table support, code block rendering, and media embedding, plus any performance/speed benchmarking of the editor.

   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “By linking notes, you can create a network of knowledge.”
   • [claimed-docs] “Templates is a core plugin that lets you insert pre-defined snippets of text into your active note.”
   • [claimed-docs] “Mobile toolbar is a customization toolbar for editing notes.”
   • [claimed-docs] “Tabs, Command Palette, plugins,”

   proof ↗⚑ flag

   Logseq!disputedcontradicted4/10

   The evidence pack lacks any first-party documentation specifically describing headings, callouts, tables, code blocks, or media-embedding support, and instead shows only adjacent editor features (page/block references, journals) that imply block-based markdown editing. Concrete hands-on reports contradict the 'fast, keyboard-driven' claim: pasting multi-paragraph text broke formatting into unwanted lists and even crashed on longer pastes, and users report severe UI lag once graphs grow, undermining the 'fast' editing experience for power users. Missing for 10: explicit docs on headings/callouts/tables/code-block syntax, embedded media handling, and independent confirmation that these specific formatting features perform well at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “I used Logseq for a while but the big problem I had with it is how strongly it is focused on bullet points. Posting long form text is cumber…”
   • [community] “Admittedly poor performance has been my primary gripe in the 7mos I've been using LogSeq on a near-daily basis... I'd gladly pay for a subsc…”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

Migration

1. switcherExport my entire knowledge base at any time in open formats, so leaving is as easy as arriving

   weight 2 · round to Obsidian
   Obsidian✓fullcommunity9/10

   Obsidian stores all notes as local, non-proprietary plain-text Markdown files (not a proprietary database or cloud lock-in), so a user's entire vault is always exportable/portable by simply copying the folder, and this is explicitly marketed as a future-proofing/anti-lock-in feature ('apps come and go, but your data should last'). Community testimonials corroborate this in practice (users migrated to/from Roam, Notion, Google Docs citing plain-text ownership as the reason switching was easy). Missing for 10: no independent hands-on verification of a bulk 'export' action for non-Markdown assets (attachments, plugin data) or edge cases in migration fidelity.

   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [community] “Moved from Google Docs to Obsidian for de-Googling; notes stored only locally and via storage sync, files are just text so notes can outlive…”
   • [community] “Migrated from Roam to Obsidian and it's really awesome - ownership of files, constant updates with new features and bug fixes, and a really …”

   proof ↗⚑ flag

   Logseq!disputedcontradicted5/10

   Logseq documents a genuine multi-format Export feature (Markdown, HTML, OPML, JSON, EDN, PNG) and historically stores data as local plain Markdown files, supporting easy exit at any time [logseq-docs-8]. However, hands-on community reports contradict the 'open, portable' framing: exported Markdown adds non-standard formatting that breaks compatibility with other Markdown apps like Obsidian [logseq-comm-19], and the newer Logseq DB version reportedly moves away from storing everything as plain markdown files, alarming users who relied on that for portability [logseq-comm-14, logseq-comm-9]. Missing for 10: independent verification that exports are lossless/round-trippable, clarity on whether DB-version graphs can still export to plain markdown, and confirmation the export covers all data (assets, whiteboards, plugins config).

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”
   • [community] “Yeah I felt the same about the decision when they decided to move to database structure. If it had this structure from the start it could've…”

   proof ↗⚑ flag

2. switcherImport my existing notes from Notion, Evernote, Roam, or plain Markdown with structure, links, and attachments preserved

   weight 3 · round to Obsidian
   Obsidian✓fullcommunity8/10

   Obsidian ships dedicated first-party importers for Notion, Evernote, Roam-style Markdown, and Airtable/OneNote (obsidian-docs-1, 24, 29, 30), converting content to durable local Markdown files with links/attachments/structure preserved, and Notion databases even convert to Bases. Community evidence (obsidian-comm-20) confirms a real-world Roam→Obsidian migration went well. Missing for 10: no independent hands-on verification of attachment/link fidelity across all four sources (Notion, Evernote, Roam, plain Markdown) in one report, and no detail on edge-case fidelity issues during import.

   • [claimed-docs] “Obsidian lets you easily migrate your data from Notion using the Importer plugin.”
   • [claimed-docs] “Obsidian lets you easily migrate your data from Notion using the Importer plugin. This converts your Notion workspace to durable Markdown fi…”
   • [claimed-docs] “Notion account (recommended) connects directly to your workspace and lets you preserve Databases and formulas which are converted to Bases.”
   • [claimed-docs] “Import from Notion|Notion - Import from Airtable|Airtable - Import from Microsoft OneNote|Microsoft OneNote - Import from Evernote|Evernote”
   • [community] “Migrated from Roam to Obsidian and it's really awesome - ownership of files, constant updates with new features and bug fixes, and a really …”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”

   proof ↗⚑ flag

   Logseq—none0/10

   The evidence pack documents Logseq's export formats and journal/page structure comparisons to Roam, but contains no mention of an import feature for Notion, Evernote, Roam exports, or Markdown migration with links/attachments preserved. Community comments mention switching from Roam via GitHub sync, not a structured import tool. Since import tooling is a plausible feature for a PKM app, absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [claimed-docs] “For people familiar with Roam Research: the Journals page in Logseq is the same as the Daily Notes Page in Roam.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”

   proof ↗⚑ flag

Graph

1. researcherExplore my knowledge base as an interactive graph of notes and connections, filtered to what I care about

   weight 1 · round to Obsidian
   Obsidian✓fullcommunity8/10

   Graph view is a documented core plugin that visualizes note relationships built from internal links, and Obsidian's linking system explicitly creates a 'network of knowledge' that the graph renders; Graph view also supports filters (though filtering specifics aren't detailed in this pack). Community evidence confirms users actively rely on the linking/graph model for organizing knowledge (e.g., RPG notes, dev notes). Missing for 10: no evidence of advanced graph filtering UI details (tags/colors/query filters) or independent hands-on praise/critique specifically of graph view's filtering usability.

   • [claimed-docs] “Graph view is a core plugin that lets you visualize the relationships between the notes in your vault.”
   • [claimed-docs] “By linking notes, you can create a network of knowledge.”
   • [community] “Used Obsidian for organizing and running tabletop RPG sessions with folders of monsters, encounters, and world notes; also good enough to re…”

   proof ↗⚑ flag

   Logseq~partialcommunity5/10

   Logseq's documented linking primitives — page/block references ([[ ]], (( ))) and simple queries ({{query}}) — provide the backbone for connecting and filtering notes, and the Whiteboard feature offers a spatial canvas with connectors for arranging knowledge visually, but no evidence explicitly documents a dedicated interactive 'graph view' with node-link visualization or filtering controls. Community reports also note serious performance degradation ('indexing and general responsiveness slows down massively once you have a few million words') which would hamper exploring a large graph. missing for 10: explicit documentation of the graph-view visualization UI and its filtering options, and independent confirmation that graph exploration performs well at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Put thoughts from your knowledge base as well as new ones next to each other on a spatial canvas together with shapes, drawings, website emb…”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

Links

1. researcherLink notes with [[wiki-style]] links and see every backlink and unlinked mention of a note in context

   weight 3 · round to Obsidian
   Obsidian✓fullcommunity8/10

   Obsidian's core feature set is wiki-style [[linking]] and a network of knowledge (obsidian-docs-18), backed by Graph view for visualizing note relationships (obsidian-docs-3), and this is corroborated by independent community usage reports praising Obsidian's linking/organization model (obsidian-comm-17, obsidian-comm-20). Missing for 10: explicit documentation snippet describing the 'unlinked mentions' panel/backlinks pane in context (only inferred from linking/graph docs, not directly quoted) and no independent hands-on confirmation of backlink-in-context UI specifically.

   • [claimed-docs] “By linking notes, you can create a network of knowledge.”
   • [claimed-docs] “Graph view is a core plugin that lets you visualize the relationships between the notes in your vault.”
   • [community] “Used Obsidian for organizing and running tabletop RPG sessions with folders of monsters, encounters, and world notes; also good enough to re…”
   • [community] “Migrated from Roam to Obsidian and it's really awesome - ownership of files, constant updates with new features and bug fixes, and a really …”

   proof ↗⚑ flag

   Logseq~partialcommunity7/10

   Docs confirm core wiki-linking mechanics ([[ ]] page references, (( )) block references, journals as the default landing page) and queries for surfacing related content, which underpins backlinking functionality core to Logseq's outliner design. However, the evidence pack never explicitly documents a dedicated 'Linked References' or 'unlinked references' UI panel showing backlinks-in-context, which is a well-known Logseq feature but unevidenced here; community notes instead focus on performance/sync issues rather than confirming backlink display quality. Missing for 10: explicit docs/evidence on the Linked References and Unlinked References panels, independent hands-on confirmation of backlink context display working well at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Every time you open Logseq, you start on the Journals page.”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

2. power-userReference or transclude an individual block or section of one note inside another and have it stay in sync

   weight 2 · round to Logseq
   Obsidian—none0/10

   The evidence pack only shows generic internal linking ('By linking notes, you can create a network of knowledge' — obsidian-docs-18) and graph view for whole-note relationships, but contains no documentation or community evidence of block/section-level embedding (transclusion) syntax or behavior. Missing for 10: any docs on block references (^blockid), section embeds, or confirmation that embedded content stays live-synced with the source note.

   • [claimed-docs] “By linking notes, you can create a network of knowledge.”

   proof ↗⚑ flag

   Logseq✓fullclaimed8/10

   Logseq's block reference syntax `(())` embeds/transcludes an individual block from any page into another, and page references `[[]]` do the same at page level; since Logseq's block-based architecture keeps a single canonical block that references simply render/link to, edits propagate automatically, keeping transclusions in sync. Docs explicitly describe both block and page referencing as core features. Missing for 10: no explicit doc quote confirming live-sync behavior on edit (implied by architecture, not directly demonstrated) and no independent hands-on confirmation of transclusion sync specifically.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Blocks that have a page as a parent i.e. usually top-level blocks can be converted to a page and back to a block easily. To convert this blo…”

   proof ↗⚑ flag

Ownership

1. power-userMy notes live in local files or a local-first store that I own and can read without the app, and everything keeps working fully offline

   weight 3 · round to Obsidian
   Obsidian✓fullcommunity9/10

   Obsidian's core design stores notes as plain-text Markdown files locally in a user-owned vault, explicitly marketed for offline use and future-proofing/app independence, corroborated by independent community reports of migrating away from cloud apps because files are local text that outlive the app. Minor caveat is Canvas's JSON format (still local, but less human-readable than Markdown), and mobile has a save-timing quirk under sync; missing for 10: independent long-term audit of full offline reliability across all core plugins and confirmation Canvas/Bases data remain equally portable as plain Markdown.

   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [community] “Moved from Google Docs to Obsidian for de-Googling; notes stored only locally and via storage sync, files are just text so notes can outlive…”
   • [community] “Obsidian Canvas uses a new JSON-based file format, open-sourced under MIT license; canvas files remain local and still link to your own futu…”
   • [community] “The Obsidian Android app does not save files to storage until the note unloads, which can break things if you sync/pull mid-edit, sometimes …”

   proof ↗⚑ flag

   Logseq~partialcommunity6/10

   Logseq's classic (file) mode stores notes as plain Markdown on local disk, exports to multiple open formats, and only publishes pages explicitly (docs-8, docs-7, docs-23), supporting the 'own your files, work offline' story; community users confirm they read/back up the raw Markdown files themselves (comm-1, comm-19, comm-7). However, the newer DB-based version raises real doubts: a user explicitly states 'I can no longer keep all my data as markdown files' with the new format (comm-14), and others cite years of stagnation, sync bugs, and performance/data-loss concerns (comm-3, comm-5, comm-6, comm-8) that undercut confidence in durable, app-independent local ownership going forward. missing for 10: clear first-party confirmation that the DB version still exposes plain-text/local files, independent verification of offline reliability at scale, and resolution of the data-loss/performance complaints.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [claimed-docs] “By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “I use Logseq personally and for work almost daily since a year ago or so. It's pretty nice and the 'least bad' PKM platform I'm aware of (no…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”
   • [community] “I had two main problems with LogSeq: 1. Not designed from the ground-up to prevent data loss. Has had data-loss issues in the past.”
   • [community] “Admittedly poor performance has been my primary gripe in the 7mos I've been using LogSeq on a near-daily basis... I'd gladly pay for a subsc…”

   proof ↗⚑ flag

2. researcherMy notes are stored or exportable in open, documented formats (Markdown, JSON) so my archive outlives the vendor

   weight 2 · round to Obsidian
   Obsidian✓fullcommunity9/10

   Obsidian core storage is plain-text Markdown files on local disk with no proprietary lock-in, explicitly marketed as future-proof so notes 'outlive the app,' and this is corroborated by independent user reports of migrating away and still having usable text files. missing for 10: independent long-term archival/format-stability audit and clarity on the newer Canvas JSON format's durability (community notes flag it as less readable than Markdown, a minor caveat).

   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [community] “Moved from Google Docs to Obsidian for de-Googling; notes stored only locally and via storage sync, files are just text so notes can outlive…”
   • [community] “Obsidian is less opinionated on the file format and folders, making it more future-proof than Logseq, though Logseq's sync is too asynchrono…”
   • [community] “Obsidian Canvas uses a new JSON-based file format, open-sourced under MIT license; canvas files remain local and still link to your own futu…”
   • [community] “This looks like Obsidian's first move away from markdown - the .canvas JSON files are readable but not as readable as markdown; hope this is…”

   proof ↗⚑ flag

   Logseq!disputedcontradicted5/10

   Logseq's docs confirm export to open, documented formats (Markdown, JSON, EDN, OPML) and its journal-based local storage model, supporting archive portability (logseq-docs-8). However, hands-on community reports contradict full open-format durability: users note the generated Markdown isn't standard-compliant/interoperable with other tools due to extra indentation (logseq-comm-19), and the newer DB-based version reportedly abandons plain Markdown as the storage format entirely, forcing users into a proprietary DB structure (logseq-comm-14). Missing for 10: confirmation that the current/default file storage (not just export) remains plain Markdown across versions, and independent verification that exported files are lossless/interoperable.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”

   proof ↗⚑ flag

Self host

1. developerRun the whole system without the vendor's cloud — local-only mode or a self-hosted sync backend I operate myself

   weight 2 · round to Logseq
   Obsidian~partialcommunity7/10

   Obsidian is fundamentally local-first: notes are plain Markdown files stored on-device, fully usable offline with no vendor cloud dependency (obsidian-docs-2, obsidian-docs-20, obsidian-docs-23), and users can sync via Dropbox, iCloud, OneDrive, or Git instead of Obsidian's paid Sync service (obsidian-docs-19), confirmed by a community user who runs it fully local plus storage sync (obsidian-comm-19). However, self-hosting a sync backend is imperfect in practice — community reports note the Git plugin works for single-device backup but is 'not great for device sync or collaboration,' requiring third-party CRDT plugins to fill the gap (obsidian-comm-8). Missing for 10: an officially documented/first-party self-hosted sync backend with real-time multi-device guarantees (vs. community workarounds), and confirmation that Git/cloud-drive sync avoids conflict issues.

   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [claimed-docs] “Obsidian syncs with Obsidian Sync, Dropbox, iCloud, OneDrive, Git, and many other third-party services.”
   • [community] “Moved from Google Docs to Obsidian for de-Googling; notes stored only locally and via storage sync, files are just text so notes can outlive…”
   • [community] “The Git plugin is great for single-device backup but not great for device sync or collaboration; a real-time collaboration plugin using CRDT…”

   proof ↗⚑ flag

   Logseq✓fullcommunity7/10

   Logseq stores data as local Markdown/EDN files by default with no cloud requirement, and is documented as 'privacy-first' — users confirm they run it fully local or pair it with self-managed sync like GitHub instead of vendor cloud. The official Logseq Sync exists only as an optional paid vendor-hosted add-on, not a self-hosted backend, and one user explicitly notes there's no built-in way to self-host it as a server despite an open feature request. missing for 10: an officially supported self-hosted sync backend (only vendor-cloud Sync or DIY git workflows exist), and independent verification that local mode has no offline degradation.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “I use Logseq personally and for work almost daily since a year ago or so. It's pretty nice and the 'least bad' PKM platform I'm aware of (no…”
   • [community] “I know Logseq is intended as an offline-first solution, but I really wish I could self-host it as a website and have all notes saved on my s…”

   proof ↗⚑ flag

Mobile

1. power-userFull-featured iOS and Android apps give me my whole knowledge base — capture, search, and linking — not a stripped-down companion

   weight 2 · round to Obsidian
   Obsidian~partialcommunity6/10

   Docs confirm the mobile app supports tabs, command palette, and full plugin support (docs-34) plus a customizable editing toolar (docs-14/25), indicating feature parity with desktop rather than a stripped companion, and the same Markdown vault format underlies both platforms enabling linking (docs-18, docs-20). However, community evidence surfaces a concrete reliability issue specific to the Android app (files not saved to storage until note unloads, causing lost content on sync) and general dissatisfaction with mobile UX/Electron design relative to native apps, undercutting a fully polished power-user experience. Missing for 10: explicit documentation of mobile search functionality, mobile graph view parity, and independent confirmation the Android save bug has been resolved.

   • [claimed-docs] “Tabs, Command Palette, plugins,”
   • [claimed-docs] “Mobile toolbar is a customization toolbar for editing notes.”
   • [claimed-docs] “Mobile toolbar is a customization toolbar for editing notes. When editing a note, you will notice a row of icons at the bottom of the app.”
   • [claimed-docs] “By linking notes, you can create a network of knowledge.”
   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [community] “The Obsidian Android app does not save files to storage until the note unloads, which can break things if you sync/pull mid-edit, sometimes …”
   • [community] “I dislike the aesthetics and wouldn't use Obsidian because of Electron; spoiled by native note apps like Bear and Noteplan on macOS with nic…”

   proof ↗⚑ flag

   Logseq—none0/10

   Evidence confirms Logseq has mobile apps (iOS/Android sync up to 10 graphs, end-to-end encrypted) but contains no evidence about the actual feature set of the mobile apps themselves — no mention of whether search, linking, queries, or full editing capabilities are present on mobile versus a stripped-down capture-only experience. Community commentary focuses on desktop performance/sync bugs, not mobile app completeness.

   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Obsidian
   Obsidian~partialprobed4/10

   Obsidian exposes some programmatic surfaces — the Obsidian URI protocol for triggering actions like opening/creating notes, and a plugin API (Vault interface) for reading/writing files — but these fall short of full UI parity. There is no official CLI or vendor-provided REST/MCP API; the probe explicitly confirms no official CLI or MCP server exists, with third-party community plugins filling that gap instead. missing for 10: comprehensive first-party API/CLI covering all UI actions, official REST or MCP server, evidence of parity for non-file operations (e.g., graph view, canvas, settings) via API.

   • [claimed-docs] “Obsidian URI is a custom URI protocol supported by Obsidian that lets you trigger various actions, such as opening a note or creating a note…”
   • [github] “Vault, the interface that lets you interact with files and folders in the vault.”
   • [github] “`Vault`, the interface that lets you interact with files and folders in the vault.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq!disputedcontradicted4/10

   Logseq docs describe a local HTTP APIs server for external access to the graph, a community-documented plugin API, and a logseq:// protocol for third-party invocation, suggesting programmatic access beyond the UI (logseq-docs-6, logseq-docs-21, logseq-docs-12, logseq-docs-22). However, there's no documentation showing this API surface covers 'everything' the UI can do (queries, whiteboards, publishing, sync are UI-first features with no documented API equivalents), and a hands-on user reports that after the move to the new DB version, 'Not being able to use Claude or codex anymore to write or update pages is a real deal breaker' — a concrete failure of AI-driven read/write parity (logseq-comm-11). missing for 10: full API coverage of queries/whiteboard/publish/sync, evidence of AI tools reliably reading+writing via API in the current version, independent confirmation the HTTP API matches UI capability breadth.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Obsidian
   Obsidian✓fullcommunity9/10

   Obsidian stores all data as local plain-text Markdown files with no proprietary lock-in, explicitly marketed as future-proof so users 'can use Obsidian offline and switch to another app easily,' and this is corroborated by independent community accounts of notes outliving the app and easy migration away. Even newer formats like Canvas are open JSON under MIT license, reinforcing the open-export/leave-anytime story. Missing for 10: no independent audit of full fidelity export for all plugin-generated data (e.g., Bases, Sync metadata) beyond core notes.

   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [community] “Moved from Google Docs to Obsidian for de-Googling; notes stored only locally and via storage sync, files are just text so notes can outlive…”
   • [community] “Obsidian Canvas uses a new JSON-based file format, open-sourced under MIT license; canvas files remain local and still link to your own futu…”

   proof ↗⚑ flag

   Logseq~partialcommunity6/10

   Logseq's docs describe a native local-markdown storage model plus an explicit Export feature covering text, HTML, OPML, PNG, EDN, JSON and standard Markdown, which supports data portability and offline 'leave anytime' use (logseq-docs-8). However, community reports note markdown output isn't cleanly interoperable with other markdown apps due to formatting quirks (logseq-comm-19), and the newer DB-based version is criticized for moving away from plain markdown files as the source of truth, undermining the 'leave in open formats' guarantee for that version (logseq-comm-14). Missing for 10: independent verification that exported formats round-trip cleanly into other tools, and clarity on export fidelity in the new DB architecture.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Logseq
   Obsidian—none0/10

   Obsidian is explicitly noted as closed-source (obsidian-comm-12), and no evidence pack item shows any open-license source availability; only the Canvas file format is MIT-licensed (obsidian-comm-14), not the app's source code itself.

   • [community] “Obsidian being closed-source makes it harder to verify their security model compared to note-taking systems where all plugin code is visible…”
   • [community] “Obsidian Canvas uses a new JSON-based file format, open-sourced under MIT license; canvas files remain local and still link to your own futu…”

   proof ↗⚑ flag

   Logseq✓fullcommunity8/10

   Logseq is explicitly described as "open-source" (logseq-docs-23), and its docs, plugin ecosystem, and marketplace are hosted publicly on GitHub, implying the source is inspectable and openly licensed; community comments corroborate "local data and source availability are important factors" (logseq-comm-7). missing for 10: explicit citation of the actual license name/terms (e.g., AGPL) and any independent audit or discussion of license compliance.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “I use Logseq personally and for work almost daily since a year ago or so. It's pretty nice and the 'least bad' PKM platform I'm aware of (no…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Logseq
   Obsidian—none0/10

   Obsidian's core app is closed-source (obsidian-comm-12) and Sync/Publish are proprietary paid cloud services with no documented self-hosted server alternative; the only 'local' aspect is that vault files live on-device, which is not the same as self-hosting the product's infrastructure. No evidence of an official self-hostable sync/publish server or open-source core.

   • [community] “Obsidian being closed-source makes it harder to verify their security model compared to note-taking systems where all plugin code is visible…”
   • [claimed-docs] “Obsidian Sync encrypts your remote vault and all communication with Obsidian's servers.”
   • [claimed-docs] “Obsidian Publish is a cloud-based hosting service that lets you publish your notes as a wiki, knowledge base, documentation, or digital gard…”
   • [claimed-docs] “Obsidian Sync is an add-on service that allows you to privately sync your notes across devices.”

   proof ↗⚑ flag

   Logseq~partialcommunity5/10

   Logseq is open-source and stores data locally as markdown files (docs-23), and offers a local HTTP API for accessing your own graph (logseq-docs-6, logseq-docs-21), which supports a 'run entirely on your own machine' notion of self-hosting. However, there is no official self-hosted server/web deployment: a community member explicitly wished they could self-host Logseq as a website with notes on their own server, noting this remains an open, unresolved GitHub feature request among 1.8k open issues (logseq-comm-20), and official Sync is a paid, vendor-hosted cloud service rather than a self-hostable component (logseq-docs-10, logseq-comm-2). Missing for 10: an official self-hosted server/backend deployment option, first-party documentation for hosting the app as a service, and confirmation that the open feature request has been resolved.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [community] “I know Logseq is intended as an offline-first solution, but I really wish I could self-host it as a website and have all notes saved on my s…”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”

   proof ↗⚑ flag

Metadata

1. power-userAttach typed properties and tags to notes and use them consistently for organization and retrieval

   weight 2 · round to Logseq
   Obsidian~partialcommunity5/10

   Obsidian's Bases core plugin (database-like views of notes) and internal linking support the kind of structured organization/retrieval a power-user would want, and community evidence confirms Bases is used as a fast, if less comprehensive, alternative to Dataview for querying notes by metadata. However, the evidence pack never explicitly documents Obsidian's Properties (YAML frontmatter with typed fields) or tag system, nor how tags/properties are used consistently for retrieval. Missing for 10: explicit docs on typed Properties/frontmatter, dedicated tag-pane/tag-search documentation, and hands-on confirmation that typed properties work reliably for retrieval across a vault.

   • [claimed-docs] “Bases is a core plugin that lets you create database-like views of your notes.”
   • [community] “Bases is essentially a 90% replacement for the Dataview plugin, much faster and more responsive, though not yet as comprehensive.”
   • [claimed-docs] “By linking notes, you can create a network of knowledge.”

   proof ↗⚑ flag

   Logseq~partialclaimed6/10

   Docs confirm block/page tagging (`#Page`) and properties (e.g., `publish:: true`), plus page/block references and query blocks (`{{query}}`) that can retrieve content by tags/properties. However, the evidence pack lacks dedicated documentation on Logseq's typed-property system (property schemas, value types, advanced query filtering by property) and no independent confirmation of consistent power-user workflows using properties for retrieval. Missing for 10: explicit docs on property types/schema, advanced query examples filtering by properties, and hands-on validation of consistent tagging/property retrieval at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Blocks that have a page as a parent i.e. usually top-level blocks can be converted to a page and back to a block easily. To convert this blo…”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”

   proof ↗⚑ flag

Queries

1. power-userQuery my notes by their structured properties and render live database-style views (tables, boards, lists) from those queries

   weight 3 · round to Obsidian
   Obsidian~partialcommunity7/10

   Obsidian's core 'Bases' plugin is documented as letting users 'create database-like views of your notes' from structured properties, and community evidence corroborates it as a real, working feature comparable to the popular Dataview plugin, confirming table/board-style query views exist. However, community feedback notes Bases is 'not yet as comprehensive' as Dataview and lacks its imperative dataviewjs scripting for custom dynamic rendering, so some advanced query/view flexibility power-users expect is limited. Missing for 10: detailed first-party documentation of specific view types (table/board/list) and their query syntax, plus independent confirmation these views match the full breadth of 'live database' functionality claimed.

   • [claimed-docs] “Bases is a core plugin that lets you create database-like views of your notes.”
   • [community] “Bases is essentially a 90% replacement for the Dataview plugin, much faster and more responsive, though not yet as comprehensive.”
   • [community] “Dataview's dataviewjs mode lets you write custom imperative JavaScript to dynamically render content in notes, a capability Bases (queries-t…”

   proof ↗⚑ flag

   Logseq~partialclaimed3/10

   Docs confirm a core query feature ({{query}} / /query) for asking questions of the knowledge base, and structured page/block references exist, but the pack never documents property-based structured queries or dynamic table/board/list rendering views (advanced query mode, query views like {{table}}) that power users need. missing for 10: documentation of advanced/structured-property queries, table/board/list view rendering from queries, and any hands-on confirmation of these views working.

   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Blocks that have a page as a parent i.e. usually top-level blocks can be converted to a page and back to a block easily. To convert this blo…”

   proof ↗⚑ flag

Search

1. researcherInstantly search all my notes with full-text search plus filters on tags, properties, and paths — including offline

   weight 3 · round to Obsidian
   Obsidian~partialclaimed4/10

   Evidence confirms offline-first, local plain-text storage (docs-2, docs-20, docs-23) and Bases as a database-like filtering view on note properties (docs-6), plus tag-based linking (docs-18), which together imply some filterable retrieval. However, the pack contains no explicit documentation of Obsidian's full-text search engine, search operators for tags/paths, or performance claims about instant search across large vaults. Missing for 10: dedicated full-text search docs, tag/path/property query syntax evidence, independent hands-on confirmation of search speed/completeness.

   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [claimed-docs] “Bases is a core plugin that lets you create database-like views of your notes.”
   • [claimed-docs] “By linking notes, you can create a network of knowledge.”
   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”

   proof ↗⚑ flag

   Logseq!disputedcontradicted5/10

   Logseq's docs describe a query system ({{query}}) for searching the knowledge base and page/block references and tags for organization (logseq-docs-4, -16, -19, -3), and it markets itself as privacy-first/local/offline (logseq-docs-23). However, hands-on community reports directly contradict the 'instant' part of the story: users report that 'indexing and general responsiveness slows down massively once you have a few million words stored' and describe persistent lag navigating pages even after months of daily use (logseq-comm-5, logseq-comm-6). Missing for 10: explicit documentation of a dedicated full-text search UI with tag/property/path filters (only generic query syntax is shown), and no independent benchmark confirming fast search at scale to offset the reported slowdowns.

   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “Admittedly poor performance has been my primary gripe in the 7mos I've been using LogSeq on a near-daily basis... I'd gladly pay for a subsc…”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

Automation hooks

1. developerDrive the app from outside — create or open notes via a URI scheme, deep links, or a local endpoint — to wire it into my scripts and workflows

   weight 2 · round to Logseq
   Obsidian~partialprobed6/10

   Obsidian documents a native URI protocol for triggering actions like opening or creating notes, which directly supports scripting/automation via deep links (obsidian-docs-8). However, there is no first-party local HTTP endpoint or official CLI evidenced — the probe explicitly confirms Obsidian ships no official CLI or vendor MCP server, leaving any local-endpoint automation to third-party community plugins not covered in this pack. Missing for 10: vendor-documented local REST/HTTP endpoint, independent hands-on examples of URI-driven workflows in real automation pipelines.

   • [claimed-docs] “Obsidian URI is a custom URI protocol supported by Obsidian that lets you trigger various actions, such as opening a note or creating a note…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq✓fullprobed8/10

   Logseq documents both a URI scheme (logseq://x-callback-url/quickCapture) that can be triggered from browser bookmarks or command line to capture/open notes, and a local HTTP APIs server enabling authorized external programmatic access to the graph — directly matching the story's ask for deep links and a local endpoint for scripting. Missing for 10: independent/hands-on confirmation of the HTTP API's request/response schema or third-party integration examples, and no evidence of a broader public REST API spec (openapi probes returned 404).

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “logseq://x-callback-url/quickCapture? ... Quick capture for short text and links. Can be added as a bookmark link to modern browser”
   • [claimed-docs] “logseq://x-callback-url/quickCapture? - Quick capture for short text and links.”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [claimed-docs] “Quick capture for short text and links. Can be added as a bookmark link to modern browser or opened from command line shell”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

Plugins

1. power-userBrowse and install from a large catalog of community plugins/extensions to add features the core app doesn't ship

   weight 3 · round to Obsidian
   Obsidian✓fullprobed9/10

   Obsidian's own docs describe a dedicated Community Plugins system for extending functionality (obsidian-docs-7, obsidian-docs-31, obsidian-docs-33), and a runtime probe confirms the vendor's official plugin registry lists 7,275 published community plugins, verifying the catalog's scale beyond marketing claims. Community discussion corroborates real-world reliance on specific popular plugins (Dataview, Git, Text-Generator) as everyday power-user tools, and docs also cover the security model (Restricted Mode) governing plugin installation. Missing for 10: independent step-by-step hands-on installation walkthrough/review of the browse-and-install UI flow itself.

   • [claimed-docs] “Use plugins to adapt Obsidian to fit your specific needs, such as support for additional file formats or integrating with a third-party serv…”
   • [claimed-docs] “Learn how to extend Obsidian with plugins built by the community.”
   • [claimed-docs] “Plugins let you extend Obsidian with your own features to create a custom note-taking experience.”
   • [claimed-docs] “By default, Obsidian runs in Restricted Mode to prevent third-party code execution.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”
   • [community] “Bases is essentially a 90% replacement for the Dataview plugin, much faster and more responsive, though not yet as comprehensive.”
   • [community] “The Git plugin is great for single-device backup but not great for device sync or collaboration; a real-time collaboration plugin using CRDT…”

   proof ↗⚑ flag

   Logseq✓fullprobed8/10

   Logseq ships an in-app Marketplace dashboard to search/install/update/remove third-party plugins, plus a documented plugin API and community docs site, and a runtime probe confirms 617 published plugin packages in the official registry. Community commentary notes Logseq's ecosystem is smaller/less mature than Obsidian's, but doesn't dispute that a working plugin catalog exists. Missing for 10: independent hands-on account of browsing/installing a plugin, and quantification of catalog quality/curation vs. just count.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “From this dashboard, third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the [[Marketplace]], can be searched, installed, upd…”
   • [claimed-docs] “Click on `Load unpacked plugin` to load plugins that are distributed outside the marketplace.”
   • [claimed-docs] “third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [community] “Yeah I felt the same about the decision when they decided to move to database structure. If it had this structure from the start it could've…”

   proof ↗⚑ flag

2. developerBuild my own plugins against a documented extension API/SDK with samples and developer docs

   weight 2 · round to Obsidian
   Obsidian✓fullprobed8/10

   Obsidian has a dedicated developer docs site with a 'Build a plugin' tutorial that compiles a sample plugin from source, an official API repository (obsidian-api) documenting interfaces like Vault, and TypeScript-based plugin development guidance; the registry-verified 7,275 community plugins confirm the extension API is actively used at scale. missing for 10: independent hands-on review of doc quality/completeness, and no official CLI/scaffolding tool beyond the sample build tutorial.

   • [claimed-docs] “In this tutorial, you'll compile a sample plugin from source code and load it into Obsidian.”
   • [claimed-docs] “Build plugins to extend the existing functionality in Obsidian using TypeScript.”
   • [claimed-docs] “you'll compile a sample plugin from source code and load it into Obsidian.”
   • [claimed-docs] “Plugins let you extend Obsidian with your own features to create a custom note-taking experience.”
   • [github] “Vault, the interface that lets you interact with files and folders in the vault.”
   • [github] “`Vault`, the interface that lets you interact with files and folders in the vault.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the vendor's own community-plugin registry (obsidianmd/obsidian-releases community-plugins.json) counte…”

   proof ↗⚑ flag

   Logseq~partialprobed6/10

   Logseq has a documented plugin API (plugins-doc.logseq.com, described as community-driven documentation for the SDK) plus in-app tooling for loading unpacked/dev plugins and a marketplace with 617 published packages showing a real developer ecosystem. However, the core API docs are explicitly community-maintained rather than official first-party reference docs with samples, and probes show no llms.txt/openapi spec, suggesting thinner formal SDK documentation than top competitors. Missing for 10: official first-party API reference with code samples/tutorials, and machine-readable API spec (openapi/llms.txt) confirming documented completeness.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Click on `Load unpacked plugin` to load plugins that are distributed outside the marketplace.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Logseq
   Obsidian~partialclaimed5/10

   Obsidian's core value proposition is local-first storage — notes are plain-text Markdown files kept on the user's own device, giving inherent control over data location without relying on a vendor cloud (obsidian-docs-2, obsidian-docs-20, obsidian-docs-23). However, for users who opt into Obsidian Sync, there is no documented ability to choose a specific storage region/jurisdiction for the encrypted cloud vault. missing for 10: explicit region/residency selection for Obsidian Sync servers, any multi-region hosting options, independent confirmation of server locations.

   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [claimed-docs] “Obsidian Sync is an add-on service that allows you to privately sync your notes across devices.”
   • [claimed-docs] “Obsidian Sync encrypts your remote vault and all communication with Obsidian's servers.”

   proof ↗⚑ flag

   Logseq~partialcommunity6/10

   Logseq stores data as local markdown/EDN files by default, giving users full control over where their data physically resides (their own device, self-hosted git repos, etc.), and its optional Sync service is end-to-end encrypted, which aligns with a privacy-first, local-first posture. However, there is no documented feature letting users select a specific data-center region for the Sync service, and community reports note sync reliability issues and no self-hosting option for a hosted graph. Missing for 10: explicit region/residency selection controls for the cloud Sync product, first-party documentation on where Sync servers are physically located, and confirmation that self-hosting/regional choice is officially supported rather than just achievable via local storage or third-party git.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”
   • [community] “I know Logseq is intended as an offline-first solution, but I really wish I could self-host it as a website and have all notes saved on my s…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Obsidian
   Obsidian~partialcommunity6/10

   Obsidian's core architecture (local plain-text Markdown storage, optional end-to-end encrypted Sync where 'no one — not even the Obsidian team — can access your notes') strongly implies user data isn't harvested for AI training since it never leaves the user's control by default. However, there is no explicit vendor statement or policy addressing AI-training use of data, and Obsidian's own docs admit community plugins have unrestricted filesystem/network access with no sandboxing, meaning third-party plugins (e.g. AI plugins) could still exfiltrate data outside Obsidian's control. Missing for 10: an explicit anti-AI-training data policy statement, and any assurance/controls over what community AI plugins do with vault data.

   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “End-to-end encryption (default) offers the strongest security... This guarantees that no one — not even the Obsidian team — can access your …”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [community] “Confirmed via Obsidian's own docs: there is no sandboxing at all for community plugins - every plugin has full access to your computer's fil…”
   • [community] “Obsidian being closed-source makes it harder to verify their security model compared to note-taking systems where all plugin code is visible…”

   proof ↗⚑ flag

   Logseq~partialcommunity3/10

   Logseq positions itself as a 'privacy-first, open-source knowledge base' with local-first storage and end-to-end encrypted sync, which implies user data isn't funneled to a cloud AI training pipeline by default, but no evidence explicitly states a policy on AI model training use of user data. Missing for 10: explicit statement addressing AI training data usage, any opt-out/consent controls for AI features, and confirmation that plugins or integrations (e.g., Claude/Codex mentioned in community posts) don't send data to third-party AI services.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Obsidian
   Obsidian~partialclaimed6/10

   Obsidian's local-first, plain-text vault model (obsidian-docs-20, obsidian-docs-23, obsidian-docs-2) gives users full control to delete or retain data simply by managing files on disk, and Sync is end-to-end encrypted with version history to restore/rollback (obsidian-docs-21, obsidian-docs-28). However there's no explicit documentation on server-side retention windows, deletion guarantees for Sync/Publish-hosted data, or export/purge tooling tailored to AI-native automation. Missing for 10: explicit Sync/Publish data-retention or deletion policy, documented data-export/erasure API, and any AI-specific retention controls.

   • [claimed-docs] “Obsidian stores your notes as Markdown-formatted plain text files in a vault.”
   • [claimed-docs] “Apps come and go, but your data should last. Obsidian uses non-proprietary plain text Markdown files stored locally on your device.”
   • [claimed-docs] “Obsidian uses non-proprietary plain text Markdown files stored locally on your device. You have total control over your data, which means yo…”
   • [claimed-docs] “End-to-end encryption (default) offers the strongest security... This guarantees that no one — not even the Obsidian team — can access your …”
   • [claimed-docs] “Version history - View or restore previous versions of a note.”

   proof ↗⚑ flag

   Logseq~partialclaimed5/10

   Logseq stores graphs as local Markdown files and is marketed as 'privacy-first,' implying users can delete or retain data simply by managing local files, and Export lets users extract data in multiple formats; optional Sync is end-to-end encrypted. However, there is no explicit documentation on deletion mechanics for synced/cloud data, data-retention policies, or how to purge synced copies across devices. Missing for 10: documented data-retention/deletion policy, explicit instructions for deleting synced cloud data, and independent verification that deletion is complete and irreversible.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Obsidian—none0/10

   The evidence pack covers local-first storage and Sync encryption but contains no mention of telemetry, usage analytics, or an opt-out setting for such tracking. This is a fair question for any desktop app, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

   Logseq—none0/10

   The evidence describes Logseq as 'privacy-first, open-source' and local-first, implying no telemetry infrastructure exists, but there is no explicit documentation of a telemetry/usage-tracking feature or an opt-out setting for it. Absence of concrete evidence of an actual telemetry toggle means this cannot be confirmed as full/partial delivery. Missing for 10: explicit telemetry/analytics policy documentation, evidence of an opt-out setting or confirmation that no tracking occurs at all.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”

   proof ↗⚑ flag

Publish

1. researcherPublish selected notes as a browsable website — a digital garden with working links — without leaving the app

   weight 2 · round to Obsidian
   Obsidian✓fullclaimed8/10

   Obsidian Publish lets users select notes from their vault and publish them as a hosted, browsable site (digital garden/wiki) at publish.obsidian.md/your-site, with working internal links preserved via Obsidian's native linking system, all configured from within the app. missing for 10: no independent hands-on account of the publish workflow or link-rendering fidelity, and Publish is a paid add-on rather than free/bundled.

   • [claimed-docs] “Obsidian Publish is a cloud-based hosting service that lets you publish your notes as a wiki, knowledge base, documentation, or digital gard…”
   • [claimed-docs] “Select the notes you want to share with the world, press Publish, and we'll host it at publish.obsidian.md/your-site”
   • [claimed-docs] “By linking notes, you can create a network of knowledge.”

   proof ↗⚑ flag

   Logseq✓fullclaimed7/10

   Logseq's Publishing docs confirm per-page publish:: true flags to selectively expose notes, and the Publish feature generates a browsable static SPA site with working page/block references intact, matching the digital-garden use case entirely within the app. missing for 10: no independent/hands-on report confirming the exported site's link integrity or ease of workflow, and no detail on hosting/deployment specifics or custom domain support.

   • [claimed-docs] “By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.”
   • [claimed-docs] “This feature publishes a graph as a [[Publish Web]], single page application (SPA).”
   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”

   proof ↗⚑ flag

Collaboration

1. researcherShare a vault or space with collaborators and edit notes together without stepping on each other's changes

   weight 2 · round to Obsidian
   Obsidian!disputedcontradicted4/10

   Vendor docs claim Obsidian Sync lets teams 'collaborate on a shared vault' and offers version history to restore prior versions, but this is file-sync-based rather than real-time conflict-free editing — community evidence explicitly notes that neither Sync-adjacent tools (e.g. Git plugin) are 'great for device sync or collaboration' and that a separate third-party CRDT-based plugin had to be built to achieve Google-Docs-style simultaneous editing without overwriting changes, implying native Sync doesn't guarantee non-destructive concurrent edits. missing for 10: evidence of built-in conflict-free simultaneous multi-user editing, first-party documentation on merge/conflict handling during concurrent edits, hands-on reports confirming no data loss when two collaborators edit the same note at once.

   • [claimed-docs] “With Obsidian Sync you can collaborate on a shared vault with your team.”
   • [claimed-docs] “Version history - View or restore previous versions of a note.”
   • [community] “The Git plugin is great for single-device backup but not great for device sync or collaboration; a real-time collaboration plugin using CRDT…”

   proof ↗⚑ flag

   Logseq—none0/10

   Logseq's Sync feature is described as syncing a user's own graphs across their own devices (desktop/Android/iOS), not as multi-user real-time collaborative editing with conflict resolution; community reports describe using GitHub for personal sync/backup and note Logseq's own sync was still buggy/beta, with no evidence of concurrent multi-collaborator editing safeguards.

   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”
   • [community] “I still use Logseq and conceptually it's still a great method for building a second brain. But it has been dormant for years and early attem…”

   proof ↗⚑ flag

Sync

1. power-userAn official sync service keeps my notes updated across all my devices with end-to-end encryption the vendor can't read

   weight 3 · round to Obsidian
   Obsidian✓fullcommunity8/10

   Obsidian Sync is an official first-party add-on service documented to encrypt the remote vault and all communications, with end-to-end encryption as the default so 'no one — not even the Obsidian team — can access your notes,' directly matching the story. Missing for 10: independent third-party security audit or hands-on verification of the E2E claim, and one community report notes an Android sync edge case (files not saved until note unloads) that can cause missing content during sync, a minor reliability caveat.

   • [claimed-docs] “Obsidian Sync encrypts your remote vault and all communication with Obsidian's servers.”
   • [claimed-docs] “End-to-end encryption (default) offers the strongest security... This guarantees that no one — not even the Obsidian team — can access your …”
   • [claimed-docs] “Obsidian Sync is an add-on service that allows you to privately sync your notes across devices.”
   • [claimed-docs] “End-to-end encryption (default) offers the strongest security but requires you to safely store your encryption password.”
   • [community] “The Obsidian Android app does not save files to storage until the note unloads, which can break things if you sync/pull mid-edit, sometimes …”

   proof ↗⚑ flag

   Logseq!disputedcontradicted5/10

   Docs confirm an official Logseq Sync service across Desktop/Android/iOS with explicit end-to-end encryption ('Yes, your graph is end-to-end encrypted'), fitting the story's claim. However, community reports directly contradict reliable delivery: one user in 2022 found the paid sync beta 'has enough bugs that I wouldn't rely on it yet,' and another in 2025 stated 'early attempts at syncing didn't work well... I paid to support the sync effort but we saw nothing for years,' indicating the sync feature has a documented history of not working as promised despite payment. Missing for 10: independent verification that sync is now stable/production-ready, technical detail on the E2EE key model, and resolution of the multi-year reliability complaints.

   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”
   • [community] “I still use Logseq and conceptually it's still a great method for building a second brain. But it has been dormant for years and early attem…”
   • [community] “I loved what Logseq had to offer, and setup monthly donations for a while, but after the long period of apparent stagnation I lost faith and…”

   proof ↗⚑ flag

2. power-userView a note's version history and restore earlier versions or recover deleted notes

   weight 2 · round to Obsidian
   Obsidian✓fullclaimed6/10

   Obsidian's own docs explicitly list 'Version history - View or restore previous versions of a note' as a feature of Obsidian Sync, directly matching the story's core ask for power-users who pay for Sync. Missing for 10: explicit documentation of deleted-note recovery workflow, and independent/hands-on corroboration beyond the single first-party doc line.

   • [claimed-docs] “Version history - View or restore previous versions of a note.”
   • [claimed-docs] “Obsidian Sync is an add-on service that allows you to privately sync your notes across devices.”

   proof ↗⚑ flag

   Logseq—none0/10

   The evidence pack contains no documentation of a native version-history or restore/undo-delete feature in Logseq; users instead rely on external tools like Git for backup (logseq-comm-1), and there are reports of past data-loss issues (logseq-comm-3), but no built-in mechanism to view or restore prior versions of a note is described.

   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “I had two main problems with LogSeq: 1. Not designed from the ground-up to prevent data loss. Has had data-loss issues in the past.”

   proof ↗⚑ flag