Tana alternatives, sorted by what you'd miss
Tana Outliner, the note app, now a separate product from Tana's meeting platform, is three ideas in one: an outliner, a structure system called supertags, and AI woven through both. Which alternative fits depends on which of the three brought you in, so the useful list is sorted by that, not by popularity.
Most "Tana alternatives" searches happen for one of two reasons. Either the app is more structure than the notes deserved, and every capture session turns into a schema design session. Or the notes have become work that matters, and the question of where they actually live, in whose cloud, exportable how, has started to feel less academic. Both are reasonable moments to look around. What to look at depends on what you'd miss.
Sorted by what you'd miss
| If what you'd miss is… | Look at | Why |
|---|---|---|
| Supertags, the structure attached to any node | Capacities, or Notion databases | Capacities builds around object types, the nearest native cousin of a supertag, compared in Capacities vs Obsidian. Notion gets you the same shape through databases, at the cost of living in a workspace, weighed in Notion vs Obsidian |
| The outliner itself, thinking in nested bullets | Logseq's file-based track | Still an outliner first, and it writes plain files you keep, covered in Logseq alternatives |
| The AI features around your notes | Read the fine print first | The AI in most note apps chats over your text and, at best, extracts into fields you defined. Where each app sits on that range is mapped in the best second brain apps roundup |
| Nothing, you want out of app-shaped notes entirely | Plain markdown files plus an agent | The argument for files over any workspace, Tana included, is markdown vs a database |
The question the whole category avoids
Tana, like most of its rivals, holds your notes in its own cloud. Export exists, and credit where due, an outline exports more cleanly than a tangle of database relations. But exporting is something you do on the way out, not a property you live with. The apps that store plain local files, Obsidian first among them, give you the property itself: the folder is yours, readable by anything, before and after you change tools.
The test that settles it. Could you open what you wrote last year without the app you wrote it in? If the honest answer is no, then whichever alternative you pick, you are choosing a landlord, and the comparison that matters is the lease.
What none of them fix
Here is the part the category will not say about itself. Supertags, object types, databases and backlinks are all ways for you to structure what you typed. None of them address the harder half: most of what you need on file arrives in mail and meetings you were already in. A few now transcribe the meeting or pull tasks out of the inbox; what none of them do is keep the project record current afterwards. A more elegant schema does not close that gap. It gives the gap nicer furniture. The pattern, and what it takes to actually close it, is laid out in why second brain systems fail.
Structure kept current for you
The book builds the other half: plain files you own, and an assistant that reads your mail and meetings and keeps those files current. About an hour to a working system.
Get the bookSee the finished loop running
The same idea at company scale: mail and meetings in, current records and drafted next steps out. A worked example, clickable end to end.
See the demo