Logseq: features, limits & comparisons
An outliner with properties, templates and queries; supertags arrive as several smaller ideas.
functionality and fit
Recorded license: AGPL-3.0.
- Classic file graphs are folders of Markdown or Org-mode files plus Logseq configuration/cache files and can be synced with a file service; the newer DB graph stores the graph in a local SQLite database, while optional Logseq Sync/RTC sends graph data to Logseq's service
- Download the desktop/mobile release or use the hosted web app; no server is required for a local graph
Costs and editions: A source license is separate from operating costs. Hosting, storage, external APIs and commercial support may require payment.
scope and migration checks
- Logseq has properties, templates, and queries but no single supertag system that instantly turns blocks into typed records with live structured views like Tana.
- Logseq closely matches the outliner, but its sync and collaboration story is less mature and its transition between file and database editions adds uncertainty.
- Its links and whiteboards are powerful, but whiteboard polish, mobile experience, and performance are rougher, while the newer database path still carries beta risk.
recorded catalogue description · recorded source check 2026-08-14 · suitability checks are editorial assessments, not hands-on tests
licenseAGPL-3.0
runsyour machine or their cloud
installDownload the desktop/mobile release or use the hosted web app; no server is required for a local graph
dataClassic file graphs are folders of Markdown or Org-mode files plus Logseq configuration/cache files and can be synced with a file service; the newer DB graph stores the graph in a local SQLite database, while optional Logseq Sync/RTC sends graph data to Logseq's service
setupStable local installation is simple, but the visually stronger DB graph/RTC path is still beta or alpha and explicitly carries data-loss warnings; free cross-device file-graph sync requires choosing and safely operating a third-party file-sync method
recorded source check 2026-08-14 · installation not tested
compare these app workflows
These are scoped comparisons, not guarantees that Logseq reproduces every paid feature. Follow each build guide for the implementation boundary and the collection for other options.
An outliner with properties, templates and queries; supertags arrive as several smaller ideas.
the catchLogseq has properties, templates, and queries but no single supertag system that instantly turns blocks into typed records with live structured views like Tana.
the verdict →all Tana alternatives →Roam's block graph, minus the monthly tribute and plus a folder you can inspect.
the catchLogseq closely matches the outliner, but its sync and collaboration story is less mature and its transition between file and database editions adds uncertainty.
the verdict →all Roam Research alternatives →Cards, block links and whiteboards for sense-making, with rougher furniture.
the catchIts links and whiteboards are powerful, but whiteboard polish, mobile experience, and performance are rougher, while the newer database path still carries beta risk.
the verdict →all Heptabase alternatives →Daily notes, backlinks and block references; calendar context is native, AI is optional.
the verdict →latest catalogue source check 2026-08-14 · recorded recurring plans: $647.88/yr (before operating costs) · no votes, no pay-to-list
sources and related categories
These are sources retained with the catalogue record. Their recorded check date is not a new verification of current terms.