TriliumNext/Trilium

Prefer this fork only if its API/website/localization changes are directly useful to you. If you mainly want the full upstream feature set with low maintenance risk, upstream is the safer choice.

Choose this fork only if its specific rendering/UI changes are important to you. If you want the broadest compatibility, fastest fixes, and least maintenance risk, upstream is the safer choice.

Prefer upstream unless you specifically need this fork's older baseline or its small local patches. This fork is materially behind, looks unmaintained, and is best treated as a custom snapshot rather than a healthy alternative distribution.

Choose this fork if you want a worldbuilding-focused Trilium variant with draft hiding and RPG templates. Choose upstream if you need the full, mature Trilium feature set, documentation, and broad platform coverage.

Choose this fork if you want the localized/command-palette/preview improvements and can tolerate a large upstream lag. Choose upstream if you want the broadest feature set, latest fixes, and easiest long-term maintenance.

Prefer upstream unless you explicitly need this historical snapshot; this fork shows no added value and is significantly behind current upstream.

Choose this fork only if the presentation/slide workflow is the main requirement. If you want a stable, broadly current Trilium install, upstream is the safer choice.

Prefer this fork only if its API/documentation or localized deployment work matches your needs. If you want the full upstream feature set and current fixes, upstream is the safer choice.

Choose this fork only if you specifically need its older, customized behavior. For most adopters, upstream is the better default because it is actively maintained and far ahead in fixes and features.