Tana Review: An Outliner-Based PKM Tool That Thinks in Graphs

I’ve been on a personal knowledge management odyssey that, looking back, spanned about seven years and five different tools. Evernote (2018-2020), Notion (2020-2022), Roam Research (2022-2023), Obsidian (2023-2025), and finally Tana (since March 2025). Each migration happened because the previous tool was missing something that mattered: Evernote had no structure, Notion required upfront database decisions, Roam had no typing system, Obsidian had no structured data layer. Tana is the first tool where I stopped looking for the next one — but that doesn’t mean it’s the right tool for everyone.

I received a Tana invite in February 2025 after being on the waitlist for about three weeks, and I’ve been using it as my primary thinking and organizing environment for over a year. Here’s what I’ve learned about the supertag system, the learning curve, and the honest trade-offs that the enthusiastic early-adopter community doesn’t always discuss.

How Supertags Changed How I Capture Information

The feature that made me switch from Obsidian is supertags, and I need to explain them carefully because the concept took me about two weeks to internalize. A supertag is a tag you apply to a node (a bullet point) that adds structured fields to it. If I tag a node with #task, Tana automatically adds fields for due date, priority, status, and assignee. If I tag a node with #meeting, it adds fields for attendees, date, decisions, and action items.

The critical difference from Notion databases is that I don’t have to decide upfront where something belongs. In Notion, I create a task database first, then add tasks to it. In Tana, I type freely in my daily notes — “discuss deployment timeline with infra team” — and when I later decide that bullet is a task, I tag it. The structure emerges from my tagging rather than being pre-designed. After three weeks of daily use, I realized this had eliminated a mental friction I hadn’t even named: the “where does this go?” pause before capturing anything.

Here’s a concrete example from my workflow. During a client call, I take notes in my daily page as unstructured bullets. After the call, I spend about 3 minutes applying supertags: #decision for decisions, #action-item for follow-ups, #contact for new people mentioned. Those tagged nodes now appear automatically in views I’ve built — my “Open action items” view, my “Decisions this month” view, my “People to follow up with” view. In Obsidian, I was manually copying action items from meeting notes into a separate task list, which took roughly 5-7 minutes per meeting. Supertags eliminated that duplication step entirely. Across 8-10 meetings per week, I’m saving roughly 40-60 minutes of manual cross-referencing.

The type inheritance system is what makes this scalable. A supertag can inherit from another supertag — I have #bug-report inheriting from #task, which means bug reports get all the task fields plus additional fields for severity, reproduction steps, and affected version. If I update the #task supertag (adding a “reviewer” field, for example), every descendant — tasks, bug reports, feature requests — inherits the change. This is genuine data modeling that you interact with through an outline, and it took me about three weeks of daily use before it felt natural rather than intellectually effortful.

The Outlining Interface: Power and Pain Points

Tana’s editor is node-based, which means every bullet point is a node with a unique ID that can be referenced from anywhere else in your workspace. Indentation carries semantic meaning — indenting a node under another creates a parent-child relationship that’s part of the graph structure and queryable. If I indent “Fix login timeout” under “Q3 Platform Improvements,” Tana understands that relationship structurally. I can then query “show me all tasks that are children of the Q3 Platform Improvements project node” and get a live, updating list.

This sounds like basic outlining, but the combination of structural indentation plus backlinks plus supertags creates a system that’s more powerful than it appears. Every node shows backlinks at the bottom — a list of every other node that references it. If I tag a meeting note’s action item as a #task, that task node now shows a backlink to the meeting note where it originated. I can trace the full provenance of any piece of information. In my first month with Tana, I discovered that roughly 40 percent of my action items had no clear origin — they were floating tasks in my old Obsidian system with no context about why they existed or who requested them. Tana eliminated that ambiguity.

The learning curve, however, is steeper than any PKM tool I’ve used. The difficulty isn’t the interface — the interface is clean and the keyboard shortcuts are consistent. The difficulty is mental. New users have to understand three overlapping organizational systems simultaneously: visual hierarchy through indentation, semantic relationships through linking and supertagging, and structured data through supertag fields and queries. Knowing which mechanism to use for which purpose isn’t obvious, and Tana’s documentation, while improving, still assumes a level of conceptual fluency that takes weeks to develop.

