TriliumNext 0.91 Shift: Open-Source Note-Taking Economics

The release of TriliumNext 0.91 in November has disrupted the economics of hierarchical note-taking by offering a fully open-source, self-hosted alternative that challenges the proprietary status quo. Knowledge workers who value data sovereignty are now weighing this new tool against established platforms like Obsidian and Logseq, which have dominated the bidirectional linking market for years. The core appeal lies in the ability to run a personal knowledge base on local infrastructure without relying on external servers or subscription fees. This shift forces a re-evaluation of how users manage their "vaults," as the cost of entry drops to zero while the technical barrier rises slightly for those unfamiliar with server administration.

Obsidian remains the benchmark for flexibility, operating on a folder of text documents known as a vault where each note is a standard Markdown file. Its graph view visualizes connections between notes as nodes and edges, facilitating the discovery of relationships that might otherwise remain hidden in isolation. However, Obsidian is proprietary software, meaning users must trust the company with their data integrity and future development roadmap. The application launched version 1.0.0 on October 13, 2022, after two years of beta testing, and introduced its Canvas feature in December of the same year for spatial note arrangement. While the plugin ecosystem allows for extensive customization, reviewers have noted that useful features often require significant time to tailor, creating a steep learning curve for beginners who find Markdown challenging.

Self-Hosted Economics vs. Proprietary Flexibility

TriliumNext 0.91 addresses the primary complaint about Obsidian: the lack of true open-source freedom. By allowing users to self-host their instance, it eliminates the risk of vendor lock-in associated with proprietary formats. In contrast, Obsidian files are saved in generic Markdown language, which ensures transferability to other systems, but the application itself remains closed source. This distinction matters for organizations concerned with long-term data preservation and security. The economic argument favors self-hosting for power users who can manage their own hardware, as it removes recurring subscription costs entirely. For individual users, however, the maintenance overhead of keeping a server updated may outweigh the financial savings.

Logseq offers another perspective, focusing on outliner-based bidirectional links within an open-source framework. It competes directly with Obsidian in the personal knowledge management space but approaches organization through a different structural lens. The choice between these tools often comes down to whether a user prefers a canvas-based spatial layout or a linear, block-based hierarchy. Obsidian’s Bases plugin enables database-like views of notes, customizable to look like dynamic tables or maps, adding a layer of structure that pure outliners lack. Users can also leverage community-developed plugins to extend functionality, though this requires navigating a complex ecosystem of third-party code.

The decision hinges on whether you prioritize immediate usability or long-term control. Obsidian provides a polished experience out of the box, with end-to-end encryption for sync and a vast library of themes. TriliumNext demands more technical effort but grants complete ownership of the data stack. If your workflow relies heavily on specific community plugins that only exist for Obsidian, switching costs will be high. Conversely, if data privacy is your non-negotiable requirement, the self-hosted model offers a level of assurance that no commercial cloud service can match. Which trade-off aligns better with your current workflow?