nanotdbvsvictoriametrics
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| nanotdb | victoriametrics | |
|---|---|---|
| Score | 44/100 | 78/100 |
| Rank in category | #7 of 8 in Databases & storage | #3 of 5 in Time Series |
| GitHub stars | 141 | 18 115 |
| Stars, last 30 days | +0 | +268 |
| Stable releases, 12 months | 6 | 26 |
| Latest release | v1.4.0 · 28 May 2026 | v1.156.0 · 9 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | No | Yes |
| License | MIT | Apache-2.0 |
| Main language | Go | Go |
Which one should you pick?
victoriametrics scores 78/100 against 44/100 for nanotdb, so it is the safer default.
victoriametrics ships more often: 26 stable releases in the past year, against 6 for nanotdb.
If you want the quickest setup, nanotdb is easier to run; victoriametrics needs more configuration.
victoriametrics is growing faster right now (+268 stars in 30 days).
Key differences
- License: nanotdb is MIT, victoriametrics is Apache-2.0.
- Only victoriametrics ships an official Docker image.
- Platforms only nanotdb lists: Build from Source, Systemd.
- Platforms only victoriametrics lists: Ansible, Docker, Helm Charts, Kubernetes.
- Features only nanotdb lists: Aggregate queries, Built-in Dashboard, Crash Recovery, Dashboard editor and 9 more.
- Features only victoriametrics lists: Alerting via vmalert, Built-in web UI (vmui), Cardinality limiter, Deduplication of scraped samples and 10 more.
nanotdb details →victoriametrics details →
Swap a project
Keep nanotdb, compare it with
Keep victoriametrics, compare it with