I was productive in Tana after about two weeks but didn’t feel fluent until roughly six weeks in. The first two weeks involved a lot of trial and error: applying a supertag when I should have used a link, using indentation when I should have used a supertag field, building queries that returned unexpected results because I’d structured nodes incorrectly. If you’re someone who wants a tool that’s immediately intuitive, Tana is not it. If you’re willing to invest 10-15 hours of learning for a system that genuinely respects the structure of your information, the payoff is real.

Comparing Tana to the Alternatives After Migration

Since I’ve used all four major competitors, here’s my honest comparison after migrating my full knowledge base — roughly 2,400 notes accumulated over seven years — into Tana over a two-month period.

Versus Notion: Notion remains stronger for anything you need to publish or share. Notion’s page-based document model produces clean, readable pages that non-technical stakeholders can navigate without training. Tana’s outline-based interface is harder to share — it looks like a nested outline to someone who doesn’t understand the tool, and the power features (queries, supertags) aren’t visible to viewers. I still maintain a shared Notion workspace for team documentation and use Tana as my personal thinking environment. The migration took about 15 hours total, mostly because I was selectively moving content rather than doing a bulk export-import, which Tana’s import tools don’t support cleanly.

Versus Roam: Tana is essentially Roam with a type system. Roam’s daily notes and bidirectional linking are present in Tana, but supertags and typed queries add a layer of structure that makes information more retrievable over time. In Roam, after 18 months of use, I had about 1,100 pages but struggled to surface specific information because everything was unstructured text with backlinks. In Tana, the supertag system means I can surface “all decisions made in Q1 2026” or “all action items assigned to me from meetings with the marketing team” without manual tagging. The cost is that Tana feels heavier than Roam — more structured, more deliberate, less suited to pure freeform writing.

Versus Obsidian: This is the comparison I get asked about most. Obsidian’s advantages are local-first plaintext files, offline access, and a plugin ecosystem with roughly 1,800 community plugins. If you need to work without internet, Obsidian is the clear choice — Tana requires a connection and caches limited content for offline use. If you rely on specific Obsidian plugins (Dataview, Templater, Kanban, Excalidraw), Tana doesn’t have equivalents for most of them. The trade-off is that Tana’s structured data layer is built into the core product rather than added through plugins that can break on updates. I spent roughly 3 hours maintaining my Obsidian setup each month — updating plugins, fixing compatibility issues, troubleshooting sync conflicts. Tana requires nearly zero maintenance since everything is server-side.

Where Tana Still Frustrates After a Year

Three limitations have persisted through my year of daily use that I think are important to name.

Mobile is Tana’s weakest link. The iOS app exists and works, but bullet manipulation — indenting, outdenting, moving nodes, applying supertags — is noticeably harder on a touchscreen than with a keyboard. The app also loads slower than the desktop web version, with a 3-5 second cold start that’s frustrating when you’re trying to capture a quick thought. I’ve defaulted to using Apple Notes for mobile capture and processing into Tana when I’m back at my desk, which defeats part of the “capture everything here” promise.

Offline access is the other major limitation. Tana is web-first and requires an internet connection. The mobile app caches some recent content, but it’s not a full offline experience — you can’t browse your entire knowledge base, create new nodes with supertags, or run queries without connectivity. As someone who works on flights roughly twice a month, this is the single biggest friction point in my workflow. Obsidian handles this flawlessly because everything is local plaintext. Tana currently doesn’t try to.

Export and data portability are a practical concern even if Tana isn’t trying to lock you in. You can export to JSON and Markdown, but the structured supertag data — field definitions, type hierarchies, query results — doesn’t cleanly translate to either format. If I needed to rebuild my knowledge base in another tool tomorrow, I’d lose roughly 40 percent of the structure I’ve built in Tana and face significant manual restructuring. This isn’t a malicious lock-in strategy — it’s that the typed graph structure Tana uses doesn’t have a standard interchange format — but it’s a real risk worth acknowledging if you’re considering migrating years of notes.

Who Should Invest in Tana

After a year of daily use, I recommend Tana to people who match this profile: you’ve tried at least two other PKM tools and found each missing something, you think in hierarchies and relationships rather than flat lists, and you’re willing to invest 10-15 hours of deliberate learning for a system that will pay off over months of use. Researchers, project managers, engineers, and writers who deal with interconnected information will find the structural power genuinely transformative.

Tana is a poor fit for users who want a quick, intuitive notes app that just works, who need robust offline access for frequent travel, or who depend heavily on mobile capture. For those use cases, Apple Notes, Notion, or Obsidian remain more practical choices. Tana is a thinking tool for people who are serious about structured knowledge, and it doesn’t pretend to be anything simpler.