Logseq

Extend a Markdown/Org-mode outliner into a knowledge graph with tasks and PDF annotation

The official README positions Logseq as a privacy-first knowledge-management and collaboration platform, with support for Markdown and Org-mode, PDF annotation, and task management. It works well as a PKM where daily journals and outlines are broken into smaller units that can later be connected and revisited through pages and block references.

Sources: [1]

Adapt the workflow through plugins, themes, mobile apps, and a public Plugin API

The README highlights a plugin and theme ecosystem, mobile apps, and a public Plugin API. Logseq is therefore more than a closed desktop note editor: community extensions and custom plugins can change capture, presentation, and automation. The codebase centers on Clojure/ClojureScript and also includes Electron and mobile runtimes, with a CLI shipped from the same repository.

Sources: [1][3]

Move toward DB graphs with unified nodes, typed properties, tags, tables, MCP, and RTC

The DB version brings pages and blocks closer under a shared node model and adds typed properties, tag inheritance, table views, queries, cards, assets, and templates. The official DB documentation also covers an MCP Server, Sync, CLI, automated backup, and graph export/import, showing the project's direction toward a more structured knowledge base than the traditional file graph.

Sources: [2]

For outline-first thinking, linked knowledge, local data control, and long-lived personal knowledge bases

Logseq fits people who prefer capturing small blocks over drafting finished documents first, then organizing knowledge through references and tags. It remains relevant to users who want to manage Markdown/Org-mode file graphs themselves, while the DB graph gives property- and table-oriented users a new direction to evaluate. Developers who want plugins or CLI-driven workflows also have room to customize it.

DB graphs are beta while RTC and the new mobile app are alpha, with possible data loss

The README labels the DB version beta and the new mobile app and RTC alpha. It explicitly says data loss is possible and recommends automated backups or regular SQLite database backups. The official guidance is to use a dedicated test graph and a non-critical project before relying on the new stack.

The DB version is not merely a storage-format swap: the node, property, and tag model changes, as does synchronization. Existing users should read db-version-changes and validate backups, export/import behavior, and plugin compatibility before migration.

Sources: [1][2]

Local-first use and synced collaboration have different data boundaries, and AGPL obligations matter

A local file graph and a DB graph using RTC or multi-device sync have different data paths and recovery considerations. If sync is enabled, verify the sync state and export path separately from local backups so one mechanism is not mistaken for the other.

Logseq is licensed under AGPL-3.0. Redistribution, modifications, and especially network-accessible modified deployments should be reviewed for the license's source-availability obligations.

Sources: [1][4]