compare
TDengine vs VictoriaMetrics
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | TDengine | VictoriaMetrics |
|---|---|---|
| Language | C | Go |
| Licence | AGPL-3.0 | Apache-2.0 |
| Stars | 25k | 18k |
| Latest | ver-3.4.1.6 | v1.153.0 |
| Last push | 2026-10-06 | 2026-10-06 |
| Release cadence | about 28 days between releases | about 14 days between releases |
| Active contributors | 28+ commit authors on the default branch in the last 90 days | 54 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace InfluxDB. Alternatives to InfluxDB →
Full replacementTDengineTime series queried in SQL, with one table per device grouped under supertables.
PartialVictoriaMetricsAccepts the InfluxDB line protocol for writes, but is queried with MetricsQL.
TDengine
- ver-3.4.1.62026-04-303.4.1.6
- ver-3.4.1.02026-04-013.4.1.0
- ver-3.4.0.92026-03-023.4.0.9
- ver-3.4.0.22026-02-023.4.0.2
- ver-3.4.0.02026-01-083.4.0.0
TDengine
unsigned The latest release, ver-3.4.1.6, carries no signature GitHub could verify.
Loading the security report
VictoriaMetrics
unsigned The latest release, v1.153.0, carries no signature GitHub could verify.
Loading the security report