Tools of the Trade

Choosing a PKM tool is one of those decisions that inspires the same irrational passion people reserve for text editors, programming languages, and barbecue techniques. Communities form. Manifestos are written. Migration guides are published with the solemnity of refugee resettlement plans. And every eighteen months, a new tool arrives promising to be the One True System, triggering another round of agonized switching.

This chapter aims to cut through the noise. We will survey the major tools in the PKM landscape with honest assessments of their strengths and weaknesses. We will establish criteria for choosing wisely. And we will make the case for a principle that should guide every decision: your knowledge should outlast your tools.

Obsidian: The Local-First Powerhouse

What it is: A markdown-based note-taking application that stores everything as plain text files on your local filesystem.

Why it matters: Obsidian has become the default recommendation for serious PKM practitioners, and for good reason. It gets the fundamentals right: your notes are plain markdown files in a folder on your computer. No proprietary database, no mandatory cloud sync, no vendor lock-in. If Obsidian disappeared tomorrow, you would still have a folder full of perfectly readable text files.

Strengths:

  • Local-first architecture. Your data lives on your filesystem. You own it completely. You can back it up with git, sync it with Syncthing, or copy it to a USB drive. No internet connection is required to access your notes.
  • Plugin ecosystem. Obsidian's community plugin system is extraordinary. As of this writing, there are over 1,800 community plugins covering everything from spaced repetition to Kanban boards to dataview queries that treat your vault as a queryable database. If Obsidian cannot do something out of the box, there is almost certainly a plugin for it.
  • Graph view. The visual graph of connections between notes is more than eye candy — it reveals clusters of related ideas, orphaned notes that need better connections, and structural patterns in your thinking.
  • Linking and backlinking. First-class support for [[wikilinks]] and automatic backlink tracking makes building a Zettelkasten-style network straightforward.
  • Templates and automation. The Templater plugin, combined with QuickAdd and dataview, enables sophisticated automation without leaving the application.

Weaknesses:

  • Not truly open source. Obsidian is free for personal use but proprietary. The source code is not available for inspection or modification. This matters less than you might think — because the data format is open (plain markdown), you are not locked in even though the application is closed.
  • Sync costs money. Obsidian's own sync service costs $4/month. You can avoid this by syncing your vault folder through other means (iCloud, Dropbox, Syncthing, git), but the official sync is the most seamless option, especially for mobile.
  • Electron-based. Obsidian runs on Electron, which means it consumes more memory than a native application. On modern hardware this is rarely noticeable, but if you are running on constrained systems, it is worth knowing.
  • Plugin quality varies. The plugin ecosystem is a double-edged sword. Some plugins are brilliantly maintained; others are abandoned side projects that break with every update. Audit your plugins periodically.

Best for: Writers, researchers, developers, and anyone who values data ownership and long-term durability.

Logseq: The Outliner Alternative

What it is: An open-source, outliner-based knowledge management tool that stores data as local markdown or org-mode files.

Strengths:

  • Truly open source. Licensed under AGPL, the source code is available on GitHub. If the company disappears, the community can fork and continue development.
  • Outliner-first design. Every piece of content in Logseq is a block in an outline. This makes it natural for people who think in hierarchies and bullet points. Blocks can be referenced and embedded elsewhere, giving you granularity below the note level.
  • Daily journals as default. Logseq encourages a journal-first workflow: you write in today's journal page and link to topic pages as needed. This eliminates the "where should I put this?" paralysis that afflicts folder-based systems.
  • Local storage. Like Obsidian, your files live on your filesystem.

Weaknesses:

  • Performance. Logseq can become sluggish with large databases. The team has been working on a database version to address this, but as of this writing, performance with tens of thousands of blocks remains a concern.
  • Markdown compatibility. Logseq's outliner structure means it writes markdown in a specific format (heavy on bullet points) that looks odd when opened in other markdown editors. Your data is technically portable, but practically it requires some cleanup.
  • Smaller ecosystem. The plugin and theme ecosystem is significantly smaller than Obsidian's.
  • Mobile experience. The mobile apps have improved but still lag behind Obsidian's mobile offering in polish and reliability.

Best for: Outliner enthusiasts, open-source advocates, and people who prefer a journal-first workflow.

Notion: The Collaborative All-in-One

What it is: A cloud-based workspace that combines notes, databases, wikis, project management, and more in a single application.

Strengths:

  • Collaboration. Notion's real-time collaboration is genuinely excellent. Multiple people can edit the same page simultaneously, leave comments, and manage shared workspaces. For teams, this is a significant advantage.
  • Databases. Notion's database feature — which lets you create structured tables with multiple views (table, board, calendar, gallery, timeline) — is unique and powerful. It bridges the gap between freeform notes and structured data.
  • Polish. The user interface is beautiful and intuitive. Notion lowers the barrier to entry for people who are not technically inclined.
  • Templates. A vast library of community templates covers virtually every use case, from CRM systems to habit trackers to content calendars.

