ChartDBvsgrimmory
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ChartDB | grimmory | |
|---|---|---|
| Score | 74/100 | 69/100 |
| Rank in category | #7 of 40 in Database Management | #2 of 12 in Book Management |
| GitHub stars | 23 030 | 4 626 |
| Stars, last 30 days | +80 | +201 |
| Stable releases, 12 months | 5 | 19 |
| Latest release | v1.20.1 · 7 Apr 2026 | v3.5.0 · 21 Sept 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | AGPL-3.0 |
| Main language | Typescript | Java |
Which one should you pick?
ChartDB scores 74/100 against 69/100 for grimmory, so it is the safer default.
grimmory ships more often: 19 stable releases in the past year, against 5 for ChartDB.
If you want the quickest setup, ChartDB is easier to run; grimmory needs more configuration.
grimmory is growing faster right now (+201 stars in 30 days).
ChartDB details →grimmory details →
Swap a project
Keep ChartDB, compare it with
Keep grimmory, compare it with