Select product
InfluxDB 3
InfluxDB 2
Other products
InfluxDB 3 is the current generation of InfluxDB and the recommended platform for new time series workloads—built for high-speed, high-cardinality data from the edge to the cloud.
Not sure which product fits your use case? See Which InfluxDB 3 should I use?
The open source recent data engine optimized for time series and event data.
The scalable data engine built for recent and historical time series and event data.
The Kubernetes-enabled, highly-available InfluxDB 3 cluster built for high write and query workloads on your own infrastructure.
The fully-managed, multi-tenant InfluxDB 3 service deployed in the cloud.
The fully-managed InfluxDB 3 cluster dedicated to your workload and deployed in the cloud.
A standalone UI designed for visualizing, querying, and managing data in InfluxDB 3 Core and Enterprise.
The open source data collection agent with support for a large catalog of data sources and targets.
Centralized Telegraf configuration management and agent observability with an intuitive UI.
Enterprise support for Telegraf and Telegraf Controller, plus higher limits and enterprise features in Telegraf Controller.
The open source time series platform with support for Flux and InfluxQL, scheduled tasks, dashboards, and more.
The fully-managed, multi-tenant InfluxDB v2 instance deployed in the cloud and powered by the TSM storage engine.
The functional language specifically designed for querying and processing data.
The open source single-node InfluxDB v1 instance designed for high write and query workloads.
The highly available InfluxDB v1 cluster built for high write and query workloads.
The web UI that visualizes your InfluxDB time series data and easily creates alerting and automation rules.
The data processing framework for creating alerts, running ETL jobs, and detecting anomalies.
© 2026 InfluxData, Inc.
Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.
Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.
Also new in 2.9.0:
EXPLAIN and EXPLAIN ANALYZE in the SQL editor.influxdb3 update table.--max-concurrent-queries and an enforced
WAL buffer limit.Telegraf Controller 1.1 lets teams make fleet-wide configuration changes with a single edit using global constants, configuration groups, and configuration aliases. Configuration versioning makes every change traceable, comparable, and reversible. High availability, available with Telegraf Enterprise, automatically fails over between Controller instances so agents can continue pulling configurations and reporting health if an instance goes down.
InfluxDB OSS 1.13.0 adds mTLS support, adaptive TSI cache sizing, and a hardening option to mitigate SSRF.
Key updates in InfluxDB OSS 1.13.0:
hardening-enabled option to mitigate server-side request
forgery (SSRF) in Flux HTTP requests.For details, see the InfluxDB OSS 1.13.0 release notes.
latest tag for InfluxDB Docker images will
point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version
tags in your Docker deployments.If using Docker to install and run InfluxDB, the latest tag will point to
InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in
your Docker deployments. For example, if using Docker to run InfluxDB v2,
replace the latest version tag with a specific version tag in your Docker
pull command–for example:
docker pull influxdb:2