The Quiet Defection Nobody Saw Coming
Obsidian does not have a marketing team talking about its growth. It does not publish press releases about user milestones or hire spokespeople to make noise at tech conferences. What it does have is a growing base of developers, engineers, and technical power users who have stopped paying for Notion, Confluence, and a half-dozen other SaaS note-taking and documentation tools – and are not going back.
The pitch is simple: your notes live on your machine, in plain Markdown files, forever. No subscription required to access your own writing. No vendor lock-in. No pricing page that changes every eighteen months.
That one feature – local-first file storage – has quietly become a wedge issue inside the productivity software market.
Why Developers Stopped Trusting the Cloud for Personal Knowledge
The frustration driving developers toward Obsidian is not primarily about price, though price does come up. It is about control. When a SaaS tool holds your notes, your documentation, your research, and your institutional knowledge inside a proprietary database, you are betting that the company stays solvent, keeps its pricing reasonable, and never decides to sunset the product. That is a lot of trust to extend to a startup – or even to a large company whose priorities shift.
Notion, for all its visual polish and collaborative features, stores data in a format that does not export cleanly. Getting your notes out means using an export function that produces a folder of half-broken Markdown files with internal links pointing to nothing. For a developer who thinks carefully about data portability, that is not a minor inconvenience – it is a disqualifying flaw. Obsidian’s vault, by contrast, is just a folder of .md files. You can back it up with Git, sync it with any file service, open it in any text editor, and read it thirty years from now without needing to log into anything.
There is also a plugin ecosystem that has taken on a life of its own. The Obsidian community has built hundreds of plugins – calendar views, Kanban boards, spaced repetition systems, graph-based knowledge mapping – that extend the tool far beyond basic note-taking. The same engineers who resist vendor lock-in are, by nature, the same people who enjoy building or modifying their own tools. Obsidian hands them the keys.
What This Means for the SaaS Productivity Stack
The shift is not about Obsidian beating Notion in a feature checklist comparison. Notion still wins on collaboration, databases, and team wikis. What Obsidian is carving out is a specific category: the personal knowledge management layer that lives below the team layer, where an individual developer keeps their notes, their learning logs, their architecture diagrams, and their project context. That layer used to default to Notion or Confluence because those were the tools already in the organization. It is now defaulting, for a growing number of technical users, to Obsidian.
The downstream effect on SaaS platforms is subtle but real. When a developer does not use Notion for personal knowledge, they are less likely to advocate for it inside their organization. The bottom-up adoption model that made tools like Notion and Slack so effective at infiltrating enterprise environments depends on individual users loving a product and spreading it inward. Developers who love Obsidian are not spreading Notion. They are, at most, tolerating it for team tasks while quietly building their real knowledge base somewhere else.
Obsidian also runs on a one-time purchase model for its commercial license, with optional paid sync and publish features. That pricing structure is almost aggressively anti-SaaS in a market where monthly subscriptions are the default. Some companies trying to build sustainable software businesses would call this a liability. Obsidian’s user base calls it the point.
The Loyalty Problem Big SaaS Cannot Easily Fix
There is no straightforward response available to Notion or Confluence here. They could offer local storage options, but doing so would undermine the cloud-sync architecture their collaboration features depend on. They could lower prices, but the developers moving to Obsidian are not primarily leaving over cost – they are leaving over philosophy. Building a feature that says “we trust you to own your data” is not something a company can bolt onto an existing product without rethinking core assumptions about how the product works and how it makes money.
Obsidian’s growth also benefits from being largely invisible to the analysts and press who track SaaS market share. Because it does not operate on a subscription model and does not publicize user numbers, it does not show up in the dashboards where enterprise software competition gets measured. The tool can gain traction inside engineering teams without anyone in a procurement department noticing. By the time a CTO realizes half the senior engineers have migrated their personal knowledge management off Notion, the habit is already formed.
The real tension at the center of this story is not whether Obsidian can challenge Notion commercially – it probably cannot, and its business model suggests it is not trying to. The tension is whether SaaS productivity tools built on proprietary cloud storage can hold the loyalty of users who have started to think seriously about what happens to their data when the business relationship ends. Obsidian did not create that anxiety. It just built the most convenient exit ramp available.
