JoplinvsTrinity
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Joplin | Trinity | |
|---|---|---|
| Score | 83/100 | 57/100 |
| Rank in category | #2 of 81 in Notes & Editors | #60 of 209 in AI Agents |
| GitHub stars | 56 922 | 713 |
| Stars, last 30 days | +442 | +2 |
| Stable releases, 12 months | 18 | 4 |
| Latest release | v3.7.22 · 28 Oct 2026 | v1.0.0 · 20 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Other | Apache-2.0 |
| Main language | Typescript | Python |
Which one should you pick?
Joplin scores 83/100 against 57/100 for Trinity, so it is the safer default.
Joplin ships more often: 18 stable releases in the past year, against 4 for Trinity.
If you want the quickest setup, Joplin is easier to run; Trinity needs more configuration.
Joplin is growing faster right now (+442 stars in 30 days).
Joplin details →Trinity details →
Swap a project
Keep Joplin, compare it with
Keep Trinity, compare it with