TriliumNext/Trilium: A Hierarchical Note Base That Grows Past 100,000 Notes

What TriliumNext/Trilium Actually Solves

The project is a community continuation of the original Trilium, which was developed by Zadam. The README explains that Zadam gave the repository to the community project at TriliumNext. This matters because it means the project has a governance model that is not tied to a single vendor. The last push was August 2026, and recent releases are frequent, with v0.105.0 released on that date. So the project is actively maintained, but it is not a commercial product with a support team. You are adopting a community-run tool, which has implications for long-term stability and upgrade paths.

The Architecture: A Tree, Cloning, and Attributes

The note types go beyond plain text. There are rich WYSIWYG notes with tables, images, and math. There are code notes with syntax highlighting. There are canvas notes based on Excalidraw for sketching diagrams, relation maps for visualizing connections between notes, note maps for showing links, mind maps based on Mind Elixir, and geo maps with location pins and GPX tracks. This is a wide range of note types, which can be useful but also adds complexity. Each note type has its own editor and data model, and you need to understand when to use which. The README does not explain the trade-offs between these types, so you will need to consult the documentation to see if the canvas or mind map meets your needs or if it is just a novelty.

Getting It Running: Installation and Configuration

Synchronization is a separate component. The README mentions self-hosted sync server and third-party services for hosting a sync server. This is not a cloud sync like Evernote. You either run your own sync server or pay a third party. The documentation has a synchronization page and a cloud hosting page. This means the setup cost is higher than a typical note app. You need to maintain a server process, handle backups, and manage network access. For a single user on a single device, you might not need sync at all. But if you want to access your notes from multiple devices, you must set up the sync server. The mobile frontend is touch-optimized, but it is a web frontend, not a native app. So offline mobile access is not guaranteed; you need a stable connection to your sync server.

The Real Limitation: Sync, Mobile, and the AGPL License

The mobile frontend is a web app, not a native app. The README says it is touch-optimized, but it depends on a connection to the server. If you are offline, you cannot access your notes unless you have set up some offline caching, which is not mentioned in the README. This is a significant gap for users who need to read notes on a plane or in a remote area. The AGPL-3.0 license is another consideration. The README lists the license as AGPL-3.0. This is a strong copyleft license. If you use Trilium as a hosted service for others, you may be required to release your modifications to the source code. This is not a problem for personal use, but it is a serious constraint for organizations that want to embed Trilium into a proprietary product. The README does not discuss licensing implications, but the license is clear. You should consult a lawyer if you are unsure how AGPL affects your use case.

Alternatives: Evernote, Markdown Files, and the Difference in Approach

Another alternative is a wiki system like MediaWiki or DokuWiki, but those are server-based and not designed for personal note-taking. The README does not mention them, but they are relevant if you need collaborative editing. Trilium does not appear to support real-time collaboration; it is a single-user system with sync for multiple devices, not multiple users editing the same note simultaneously. The README mentions sharing notes to the public internet, but that is publishing, not collaborative editing. So if you need to work on notes with a team, Trilium is the wrong tool. You would be better off with a wiki or a collaborative document tool like Google Docs.

Maintenance and Upgrade Cost

The license is AGPL-3.0, which has implications for redistribution and modification. The README does not provide legal advice, but the license is clear: if you modify the source and distribute it, you must make your modifications available under the same license. For personal use, this is not a burden. For a company that wants to use Trilium as a backend for a commercial product, this could be a deal-breaker. You should verify that the AGPL terms are acceptable for your organization before building on it. The project also has a REST API, which is called ETAPI in the documentation. This allows automation, but the API is part of the AGPL codebase, so any scripts you write that interact with the API are not affected, but if you modify the server code, you are. This is a nuance that many users overlook.

Editorial conclusion

Adopt TriliumNext/Trilium if you need a self-hosted, hierarchical note base that can scale past 100,000 notes and you are comfortable with the AGPL-3.0 license and the effort of running your own sync server. Do not adopt it if you require native mobile offline editing, a managed cloud service, or a permissive license for commercial embedding. Before committing, verify the current migration path from older Zadum/Trilium versions, test the sync server under your network conditions, and confirm that the scripting API covers the automation you plan to build. The project is actively maintained with recent releases, but its community-driven nature means you should check the documentation for any breaking changes before each upgrade.

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes