Notion alternatives, sorted by how you actually work

The mistake people make leaving Notion is shopping for "a Notion alternative" as though that's one product category. It isn't. The tools people land on fall into three groups that share almost no design goals, and picking the wrong group is why the second migration usually follows within a year.

Work out which group you're in first. The tool choice inside a group is comparatively easy.

Group one: you want your notes as files on your disk

This is the largest group and the one Notion serves worst. The complaint isn't features — it's that your writing lives in someone else's database, in a format you can't open without them.

Obsidian stores everything as Markdown files in a folder you choose. That's the entire pitch, and it's a good one: your notes open in any text editor, sync through any file-sync service, and survive the company. The plugin ecosystem is enormous and genuinely load-bearing — most people's setup is Obsidian plus five or six community plugins.

Logseq makes the same local-files promise but organises around an outliner and daily notes rather than documents. If you think in bullets and journal entries, it fits better than Obsidian. If you think in pages, it won't.

The trade-off both share: collaboration is weak. These are single-player tools with sync bolted on. If two people need to edit the same note at the same time, you're in the wrong group.

Group two: you want the block editor without the platform

Some people like Notion's editing model and just want it open, self-hostable, or faster.

AFFiNE merges the document editor and the infinite canvas into one surface — the same content can be a page or a whiteboard. It's genuinely open source, and the ambition is visible.

AppFlowy is closer to a direct Notion clone: databases, boards, documents, self-hostable, Rust-based. If your requirement is literally "Notion but I control the server," this is the shortest path.

Anytype belongs here too, with a caveat worth knowing: it's local-first and end-to-end encrypted, but the desktop and mobile apps ship under a source-available licence, not an OSI open-source one. Only the underlying protocols are MIT. That matters if you chose it for the licence.

Group three: you want thinking software, not a workspace

The smallest group and the most opinionated. These tools aren't trying to replace Notion's project tracking — they're trying to make connected thinking faster.

Tana treats every node as a typed object with fields, so a meeting note can become structured data without you building a database first. It has a real learning curve.

Capacities organises around object types — people, books, meetings — rather than folders. Gentler than Tana, less powerful.

Neither is a good place to run a team's projects. Both are excellent places to think.

When you should just stay

Notion's weaknesses are real: performance degrades on large workspaces, offline is unreliable, and the AI features are competent rather than compelling. But if your team already has a working Notion setup and someone maintaining it, the migration cost is almost certainly higher than the annoyance.

The signals that genuinely justify moving:

• You need offline-first reliability and Notion has failed you on a plane or a bad connection
• You want your writing in files you own, and that's a values question you've already settled
• Your workspace has grown large enough that page loads are a daily irritation
• You're paying per seat for people who only ever read

If none of those apply, the honest answer is that you're bored, not blocked. Spend the migration weekend on something else.

The short version

Files on disk → Obsidian, or Logseq if you're an outliner person. Block editor you control → AppFlowy for a close clone, AFFiNE for the docs-plus-canvas bet. Thinking tool → Tana if you'll invest in learning it, Capacities if you won't. Team workspace with everything in one place → you're describing Notion, and you should probably keep it.