Weaknesses:

  • Cloud-dependent. This is the fundamental problem. Your data lives on Notion's servers. No internet, no notes. If Notion has an outage — and they have had several — you have nothing. If Notion goes out of business, your data is hostage to their export tools (which exist but are imperfect).
  • Performance. Notion can be slow, especially with large workspaces. Loading times for complex pages are noticeable.
  • Proprietary format. Notion stores data in its own format. You can export to markdown, but the export is lossy — databases, toggles, callouts, and embedded content do not survive the translation cleanly.
  • Privacy. Your notes live on someone else's computer. Notion's privacy policy is reasonable, but if you work with sensitive information, this matters.
  • Offline support. Notion has added offline capabilities, but they remain limited compared to local-first tools. You can view cached pages offline, but creating and editing offline is inconsistent.

Best for: Teams that need collaboration, project managers, and people who value aesthetics over data sovereignty.

Roam Research: The Pioneer

What it is: A web-based tool for networked thought, featuring bidirectional linking and block-level references.

Strengths:

  • Historical significance. Roam popularized bidirectional linking, block references, and the concept of "networked thought" in consumer tools. Much of what Obsidian and Logseq offer today was pioneered by Roam.
  • Block references. Roam's implementation of block-level transclusion — embedding a specific bullet point from one page into another, with the reference staying live — remains one of the best in the field.
  • Query system. Roam's query language lets you build dynamic views of your knowledge base.

Weaknesses:

  • Price. At $15/month (or $180/year), Roam is significantly more expensive than most alternatives, several of which are free.
  • Cloud-only. Your data lives on Roam's servers. Export options exist but are limited to JSON and markdown formats that require significant post-processing.
  • Development pace. After an initial burst of innovation, Roam's development has slowed considerably. Features that competitors have shipped — mobile apps, plugin systems, publishing — have been slow to arrive or remain absent.
  • Small team risk. Roam is built by a small team. The long-term viability of the product is a legitimate concern for anyone committing years of knowledge to the platform.

Best for: Early adopters who are already invested in the platform and value its specific approach to block-level thinking.

DEVONthink: The macOS Powerhouse

What it is: A document management and knowledge organization system for macOS (and iOS), designed for handling large, diverse collections of files.

Strengths:

  • AI classification. DEVONthink includes a built-in AI engine that classifies documents, suggests filing locations, and finds related content. This predates the current AI hype by over a decade — it uses techniques like n-gram analysis and semantic similarity to understand your documents.
  • Format omnivore. While other tools focus on markdown, DEVONthink handles PDFs, web archives, images, email, Word documents, spreadsheets, and virtually any other file format. It is a true document management system.
  • Powerful search. Full-text search across all document types, with boolean operators, proximity search, and fuzzy matching. DEVONthink indexes the content of PDFs including OCR for scanned documents.
  • Local storage. Everything lives in a database on your Mac. Sync between devices uses your own cloud storage (iCloud, Dropbox, etc.) with end-to-end encryption.
  • Mature and stable. DEVONthink has been in active development since 2002. It is not going anywhere.

Weaknesses:

  • macOS only. There is no Windows or Linux version. If you leave the Apple ecosystem, you leave DEVONthink.
  • Learning curve. DEVONthink is powerful but complex. The interface feels dated compared to modern tools, and the sheer number of features can be overwhelming.
  • Not a writing tool. DEVONthink excels at organizing and retrieving documents but is not designed for long-form writing or Zettelkasten-style note-taking. Many users pair it with Obsidian — DEVONthink for document management, Obsidian for note-taking.
  • Price. The Pro version costs $199 (one-time purchase). Not unreasonable for what you get, but significantly more than free alternatives.

Best for: Researchers, lawyers, academics, and anyone on macOS who manages large collections of diverse documents.

Zotero: The Research Workhorse

What it is: A free, open-source reference manager designed for academic research.

Strengths:

  • Citation management. Zotero's core competency is managing bibliographic references and generating citations in any format. For anyone who writes papers, this is indispensable.
  • PDF annotation. The built-in PDF reader supports highlighting, commenting, and extracting annotations into notes.
  • Browser integration. The Zotero Connector browser extension captures bibliographic metadata from virtually any website, journal, or library catalog with a single click.
  • Open source and free. Zotero is free for most users (you pay only if you need more than 300MB of cloud storage for attachments).
  • Plugin ecosystem. Plugins like Better BibTeX (for LaTeX users) and Zotero-Obsidian integration extend Zotero's capabilities significantly.

Weaknesses:

  • Narrow focus. Zotero is a reference manager, not a general-purpose knowledge management tool. It handles research sources well but is not designed for meeting notes, project management, or freeform thinking.
  • Note-taking is basic. Zotero's built-in note editor is functional but limited. Most serious users export their Zotero annotations to a more capable tool (Obsidian, Logseq, etc.) for further processing.

Best for: Academics, researchers, and anyone who regularly cites sources in their writing. Pair it with a more general PKM tool.

