I love Obsidian. Here's why I'm building something different.

What Obsidian gets right

Let me start with genuine admiration. Obsidian is one of the best things to happen to personal knowledge management. It got the big things right:

• Local-first — Your notes are markdown files on your machine. No cloud dependency. No vendor lock-in. If Obsidian disappears, your files don't.
• Linking — Bidirectional links between notes create a genuine web of knowledge, not just a folder tree.
• Community — The plugin ecosystem is extraordinary. Whatever you need, someone probably built it.
• Privacy — No account required. No analytics. No data harvesting.

I use Obsidian. I respect the team behind it deeply. Everything I'm about to say comes from a place of "yes, and" — not "no, but."

The markdown ceiling

Obsidian's greatest strength is also its limitation: everything is a markdown file. This is powerful for text-first thinkers — writers, developers, academics who live in prose. But there's a large population of knowledge workers who don't think primarily in text.

Designers think in visual compositions. Researchers think in clusters of sources. Filmmakers think in sequences. Project managers think in dependencies. For all these people, markdown is a compromise — it captures the content but loses the spatial structure of the thinking.

Obsidian Canvas helps. It's a step toward spatial thinking. But it's an add-on to a text-first tool, not a spatial foundation. The canvas items are still pointers to markdown files. The spatial layout is a view, not the primary organizational structure.

Plugin fatigue

Obsidian's plugin ecosystem is its superpower and its curse. Want AI? Install a plugin. Want Kanban? Plugin. Calendar? Plugin. Spaced repetition? Plugin. Each one requires configuration, has its own update cycle, and may break when Obsidian updates.

After a few months, your Obsidian setup becomes a custom-built IDE that only you understand. It works beautifully — until it doesn't. A plugin conflicts with another. An update breaks your workflow. You spend an afternoon debugging your note-taking app instead of taking notes.

There's also the paradox of choice. With 1,500+ plugins, you can spend more time configuring your system than using it. The tool becomes the hobby.

What Depli does differently

Depli shares Obsidian's values — local-first, privacy-respecting, user-owned data — but starts from a different premise: space is the primary organizational structure, not text.

In Depli, every project lives on a canvas. Not as an optional view, but as the foundation. Modules — notes, sources, tasks, media, timelines — sit in this space as distinct entities with semantic meaning. A note module knows it's a note. A source module knows it holds references. They're not all markdown files wearing different CSS.

AI (Sona) is built in, not bolted on. It understands the spatial context — what's near what, what you've been working on, what connections you haven't noticed. No plugin installation, no API key configuration, no debugging someone else's integration.

Different tools for different minds

This isn't a "Depli is better" argument. It's a "different minds need different tools" argument.

If you think in text — if your natural medium is prose, if you love the purity of plain files, if you enjoy configuring systems — Obsidian is exceptional. It will serve you well for decades.

If you think in space — if you arrange ideas physically, if you need to see the shape of a project at a glance, if you want your tools to work out of the box without configuration — that's the gap Depli fills.

I'm building Depli because my brain doesn't think in markdown. It thinks in rooms, in clusters, in spatial relationships. And I suspect I'm not alone.

Obsidian is a registered trademark of Dynalist Inc. This article reflects our respect for their work and our different design philosophy.