Tana vs Logseq - in-depth comparison of features and use-cases
The fast-evolving landscape of digital knowledge management leaves users with a number of choices as to where they would like to manage their information. For many, Logseq and Obsidian come to mind as leading contenders. But Tana has gained an impressive following since its release at the end of September 2022, over two years behind Logseq and Obsidian.
So what's special about Tana, and why are people excited about it?
It seems like many users want one tool to rule them all, and Tana offers glimpses of this promise. However, in the real world, there will always be trade-offs.
This article will explore the similarities and differences between Logseq and Tana, and expand on Tana's distinguishing features. We'll also look at where each of the tools excels, and discuss the best use cases.
After reading this, you'll hopefully have a better understanding of which tool is right for you; or perhaps a better outcome, how you can leverage the tools in the areas that they're strong.
How are Tana and Logseq similar?
Both are linked knowledge graph builders: The traditional file and folder paradigm of desktop computing uses a location-based approach to organize information, requiring users to navigate complex hierarchies and folder systems to input and retrieve information. This limits the accessibility of information and slows down users working in these systems. Knowledge graphs organize information based on relationships between different pieces of information, rather than the location of those pieces of information. Information therefore appears in multiple places simultaneously, based on the relationship or association. This encourages bottom-up building of information structures, and makes input and retrieval of information effortless.
Both are outliners: Outliners structure information in a branched tree of information. This allows you to breakdown your thinking into granular building blocks.
Similar interfaces and UX elements: Both Logseq and Tana feature multi-panel layouts, with a left sidebar predominantly used for navigation, and a main panel which accommodates opening up multiple instances of information in your workspace. The keyboard shortcuts are similar, facilitating easy navigation and information manipulation. Both have a hypertext-like interface that enables you to access information quickly by clicking on linked text or bullet points.
Focus on daily journal-first / node-first approach: The day node is a new paradigm which provides a standard point of departure to capture thoughts, meeting notes, tasks, and whatever other information you need to manage. Information then flows to where it is required through the addition of links and/or metadata.
Powerful information retrieval: In modern information systems, search is more powerful and more reliable than browsing. (Side-note: This is partly why Google became such a dominant player in the internet age, because they focused on the speed of finding what the user wanted, rather than creating ontological systems to predict where information should belong. Note the similarity of the latter, slower approach to using folders and files). Both Logseq and Tana possess powerful information retrieval capabilities. Querying and search functionalities are readily accessible in both applications, allowing users to efficiently locate specific pieces of information.
Overview of differences between Logseq and Tana
Although there are clear similarities, the tools have very different implementations. Before getting into Tana's standout features, it's worth looking at some core implementation differences.
File storage: Logseq follows a local-first approach, which means that files are stored on your PC in Markdown or OrgMode format. They offer a sync service that allows you to synchronize your data with a cloud server, although this feature is currently available only to financial supporters of Logseq via OpenCollective. Tana on the other hand, is a cloud-based web application which uses Firebase on the back-end. There is no dedicated desktop application or offline functionality, although there are plans to have both eventually.
Operating systems: Logseq is compatible with various operating systems, including iOS, Mac, Android, Windows, and Linux. While it is not available in the Android Play Store, you can download it from GitHub and install it on your Android device. Tana is currently only available as a web-app, and has a Tana Capture app for iOS and Android app. (This is not a fully fledged version of Tana, but rather a companion app to capture information on the go.)
Licensing: Logseq is an open-source tool, so the code base is openly accessible. This fosters a collaborative environment where users can contribute to the development and improvement of the app, although most of the work is done by a core team. Tana on the other hand, is a proprietary product.
Pricing: Logseq's local-first version is free forever. However, many users contribute to the project on a monthly basis via OpenCollective to support its ongoing development. There are plans to introduce paid services in the future, e.g. Sync and Publishing. Tana is currently available for free in its early access release. It is expected to have a price of $10 per month or $100 per year when it launches, although there are plans for a freemium tier.
Some user interface differences: The concept of a workspace in Tana is equivalent to a graph in Logseq. It serves as the main organizing repository for your information. When it comes to tagging and referencing, Tana uses the
@symbol, which is similar to the use of square brackets ([[]]) and hashtags (#) in Logseq. The#symbol in Tana has a different purpose and functionality altogether, which brings us to the next part of this article.
Distinguishing features in Tana
The introduction of supertags
The most notable introduction in Tana is the concept of supertags, which is implemented using a hashtag. In Logseq, using a hashtag to tag something is equivalent to using square brackets to create a backlink. It simply means this 'this note or block is related to this , which is equivalent to attaching a concept to the block. The block will then show up in the Linked References section, if one navigates to the tagged page.
Tana elevates the hashtag symbol to create supertags. Supertags act as high-level categories or definitions that describe what nodes are. A helpful way to remember this is to think of a supertag as saying 'this node should go into this database'. (For those with a programming background, supertags function as classes.)
Supertags facilitate improved organization of information by making structure easily available to users. You can easily add relationships to another nodes of information, or build rich metadata with user-defined fields. This is particularly useful for defining ontologies, i.e. structured descriptions of systems. They also facilitate more complex schemas by allowing you to 'extend' other supertags. Users can then define basics structures that are inherited throughout their workspace.
Let's use the example of a meeting to show the basic structural difference. In Logseq, you would hypothetically add '#meeting #ProjectName #John' to a block, or perhaps [[meeting]] [[ProjectName]] [[John]]. In Tana you simply add '#meeting' to the node. Any predefined fields you have for a meeting, such as Project and Attendees automatically appear below the node, making it easy to add the necessary details. This approach ensures consistent structuring of information. A good template workflow with properties in Logseq allows for similar structure, but the implementation of fields in Tana is considerably more powerful, as the fields are configured in the supertag itself and can be easily updated.
Other examples: if the node is...
a
#person, let me input their role and who they report to.a
#task, let me input the related project and the priority#documentation, let me input the person responsible for updating it and the relevant parties. (Note that all of the fields have to be defined by the user)
'Everything is a node'
A major difference in Tana is the idea that 'everything is a node.' This can be a bit challenging to grasp initially, especially if you're used to the pages and blocks data model in Logseq. In Logseq, pages are a special type of block with elevated status, serving as the nodes in your knowledge graph. Tana collapses this differentiation, allowing you to easily add rich meta-data and relationships to each and every unit of information in your workspace.
Custom views for information built-in
Tana offers a number of different views which make it easy to access and manipulate information. In addition to the powerful standard list view, Tana offers table, cards, tabs and calendar views. The calendar view is particularly impressive, and hints at a future where one need not leave the application to work in a separate calendar. Whilst there are various plugins that allow for different views in Logseq, they are not native to the application. The user experience in Tana therefore feels more unified, and the ability to traverse and manipulate multiple levels of information simultaneously is powerful.
Multi-player collaboration
Tana allows for multi-user collaboration in a single workspace. The interface enables seamless sharing of information from personal workspaces into collaborative workspaces, and vice-versa. In Logseq, multi-player real time collaboration is not currently available as a feature. You can collaborate using a shared GitHub repository, but the setup and maintenance is considerably more complex.
Where each of the tools stand out
Tana and Logseq are both powerful in their own right, but there are some clear standout areas that are worth drawing attention to. Some of these points may have been called out in previous sections, but I'm including them here to emphasize their importance.
Where Tana stands out
Impressive user interface and user experience: Tana's interface feels subjectively cleaner and more refined. The overall look and feel is more polished than Logseq, and it feels more unified. The ability to manipulate information via the command line ( Ctrl/Cmd + K) is particularly slick.
Live searches (or queries) are more user-friendly: Live searches are easily accessible, most notably via the command line via natural language processing. You can also start a node with a
?to create a search node. There's a handy visual query builder, which allows users to easily filter, group and sort search results via a simple interface. I don't use many advanced queries in Logseq, but for some use-cases they are necessary. However, in Tana you don't have to wade through the intricacies of Logseq's complex Datalog query language to get the most value from your workspace.Implementation of fields (meta-data / attributes / properties): Tana will be the first to say that properties in Logseq do not equal fields in Tana. However, it is a helpful analogy. Like fields, properties specify the nature of relationships between information and add more meaning and structure to the links. But many Logseq users don't even use properties. They're unaware of the power, and admittedly it is complex to update / manipulate properties. Tana brings this functionality into every user's grasp with their elegant implementation. Simple functionality such as selecting from pre-existing values in a table view, or bulk updating nodes are not even possible in Logseq. Furthermore, there are some neat UX tricks, such as being able to hide fields based on certain conditions.
Impressive user onboarding and interaction: Tana have prioritized documentation and user learning. They're highly engaged with their community, and have co-ordinated a team of Tana Navigators (engaged community members) and Ambassadors who create content. The team is great at communicating updates, and also co-ordinating with their Ambassadors so that end users have reference materials. The engagement in the forum from all team members is impressive.
Recursive searching: Tana has introduced semantic functions into fields, which enables users to define how different nodes of information are rolled up into other nodes. This allows for powerful searching through different levels of information in your workspace.
Where Logseq stands out
Offline access: When you want to go all Henry David Thoreau on the world, you can take your laptop (and solar power source) and take your Logseq notes with you. Tana are working on offline capabilities, but at the moment this is not available, much to the chagrin of some users. (Worth another side note here... I always find it strange how people voice their feedback when they're not paying anything for a tool. If you're not happy, surely you can take your problems elsewhere?)
Extensibility and ownership of Markdown: Being able to write in Markdown enables you to access your notes across tools like Obsidian and VS Code. This ensures long-term note ownership and longevity of your notes. You can export and import Markdown with Tana, but this lacks the seamless interoperability with other applications.
Extensibility via extensions: The 'tools for thought' / personal knowledge management community love extensions. It allows users to cater to a broad set of requirements that are beyond the scope of the core development team. Tana is still a closed ecosystem, although this may come in the future.
Robust feature set for PKM: The ability to annotate PDFs and access an internal whiteboarding feature within the application are big benefits in the context of personal knowledge management. Again, it's the unification of information in a single source of truth that gives so much power.
Long-form writing: Logseq is not quite Obsidian, but it is still much easier to write long-form content in Logseq than in Tana. You can simply enter document mode by using the shortcut 't d' when you're not editing a block, and write as if you're writing in another text editor. The general text editing experience also feels cleaner as there are no fields getting in the way. The differentiation between blocks and pages also lends itself to working more fluidly with large amounts of information.
Privacy: Logseq has end-to-end encryption ('Trust No One'), which is highly desirable for users who would like the contents of their second brain to be completely inaccessible to others. (The Tana team can still access your content in an emergency with your permission, but some people do not trust such security protocols).
Where do I see the tools being used?
Project management and tracking workflows-> Tana: Tana provides powerful functionality to structure information, yet with ample flexibility to define customs workflows. Sprint planning, content pipelines, and OKRs can all be easily configured in Tana. The ability to access and manipulate information through multiple views also makes this an easy choice. In Logseq, blocks are limited to a set of statuses: WAITING TODO (LATER) DOING (NOW) DONE CANCELLED. Whilst you can define your own by using properties or a plugin, they don't transfer seamlessly throughout your workspace. Decision tracking, habit tracking and simple customer relationship management (CRM) trackers are therefore more easily configured in Tana.
Personal knowledge management ->Logseq: Knowledge snippets don't need much structure. Using Logseq as a dumping ground or digital commonplace book for my thoughts removes friction from the process. Tagging pages and blocks by concept comes naturally, rather than having to go through the rigmoral of adding a supertag with an associated
TopicsorConceptsfield. It also feels natural to retrieve and filter information using the Linked References sections, rather than having to use Live Searches all the time. I have confidence that information entered in Logseq will show up in the right place. I also like the differentiation between pages and blocks, as pages feel like a more 'concrete' place where I can move information to.Asset management -> Logseq: Logseq handles non-text files easily. Audio, video, pictures, and PDFs can all be opened in the app. I have gigabytes of personal files in my Logseq folder, and there has been no perceived performance loss. In Tana, I have only as of very recently been able to add pictures, and they take a long time to load when I want to access them. I imagine that adding gigabytes of assets may slow the performance, although this is hypothetical.
Collaborative knowledge management -> Tana: Being able to reference information in other graphs, and seamlessly share information from a personal workspace to a shared workspace are major wins. For this reason it also might make sense to take meeting notes in Tana.
Writing -> probably Logseq: Whilst I like to start my writing workflow in Tana with a template that prompts my thinking and makes sure that I articulate my thoughts clearly, I find the fluidity of writing in Logseq to be more user friendly. The interface feels more conducive to long-form writing, as discussed above.
The verdict? Personally, both Tana and Logseq add value to my workflows.
In general, I find that 'both and' approaches are usually best when navigating a complex world, and with software it is no different. Perhaps you're in a situation where you don't need all the functionality discussed for each of the tools above, in which case it makes sense to double-down on one. But for me, having both in my toolkit is powerful.
I consider Logseq to be my digital commonplace book. It's a scratchpad, providing fertile soil to plant and grow thoughts. The loose structuring of information feels like it will grow with me in the long-term. There is a certain peace that comes with the knowledge that the Markdown files will always be accessible, and that no-one can ever access my intimate journals.
But when it comes to making things happen in the world, a little bit of structure goes a long way. The way that Tana makes this structure available to users is unparalleled. Supertags seem so simple, as to be trivial. But maybe that's the truth about great design? Tana is a pleasure to use, and it's transformed the way that I manage my everyday work.
Unfortunately there is no definitive answer or 'holy grail'; every user has to consider the different trade-offs of working within the different tools. Hopefully this guide sheds some light on which setup will work best for you.