The Quiet Defection From Obsidian
Obsidian built its reputation on one promise: your notes, your files, your control. The app’s plain-text, local-first philosophy attracted a specific kind of user – the kind who spends weekends building plugin stacks and mapping knowledge graphs. For a few years, that was enough to make Obsidian the gold standard for serious note-taking. Now Craft is eating into that base, not by competing on ideology, but by competing on experience.
Craft has spent the last two years quietly adding the structural and linking features that Obsidian loyalists considered non-negotiable. Backlinks, nested pages, block references, document hierarchies – features that once required Obsidian plugins and manual configuration now ship natively inside Craft’s polished interface. The result is a tool that no longer asks power users to choose between capability and design.
The migration is happening, and it’s not small.
What Obsidian Got Right – And Where It Started Losing People
Obsidian’s core architecture is genuinely brilliant. A local vault of Markdown files means your notes are portable, readable by any text editor, and entirely under your control. No subscription locks your data behind a paywall. The plugin ecosystem – with hundreds of community-built extensions – turned the app into whatever each user needed it to be. For developers, researchers, and writers who treat their notes as infrastructure, that flexibility was the whole point.
The problem is that flexibility has a cost. Setting up Obsidian to function at a high level requires real configuration work. Getting templates, daily notes, graph views, and sync working together means installing and maintaining multiple plugins, each with its own update cycle and potential for breaking changes. New users face a steep onboarding cliff, and even experienced users spend meaningful time on maintenance rather than writing. The app never pretended otherwise – it was built by and for people who enjoy that process.
That assumption is now a liability. A growing segment of technical users – people who want power without the overhead – has started looking for something that does the structural work by default. Craft is positioned directly in that gap. It offers a document model sophisticated enough for complex projects, with linking and nesting behavior that covers most of what Obsidian’s core functionality provides, without requiring a single plugin to get there.
What Craft Is Actually Building
Craft’s approach to note-taking is block-based rather than purely linear. Each piece of content – a paragraph, a checklist, a code block – exists as a discrete unit that can be moved, nested, linked, or referenced independently. This matters because it changes how information connects. Instead of managing a folder structure manually or relying on tags to surface related content, users can build genuine hierarchies and cross-document references from the moment they start writing.
The backlink system Craft introduced brought the feature most associated with Obsidian’s “second brain” appeal directly into a native, cloud-synced app. Users can now see which documents reference a given note and navigate between them without leaving the keyboard or opening a settings panel. The experience is closer to Notion’s linked databases than to Obsidian’s graph view, but it solves the same underlying problem: how do you find and connect ideas you wrote three months ago? Craft’s answer is fast, visual, and requires no configuration. That’s a different answer than Obsidian gives, but for a lot of users, it’s a better one.
Craft also made a bet on Apple’s ecosystem that is now paying off. Deep integration with iOS, macOS, and iPadOS – including native widgets, Shortcuts support, and Apple Pencil compatibility – means the app behaves like a system application rather than a cross-platform web wrapper. For users already living inside Apple’s stack, that frictionless integration removes the last reason to tolerate Obsidian’s comparatively clunky mobile experience. Obsidian’s mobile app functions, but it has never felt like a first-class product. Craft’s does.
The Business Model Tension Nobody Talks About
Obsidian is free for personal use, with paid tiers for sync and publishing. Craft runs on a subscription model, with a free tier that covers basic use and a paid plan that unlocks sharing, version history, and advanced features. For the kind of power user who previously chose Obsidian partly because it cost nothing, moving to Craft means accepting a recurring bill. That’s a real friction point, and Craft knows it.
What softens that friction is the maintenance math. Obsidian’s free price comes with an invisible cost: the time spent managing plugins, troubleshooting sync issues, and rebuilding workflows when updates break things. Craft’s subscription buys time back. For users who bill by the hour or simply value their attention, that trade-off increasingly makes financial sense. The subscription isn’t just paying for features – it’s paying for a system that maintains itself.
The comparison to other tools shifting their user bases is instructive – Attio pulled a similar move against HubSpot by offering structural flexibility without configuration overhead, and the dynamic playing out in note-taking apps follows a similar pattern. The product that lowers the barrier to a previously expert-only workflow tends to win the next wave of users, even when the original expert tool remains technically superior in specific ways. Craft is betting that “technically superior for people who do the work” is a smaller market than it used to be.
What This Means for Obsidian’s Next Move
Obsidian isn’t standing still. The team has shipped consistent updates, and the plugin ecosystem continues to grow. The app’s open format and local-first philosophy have real adherents who will not move regardless of what Craft ships. But the middle of the market – technical users who adopted Obsidian for its power and tolerated its friction – is exactly where Craft is applying pressure, and Obsidian has no obvious answer that doesn’t compromise the architecture its existing users chose it for. Adding polish means adding abstraction. Adding abstraction means becoming a different product. That tension doesn’t resolve cleanly, and Craft is counting on it staying unresolved long enough to convert the users caught in the middle.