Org-mode: For the Emacs Faithful

What it is: A major mode for GNU Emacs that provides outlining, note-taking, task management, literate programming, and document authoring in a single plain-text system.

Strengths:

  • Unmatched power. Org-mode is, by a considerable margin, the most powerful personal information management system ever created. It handles notes, tasks, calendars, time tracking, spreadsheets, literate programming, and document export (to HTML, LaTeX, PDF, and dozens of other formats) — all in plain text.
  • Programmability. Because it runs inside Emacs, org-mode is infinitely customizable through Emacs Lisp. If you can describe a workflow, you can implement it.
  • Plain text. Org files are plain text with a simple markup syntax. They will be readable in a hundred years.
  • org-roam. The org-roam package brings Zettelkasten-style linking and backlinks to org-mode, creating a Roam/Obsidian-like experience for Emacs users.
  • Free and open source. Part of GNU Emacs, licensed under GPL.

Weaknesses:

  • Emacs. Org-mode requires Emacs, and Emacs has a learning curve best described as "vertical." If you are not already an Emacs user, the investment required to become productive is measured in weeks or months, not hours.
  • Mobile. Mobile support ranges from "workable" (Beorg on iOS, Orgzly on Android) to "painful." Nothing matches the desktop experience.
  • Collaboration. Org-mode is a single-player tool. Sharing and collaborating on org files with non-Emacs users is awkward at best.
  • Community size. The org-mode community is dedicated but small. You will find fewer tutorials, templates, and YouTube walkthroughs than for Obsidian or Notion.

Best for: Emacs users. You know who you are. For everyone else, the adoption cost is prohibitive unless you are also adopting Emacs for programming.

Criteria for Choosing

With so many options, how do you decide? Here are the criteria that matter most, roughly in order of importance.

Local-First vs. Cloud

This is the most consequential architectural decision. Local-first tools (Obsidian, Logseq, DEVONthink, org-mode) store your data on your device. Cloud tools (Notion, Roam) store your data on someone else's servers.

Local-first advantages: you control your data, you can work offline, you are not dependent on a company's continued existence, and your privacy is inherently protected.

Cloud advantages: automatic sync, easy collaboration, no backup management.

For a personal knowledge base that you intend to maintain for years or decades, local-first is the safer bet. Companies shut down, get acquired, change pricing, or pivot to different markets. Your filesystem does not.

Open Formats

Can you read your data without the tool? Markdown files pass this test. Proprietary database formats do not. The day you need to migrate to a different tool — and that day will come — open formats make the transition painless. Proprietary formats make it a project.

Longevity

How long has the tool been around? Is it backed by a sustainable business model or a dedicated open-source community? A tool that launched six months ago with venture capital funding and no revenue model is a risk. Emacs has been around since 1976. Plain text has been around since the dawn of computing. Bet on things that last.

Export Options

Even if a tool uses a proprietary format internally, good export options provide an escape hatch. Evaluate the quality of exports — do they preserve your links, tags, and metadata? Or do they produce a pile of disconnected files that require significant cleanup?

Full-text search across all your notes is not optional. It is the single most important retrieval mechanism you have. Test it with real queries before committing. How fast is it? Does it handle boolean queries? Can it search within attachments?

Extensibility

Can the tool be extended through plugins, scripts, or APIs? Your needs will evolve. A tool that cannot be extended will eventually become a constraint.

The Plain-Text Advantage

If there is one principle that should guide your tool selection above all others, it is this: store your knowledge in plain text whenever possible.

Plain text — including markdown, org-mode, and other lightweight markup formats — has properties that no proprietary format can match:

  • Universal readability. Every operating system, every device, and every text editor in existence can read plain text. This will remain true for as long as computers exist.
  • Version control. Plain text files work perfectly with git, giving you complete history of every change you have ever made to every note.
  • Scriptability. Plain text can be processed by standard Unix tools (grep, sed, awk), programming languages, and custom scripts. This makes automation trivial.
  • Durability. Plain text files from the 1970s are perfectly readable today. Can you say the same about files created in any proprietary format from that era?
  • Size. Plain text is compact. A lifetime of notes in plain text might occupy a few hundred megabytes — a rounding error on modern storage.

The tools built on top of plain text may come and go. The text itself endures.

This does not mean you should avoid tools that add features beyond plain text. Obsidian's graph view, for example, is valuable precisely because it adds a visualization layer on top of plain text files. The key is that the plain text remains the source of truth. The tool is a lens through which you view and interact with your text, not a prison that holds it hostage.

When you choose your tools, ask one final question: if this tool disappeared tomorrow, what would I have left? If the answer is "a folder of well-organized, interlinked markdown files," you have chosen well. If the answer is "a frantic search for export options," reconsider.

Your knowledge deserves better than to be trapped in an application that may not exist in five years. Write in plain text. Link with standard syntax. Back up with git. And use whatever tool makes the writing pleasant — secure in the knowledge that your words will outlast the software you used to write them.