The Future of Obsidian with CEO Stephan Ango and Andy Polaine
Based on Nicole van der Hoeven's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Stephan Ango (Kepano) anchors Obsidian’s long-term strategy in privacy, note longevity, and extensibility, with plain-text Markdown treated as the durable layer.
Briefing
Obsidian’s CEO Stephan Ango (Kepano) frames the product’s future around three non-negotiables—privacy, note longevity, and extensibility—arguing that the app’s long-term value depends more on plain-text files than on any single interface. The core pitch is simple: Obsidian should stay fast, local-first, and customizable, even if that means accepting rough edges like plugin “jank” and a steeper learning curve for newcomers.
Ango’s own entry point explains the philosophy. After years of using wiki-style note systems—starting with TiddlyWiki and earlier personal experiments—he says Obsidian arrived in April 2020 with the right combination of minimal design and practical speed: quick switching, prompts, and a file navigation approach that felt closer to a local-first “code editor” workflow. He emphasizes why local storage matters: cloud tools introduce latency and friction, while offline access enables uninterrupted writing, including on flights. That speed and control also connect to a broader belief that digital information must persist for centuries; Markdown, as a plain-text format, is treated as the durable layer that can outlive today’s apps.
From a leadership standpoint, Ango treats the growing “Obsidian clone” ecosystem as a healthy sign rather than a threat—so long as clients don’t drift into app-specific syntaxes that break interoperability. He calls the current moment a “Cambrian explosion,” where multiple tools can explore different ways of thinking. The risk, he says, is when innovation turns into fragmentation: too many proprietary extensions can make notes harder to move and harder to preserve.
A major trade-off shows up in how Obsidian handles plugins. Ango and Andy Polaine compare the plugin system to how modern mobile platforms make the whole device feel like the active app: Obsidian is fundamentally a Markdown-based editor and viewer, but powerful plugins can transform the experience. That freedom comes with downsides—new users may need to install many plugins, and community add-ons can feel less native. Still, Ango argues that extensibility is a core design principle, and “choosing to be bad” at cohesion is the price of letting users tailor workflows.
Looking ahead, the roadmap prioritizes “primitives” rather than bloated feature sets. Metadata is a key focus: improving how users add and query structured information, building toward easier use of DataView-style workflows without forcing everyone into SQL-like syntax. Publish and collaboration are also active areas, with improvements aimed at external sharing of entire vaults, shared vaults for internal teams, and single-note viewing through links. Task management is treated more conservatively—mainly making tasks more queryable and improving due-date handling—while Canvas and metadata work take precedence.
AI enters the conversation with a privacy-first constraint. Ango says community plugins already integrate GPT-style tools, but he prefers local-first, private AI where inference happens on the user’s machine. He points to the technical and hardware barriers of local training/inference and suggests Obsidian will likely watch plugin experiments before deciding what belongs in core.
Finally, Ango acknowledges Obsidian’s biggest usability gaps: sharing and collaboration remain harder than the solo note-taking experience, and accessibility feedback is ongoing. He ends by crediting the community for making the tool feel welcoming and collaborative—an asset he sees as central to Obsidian’s long-term adoption.
Cornell Notes
Stephan Ango (Kepano), CEO of Obsidian, ties the product’s future to three pillars: privacy, longevity of notes, and extensibility. He argues that plain-text Markdown is the durable layer that should survive app churn, while local-first performance keeps writing fast and reliable. Obsidian’s plugin ecosystem is treated as both its strength and its weakness: it enables users to transform the editor into different workflows, but can also create “janky” experiences and a higher setup burden. Roadmap priorities emphasize primitives like metadata (to make structured querying easier), plus publish and sharing improvements, while AI and task management are approached cautiously to preserve privacy and avoid feature bloat.
What “hook” pulled Stephan Ango into Obsidian, and why does it matter to his product philosophy?
Why does Ango treat Markdown (and plain text) as more important than the app itself?
How does Obsidian’s extensibility create both value and friction?
What does “primitives” mean in Obsidian’s roadmap, and what’s the current example?
How does Obsidian approach AI without breaking its privacy and local-first principles?
What sharing and collaboration problems remain, and how does the team think about them?
Review Questions
- Which three pillars does Ango name as Obsidian’s core design priorities, and how does each one shape product trade-offs?
- What arguments does Ango give for why plain-text Markdown should outlast Obsidian as an app?
- How do Ango and Polaine justify the plugin system despite user complaints about setup complexity and “jank”?
Key Points
- 1
Stephan Ango (Kepano) anchors Obsidian’s long-term strategy in privacy, note longevity, and extensibility, with plain-text Markdown treated as the durable layer.
- 2
Local-first performance is presented as a productivity advantage over cloud tools, especially for offline use and low-latency editing.
- 3
The rise of Obsidian clones is viewed as healthy “ecosystem diversity,” provided tools avoid drifting into app-specific syntaxes that harm interoperability.
- 4
Obsidian’s plugin model is a deliberate trade-off: it enables transformative customization but can create a less cohesive experience for new users.
- 5
Roadmap priorities emphasize foundational “primitives” like metadata and improvements to publish/sharing, rather than expanding into a bloated all-in-one suite.
- 6
AI integration is approached cautiously, with a preference for local-first, private inference aligned to Obsidian’s privacy principles.
- 7
Sharing is treated as a multi-problem area (publishing, shared vaults, single-note links, collaboration), each requiring different solutions under the same privacy constraints.