Dendron

Open-source knowledge management for developers, honestly reviewed. Including the part nobody mentions upfront.

TL;DR

• What it is: Open-source (Apache-2.0), local-first, markdown-based personal knowledge management tool built as a VS Code extension, designed around hierarchical note organization [1].
• Who it’s for: Developers who live in VS Code and need to manage large knowledge bases — hundreds or thousands of notes — without losing retrieval ability as the corpus grows [1].
• Critical status update: Dendron is in maintenance-only mode. Active development has ceased as of the announcement in GitHub Discussions [3]. No new features are coming. This changes the adoption calculus entirely.
• Cost: Free. Apache-2.0 license. No paid tier, no SaaS pricing. You pay for your own storage and publishing infrastructure [1][2].
• Key strength: The hierarchical + schema system was genuinely different from flat-link PKM tools. It scales to 10k+ notes without retrieval falling apart [1].
• Key weakness: It’s dead, practically speaking. No active maintainer, no roadmap, and VS Code’s extension ecosystem moves fast — compatibility issues will accumulate over time [3].

---

What is Dendron

Dendron is a markdown-based note-taking tool that runs entirely inside VS Code (and its open-source fork VSCodium). There is no Electron app, no web interface, no mobile client. Your notes are plain .md files in a local vault, versioned with git, editable in any text editor. Dendron adds a layer of tooling on top: hierarchical organization, schemas (a type system for your notes), note references, backlinks, and a publishing system [1][2].

The core design bet was that flat, link-based PKM — the Roam/Obsidian approach — breaks down past a certain note volume. When you have 10,000 notes and search returns 200 results, links between nodes help but don’t solve the signal-to-noise problem. Dendron’s answer was hierarchy: notes are named with dotted paths like aws.ec2.troubleshooting or project.clientname.meeting.2024-03, and the tool builds tree views, enforces schemas, and provides refactoring tools to rename entire subtrees [1].

The GitHub README opens with this line: “Dendron is currently in maintenance only, active development has ceased.” [3] That’s unusual honesty from a project’s own README, and it’s the most important fact about Dendron in 2024. Everything else in this review has to be read in that context.

At the time development wound down, Dendron had 7,380 GitHub stars, 244 contributors, and a claimed community of 30,000+ users (the “Dendrologist” community) [1][2]. That’s not a failed project — it’s a genuinely loved tool that ran out of runway.

---

Why people chose it

The testimonials on the website are all from developers and engineers, which is accurate to the actual user base [2]:

The hierarchy argument. A Site Reliability Engineer on the testimonials page puts it well: “Hierarchies [are] such a game changer. I just couldn’t organize myself with a flat structure and ended up spreading notes out. The key thing that changed my perspective was the ease of restructuring hierarchies — it gives you the confidence to just write, safe in the knowledge that you can just restructure it later.” [2] This is the thing Dendron got right: the cost of reorganizing is near-zero because the tooling handles cross-reference updates.

VS Code nativity. For developers who don’t want to leave their editor, Dendron was the only serious option in the hierarchical PKM space. Obsidian requires a separate app. Notion requires a browser. Dendron works in the same pane where you write code, with the same keybindings, the same vim mode, the same search [1].

Plain text permanence. Every note is a markdown file in a directory. You can grep it, git-blame it, diff it, open it in Vim, or push it to GitHub. This is mentioned repeatedly by users who’ve been burned by proprietary formats — Notion’s export, Roam’s incomprehensible JSON [1][2].

Schemas as a forcing function. The schema system lets you define what children a note type can have, what templates get applied on creation, and enforce naming conventions. A software architect in the testimonials: “I use Dendron mostly to manage multiple projects to keep track of meeting notes, TODOs, planned features and sharing all of this with my colleagues.” The schema system is what makes this reproducible across dozens of projects [2].

---

Features

Based on the README and website content [1][2]:

Core note system:

• Hierarchical note naming with . as separator — full lookup, autocomplete, and tree view [1]
• Schemas: YAML-defined type system for note hierarchies. Define allowed children, templates, namespace nodes [1][2]
• Note references: embed sections of one note inside another, rendered inline [1]
• Backlinks: see everywhere a note is referenced [1]
• Refactoring: rename or move an entire hierarchy and all references update [1]
• Daily journal notes with configurable structure [2]
• Scratch notes for quick capture [2]
• Templates on note creation [1]

