TDengine is designed for industrial enterprises and organizations using traditional data historians or legacy industrial IoT platforms.
- Home
- Developer Tools
- Time-Series Databases
Best Time-Series Databases 2026
When your data is organized around time, database choices can hinge on how it arrives, how it is queried, and how long it stays available. Compare deployment and ingestion methods with query languages, horizontal scaling, retention policies, and SQL support. Free-plan availability and paid-from pricing offer further points of comparison. GreptimeDB, InfluxDB, and TimescaleDB lead the ordered entries, with QuestDB and TDengine also near the top. Consider your deployment approach, expected data flow, and querying needs, then weigh the listed scaling and retention capabilities against them.
InfluxDB
InfluxDB 3 may suit teams handling timestamped data for industrial operations, observability, or AI applications.
WebWindowsMac+3VictoriaMetrics
VictoriaMetrics may suit teams needing metrics monitoring and longer-term metrics storage across on-premises, hybrid, or cloud deployments.
WebWindowsMac+3Apache IoTDB
IoT teams that need a self-hosted time-series database for edge-cloud deployments may find IoTDB relevant.
WebWindowsMac+3GreptimeDB
GreptimeDB is suited to teams handling time-indexed observability or IoT data who want SQL and PromQL querying.
AndroidWebWindows+4DolphinDB suits teams that need real-time analytics or stream processing, including those working in finance, energy, transportation, manufacturing, or scientific…
QuestDB may suit teams handling time-series data in low-latency settings, including capital-markets firms, digital-asset businesses, energy operators, aerospace…
CnosDB may suit teams collecting and querying time-oriented data for the listed IoT, industrial, vehicle, or IT operations uses.
LinDB suits teams building IoT or IT operations monitoring systems that need to store and analyze numeric time-series metrics.
Warp 10 suits teams managing sensor or other time series data on their own infrastructure.
openGemini suits teams analyzing time-series data for monitoring, observability, IoT, or operations.
Prometheus suits teams that need to collect and query system metrics or set up alerts.
Timestream suits teams building time-series workloads such as IoT telemetry, real-time monitoring, analytics, or predictive maintenance.
kdb+ suits organizations handling time-series workloads in areas such as trading, fraud detection, IoT monitoring, and other listed sectors.
RRDtool suits developers and administrators who need self-hosted time-series logging, retention policies, and graphing through command-line tools or supported language…
It suits teams needing a self-managed time-series system with PromQL, Kafka or Influx ingestion, retention policies, and horizontal scaling.
BTrDB suits developers and operators working with dense telemetry who can deploy and manage a self-hosted database.