Documentation

Select product

InfluxDB 3

InfluxDB 3 is the current generation of InfluxDB and the recommended platform for new time series workloads. Built on Apache Arrow and object storage, it supports SQL and InfluxQL, handles unlimited series cardinality, and scales without managing local disks. If you currently run InfluxDB 1 or InfluxDB 2, plan a migration to InfluxDB 3.

InfluxDB 3 Core documentation

InfluxDB 3 Core is an open source time series database designed and optimized for real-time and recent data. Learn how to use and leverage InfluxDB 3 in use cases such as edge data collection, IoT data, and events.

InfluxDB 3 Enterprise documentation

InfluxDB 3 Enterprise is a time series database built on InfluxDB 3 Core open source. It is designed to handle high write and query loads using a diskless architecture that scales horizontally. Learn how to use and leverage InfluxDB in use cases such as monitoring metrics, IoT data, and events.

InfluxDB 3 Explorer documentation

InfluxDB 3 Explorer is a standalone web-based interface for interacting with InfluxDB 3 Core and Enterprise. Visualize, query, and manage your time series data efficiently.

InfluxDB Cloud Dedicated documentation

InfluxDB Cloud Dedicated is a hosted and managed InfluxDB Cloud cluster dedicated to a single tenant. The InfluxDB time series platform is designed to handle high write and query loads. Learn how to use and leverage InfluxDB Cloud Dedicated for your specific time series use case.

InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB 3, the time series platform designed to handle high write and query loads. Learn how to use and leverage InfluxDB Cloud Serverless in use cases such as monitoring metrics, IoT data, and events.

InfluxDB Clustered documentation

InfluxDB Clustered is a highly available InfluxDB 3 cluster hosted and managed on your own infrastructure. The InfluxDB time series platform is designed to handle high write and query loads. Learn how to use and leverage InfluxDB Clustered for your specific time series use case.

Not sure which product fits your use case?

See Which InfluxDB 3 should I use? for a full comparison of all InfluxDB 3 products and migration guidance.

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

InfluxDB OSS 2.9.0: API tokens are hashed by default

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.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the 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