Content and formatting:

• Standard markdown plus Dendron-flavored extensions [1]
• Mermaid diagram support [1]
• KaTeX math rendering [1]
• Code blocks with syntax highlighting [1]

Developer tooling:

• Plain .md files — git-compatible by default [1]
• git blame for individual note edits [1]
• Vim-mode compatible (via VS Code) [1]
• Local-first: everything runs on your machine, no cloud dependency [1]

Publishing (Dendron Publishing):

• Static site generator for your vault — publish a subset of notes as a public digital garden [2]
• “Plant, Grow, Share” — the homepage feature section for this [2]

Collaboration (limited):

• Multi-vault support: compose multiple vaults, including remote git vaults [1]
• Not a real-time collaboration tool — no multiplayer editing [1]

---

Pricing: SaaS vs self-hosted math

Dendron doesn’t have a SaaS pricing model. It’s free software, Apache-2.0 licensed, with no paid tier and no freemium gate [1].

What you pay for:

• Nothing for the tool itself
• Storage: your notes are local files or a git repo — GitHub free tier handles this for most users
• Publishing: if you use Dendron Publishing, you host the static output yourself — Netlify free tier or a $5/mo VPS covers this
• A VS Code install (free)

Comparison to alternatives:

• Obsidian: free for personal use, $50/yr for commercial use, $8/mo for Sync, $4/mo for Publish — features gated behind payment [pricing data not in provided sources]
• Roam Research: $15/mo or $500/yr flat — no free tier beyond trial
• Notion: free up to a limit, then $8–10/user/mo
• Logseq: free, open-source — the closest structural competitor

For a non-technical founder doing the math: Dendron vs Notion or Roam is $0/yr vs $96–180/yr. The catch is that Dendron requires VS Code and some comfort with file systems. If you’re not a developer, this isn’t a viable Notion replacement.

---

Deployment reality check

“Deployment” for Dendron is just installing a VS Code extension. There’s no server, no Docker container, no database.

What the setup actually involves:

1. Install VS Code (or VSCodium)
2. Install the Dendron extension from the VS Code Marketplace
3. Run the “Dendron: Initialize Workspace” command
4. You now have a local vault

What can go sideways:

• Active development has ceased [3]. This is the primary risk. VS Code updates its extension API periodically. Dendron’s extension may break with future VS Code versions, and there’s no team to fix it. Users on older VS Code versions are safer for now.
• Mobile is a dead end. There’s no mobile app. You can read and edit markdown files on your phone with any text editor, but the Dendron-specific features (lookup, schemas, references) require the VS Code extension.
• Learning curve on schemas. The schema system is powerful but genuinely requires time to learn. Multiple testimonials mention taking days to figure out the right hierarchy before things clicked [2].
• Publishing requires technical comfort. Dendron Publishing generates static files you host yourself. This is not a one-click experience for a non-technical user.
• Community support is winding down. The Discord and forums still exist, but without active development the community’s ability to answer questions about bugs or new VS Code version issues is limited.

---

Pros and Cons

Pros

• Free, forever, no licensing tricks. Apache-2.0 means you can use it commercially, fork it, modify it. No “Fair-code” asterisks [1].
• Plain text vault. Your notes survive the project’s death. They’re markdown files. You own them completely and can migrate to any other tool [1].
• Hierarchy actually scales. The core design insight — that linked graphs break down at scale but trees don’t — was correct, and Dendron’s tooling executes on it better than any contemporary [1][2].
• Schema system is unique. No other mainstream PKM tool has a type system for notes. For engineering teams managing documentation at scale, this was genuinely useful [1][2].
• VS Code integration is deep. Multi-cursor, vim mode, language server, git integration — everything VS Code does well, your notes inherit [1].
• Healthy contribution base before maintenance mode. 244 contributors means the codebase is in reasonable shape; it’s not going to spontaneously explode [1].

Cons

