Logseq is a privacy-first, open-source knowledge base built on local markdown files, with outlining, graph views and plugin extensibility.
Logseq stores everything as plain markdown/Org files on your device — no lock-in, no required cloud. Its outliner-style workflow uses daily notes as the entry point, with block references, backlinks and a graph view that turns your notes into a connected knowledge base. Tasks, PDF annotations and whiteboards extend it into a full research and productivity system, and a rich plugin ecosystem adds everything from spaced repetition to Zotero integration. Sync and publishing are optional paid services; the core app is free and open source.
Daily notes capture everything — tasks, meeting notes, readings — and blocks get linked into structure as themes emerge. The graph view reveals how ideas connect across months of capture, and whiteboards support visual arrangement of clusters. Plugin ecosystems add spaced repetition, Zotero sync and custom themes, and because files are local markdown, syncing via your own storage keeps full ownership.
Logseq’s core is free and open source. Optional paid services include Logseq Sync (encrypted cloud sync) and Publish, with funding supporting ongoing development.
It suits privacy-conscious knowledge workers, developers, students and researchers who want a local-first, hackable notes system.
A developer captures everything in daily notes — tasks, meeting outcomes, article highlights — and links blocks into project pages as themes emerge. The graph reveals connections across months, and plugins add spaced repetition for study material. Local markdown storage means the archive outlives any single tool.
Yes — the app is free and open source; only optional sync/publish services are paid.
Yes, a plugin API and local graph access enable extensive community-built integrations.
Compared with Obsidian, Logseq is outliner-first and fully open source; compared with Roam, it is free and local-first.
Both tools work on local markdown, but their formats differ — Logseq adds block metadata — so while notes can interoperate loosely, dedicated vaults per tool avoid structural conflicts.