Documentation

InfluxDB Cloud Serverless documentation

This InfluxDB Cloud documentation applies to all organizations created through cloud2.influxdata.com on or after January 31, 2023 that are powered by the InfluxDB 3 storage engine. If your organization was created before this date or through the Google Cloud Platform (GCP) or Azure marketplaces, see the InfluxDB Cloud (TSM) documentation.

To see which storage engine your organization is using, find the InfluxDB Cloud powered by link in your InfluxDB Cloud organization homepage version information.

Comparing InfluxDB 3 Cloud Serverless to other InfluxDB 3 products? See Which InfluxDB 3 should I use? — Cloud Serverless has a different API surface than InfluxDB 3 Enterprise. If your organization is using InfluxDB 3, you’ll see InfluxDB Cloud Serverless followed by the version number.

InfluxDB 3 and Flux

InfluxDB Cloud Serverless and other InfluxDB 3 products don’t support Flux. Although Flux might still work with InfluxDB Cloud Serverless, it isn’t officially supported or optimized for InfluxDB 3.

Flux is now in maintenance mode. For more information, see The future of Flux.

InfluxDB Cloud Serverless is a hosted and managed version of InfluxDB backed by 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 event monitoring.

Get started with InfluxDB Cloud Serverless

InfluxDB 3

InfluxDB 3 is InfluxDB’s next generation that unlocks series limitations present in the Time Structured Merge Tree (TSM) storage engine and allows infinite series cardinality without any impact on overall database performance. It also brings native SQL support and improved InfluxQL performance.

View the following video for more information about InfluxDB 3:

How do you use InfluxDB 3?

All InfluxDB Cloud accounts and organizations created through cloud2.influxdata.com on or after January 31, 2023 are powered by the InfluxDB 3.

To see which storage engine your organization is using, find the InfluxDB Cloud powered by link in your InfluxDB Cloud organization homepage version information. If your organization is using InfluxDB 3, you’ll see InfluxDB Cloud Serverless followed by the version number.


Was this page helpful?

Thank you for your feedback!


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.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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

InfluxDB Cloud Serverless