• Active development has ceased [3]. This is disqualifying for new adoption in any production or team setting. There are no maintainers committing to VS Code API compatibility, security patches, or bug fixes.
• Developer-only tool. If your team includes anyone who doesn’t use VS Code daily, Dendron isn’t for them. There’s no web UI, no desktop app, no mobile client [1].
• Steep learning curve. The schema and hierarchy system requires genuine investment before you’re productive. One testimonial: “It took me a couple of days to figure out the best workflow.” [2] That’s from someone who was enthusiastic about it.
• Publishing is DIY. Dendron Publishing outputs static files. You configure, host, and maintain that yourself [2].
• No real-time collaboration. Multi-vault with git is available, but this is async collaboration at best. If your team needs to edit documents simultaneously, look elsewhere [1].
• Community momentum is gone. The Discord, forums, and community contributions that made Dendron worth adopting were downstream of active development. Without that, the community naturally disperses.

---

Who should use this / who shouldn’t

Use Dendron if:

• You’re a solo developer or small engineering team who wants to manage a large personal knowledge base inside VS Code, and you understand you’re adopting maintained-but-not-developed software.
• You want to migrate an existing Dendron vault — the plain text format means your existing notes aren’t going anywhere, and you can continue using it until VS Code compatibility breaks.
• You’re explicitly looking for a Roam/Obsidian alternative that works entirely offline, with no cloud sync requirement, and you’re comfortable with hierarchical (not graph) organization.

Don’t adopt Dendron fresh if:

• You’re evaluating PKM tools for a team of mixed technical/non-technical users — the VS Code requirement is a hard wall for most non-developers.
• You want a tool that will receive security patches, VS Code API updates, and feature development. Dendron won’t get these [3].
• You need mobile access — there’s no mobile client and none is coming.
• You need real-time collaboration — this isn’t the tool.

Consider migrating away from Dendron if:

• You’re an existing user who depends on Dendron Publishing — the publishing infrastructure will need eventual replacement.
• Your team’s VS Code version is managed by IT and upgraded frequently — compatibility breaks are a matter of when, not if.

---

Alternatives worth considering

• Obsidian — the most direct competitor that’s still actively developed. Graph-based rather than hierarchical, with a large plugin ecosystem. Free for personal use, paid for commercial/sync. Runs as a standalone app with optional mobile clients. If you liked Dendron’s local-first approach and don’t need the hierarchy system, Obsidian is the obvious migration path.
• Logseq — open-source (AGPL), block-based, graph-linked, actively developed. Closer to Roam in feel. Local-first with optional sync. Markdown + org-mode support. No schema system but strong outliner model.
• Roam Research — the graph PKM that Dendron was partially a reaction to. $15/mo or $500 flat. Closed source. Better for nonlinear thinking, worse for scale and structure.
• Notion — for teams who need collaboration and don’t need the developer-centric features. Closed source SaaS, $8–10/user/mo. Can’t version-control your content in any meaningful way.
• org-mode (Emacs) — if Dendron’s appeal was “powerful PKM inside your editor,” org-mode has been doing this for decades and its development isn’t stopping. Higher learning curve, tighter Emacs lock-in.
• Foam — VS Code extension like Dendron, open-source, still maintained (as of this writing). Flat/graph-linked rather than hierarchical. More minimal. If you want “PKM in VS Code” without the hierarchy complexity, Foam is worth evaluating.

---

Bottom line

Dendron built something genuinely novel — a hierarchical, schema-driven PKM that actually scaled — and attracted a real community of developers who were tired of graph PKM tools breaking down at volume. The core design was right, the execution was good, and the Apache-2.0 license meant your data was always yours. Then the team stopped active development.

That last fact makes recommending Dendron for new adoption almost impossible to justify. Not because the software is broken today, but because VS Code moves fast, technical debt accumulates, and there’s no one fixing it. Your notes will be fine — they’re markdown files. Your Dendron installation will eventually fall behind the VS Code API and stop working correctly.

If you’re an existing Dendron user: your data is safe, keep using it until something breaks, and plan a migration to Obsidian or Logseq when that happens. If you’re evaluating tools for the first time: the tool Dendron was trying to be is the right concept, but Obsidian (with plugins like Dataview and Templater) or Logseq is where the active development is now.

---

Sources

1. Dendron GitHub README — primary source for features, design philosophy, license, contributor count, and maintenance status. https://github.com/dendronhq/dendron
2. Dendron Official Website — homepage testimonials, feature descriptions, Dendron Publishing overview. https://www.dendron.so
3. GitHub Discussions — “Dendron is currently in maintenance only, active development has ceased” https://github.com/dendronhq/dendron/discussions/3890