Obsidian
What It Does
Obsidian is a local-first personal knowledge management (PKM) application built around plain markdown files. All notes are stored in a “vault” — a standard directory on the user’s filesystem — giving users complete control and portability. The application provides bi-directional linking (notes can reference each other and automatically appear in each other’s backlinks panel), a graph view visualizing the connection network, and a plugin ecosystem with thousands of community-contributed extensions.
Unlike cloud-first alternatives (Notion, Roam), Obsidian treats the file system as the source of truth. Users own their data unconditionally. Sync and publish are optional paid add-on services; the core application is free with no usage limits. As of February 2026, commercial use no longer requires a separate license.
Key Features
- Local-first markdown: All notes stored as plain
.mdfiles in a user-controlled directory; no vendor lock-in - Bi-directional links:
[[note-name]]syntax creates links tracked in both directions; backlinks panel shows all notes linking to a given note - Graph view: Interactive visualization of the note network; useful for identifying clusters and orphaned notes
- Canvas: Spatial note arrangement for visual thinking and project planning
- Plugin ecosystem: 2,000+ community plugins; covers Kanban boards, spaced repetition, Dataview queries, calendar, and more
- Obsidian Sync: Optional end-to-end encrypted sync across devices ($4–5/month)
- Obsidian Publish: Optional service to publish notes as a public website ($8–10/month)
- Themes: Fully customizable appearance via CSS
- Template support: Note templates with variable substitution for consistent structure
Use Cases
- Use case 1: Developer personal knowledge base — structured notes on code patterns, system designs, and technical decisions accumulated over months with LLM agent integration (Karpathy’s LLM Wiki pattern)
- Use case 2: Research compounding — reading papers and linking concepts, authors, and findings into a networked graph that makes implicit connections explicit
- Use case 3: Project management — using Canvas and Kanban plugins for visual task tracking alongside linked project notes
- Use case 4: Digital garden — maintaining a personal wiki published via Obsidian Publish for sharing evolving thinking
- Use case 5: AI-assisted knowledge management — using Obsidian as the file system layer while an LLM agent (Claude Code, etc.) maintains the wiki structure
Adoption Level Analysis
Small teams (<20 engineers): Fits well for individual use or small teams sharing a vault via Git. Free tier covers all core functionality. Plugin ecosystem handles most workflow needs. The local-first model requires users to manage their own sync strategy if not using Obsidian Sync.
Medium orgs (20–200 engineers): Viable for team knowledge bases if the team is comfortable with Git-based collaboration. Concurrent editing is awkward without proper conventions. Not designed as a team collaboration tool; Confluence or Notion handle shared editing better. Shared wikis work if one person (or an agent) is the primary maintainer.
Enterprise (200+ engineers): Does not fit. No RBAC, no audit logs, no enterprise SSO, no programmatic API, no integration with enterprise identity. Obsidian is a personal productivity tool; enterprises needing shared knowledge management should look elsewhere.
Alternatives
| Alternative | Key Difference | Prefer when… |
|---|---|---|
| Notion | Cloud-first, richer collaboration, databases | Team-shared knowledge base; collaboration is primary use case |
| Roam Research | Outliner-first, daily notes focus | Roam’s block-reference model fits your thinking style better |
| Logseq | Open-source, local-first similar to Obsidian | You want open-source with outliner-style editing |
| Dendron | VSCode-based, hierarchical note structure | You work primarily in VSCode; prefer hierarchical over flat+linked |
| Standard Notes | Simpler, focused on encrypted private notes | Security and simplicity are priority over linking/graph features |
Evidence & Sources
- Obsidian official pricing — pricing structure
- Obsidian Pricing 2026: 5 Plans from Free–$50/month — independent pricing overview
- Mastering Personal Knowledge Management with Obsidian and AI — practitioner experience with AI integration
- How to Build a Local LLM Knowledge Base With Obsidian (2026) — local AI integration guide
Notes & Caveats
- Not truly open-source: The core application is proprietary, though free. The source code is not available for inspection or contribution. Plugin code is open-source, but the core is not.
- No API: Obsidian has no programmatic API for external applications. Integration with LLM agents relies on agents reading/writing the vault as a filesystem — which works but is informal.
- Concurrent editing: Multiple simultaneous writers to the same vault cause merge conflicts in Git and data loss without Obsidian Sync (which handles this via CRDT). Not designed for team collaboration.
- Mobile experience: Mobile apps exist but are historically behind desktop in feature parity. Plugin support on mobile is inconsistent.
- Plugin quality variance: With 2,000+ community plugins, quality varies widely. Core plugins are maintained; community plugins may be abandoned.
- Valuation vs. revenue transparency: Estimated $300–350M valuation reported, but as a bootstrapped private company, Obsidian does not disclose revenue or funding. User-supported model is sustainable but no venture backing means slower feature development.
- AI integration is informal: LLM agent integration (Karpathy’s LLM Wiki pattern, Claude Code) works through filesystem access. There is no native AI feature set in Obsidian itself as of 2026; community plugins fill this gap with varying quality.