ChartDBvstemporal
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| ChartDB | temporal | |
|---|---|---|
| Score | 74/100 | 83/100 |
| Rank in category | #7 of 40 in Database Management | #1 of 1 in Workflow |
| GitHub stars | 23 026 | 24 049 |
| Stars, last 30 days | +76 | +789 |
| Stable releases, 12 months | 5 | 11 |
| Latest release | v1.20.1 · 7 Apr 2026 | v1.30.8 · 12 Oct 2026 |
| Setup | Easy | Advanced |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | MIT |
| Main language | Typescript | Go |
Which one should you pick?
temporal scores 83/100 against 74/100 for ChartDB, so it is the safer default.
temporal ships more often: 11 stable releases in the past year, against 5 for ChartDB.
If you want the quickest setup, ChartDB is easier to run; temporal needs more configuration.
temporal is growing faster right now (+789 stars in 30 days).
ChartDB details →temporal details →
Swap a project
Keep ChartDB, compare it with
Keep temporal, compare it with