Overview

InfluxDB 3 combines timestamped-data storage with query and processing options. InfluxData states that it supports millions of writes per second, billions of series without cardinality limits, and sub-10ms query responses. Those capabilities make it a candidate for demanding real-time workloads, though the actual fit depends on the selected deployment and workload.

Teams can choose open-source single-node Core, self-managed Enterprise, managed single-tenant Cloud Dedicated, multi-tenant Cloud Serverless, or Amazon Timestream for InfluxDB on AWS. This range is useful when deployment constraints differ across projects, but it also means availability, security, and support vary by edition. Browse Time-Series Databases, IoT Analytics Software, Metrics Monitoring Tools, Database Software, OLAP Software, and Columnar Databases.

Key features

Querying and ingestion

Native SQL works alongside InfluxQL, and a built-in Python processing engine extends the query path. Ingestion can use line protocol, HTTP API, client libraries, Telegraf, or the influxdb3 CLI. More than 400 pre-built Telegraf plugins and official libraries for Python, JavaScript, Go, Java, and C# give teams several routes to connect existing systems without making one client the only option.

Storage and scale

Data is stored as compressed Parquet files in object storage with S3 API compatibility. That storage approach is relevant to teams already using object-storage workflows. Retention policies and horizontal scaling are supported, while the product’s stated high write and query capacity is aimed at large time-series workloads.

Security, availability, and support

InfluxData says its products are ISO 27001, ISO 27018, and SOC 2 certified, with end-to-end encryption and granular access controls across managed and self-managed InfluxDB 3 products. Enterprise adds SAML/SSO and OAuth. Cloud Dedicated offers SAML/SSO and private networking as add-ons. Core has no enterprise security or high availability and is community supported; Enterprise and Cloud Dedicated include a technical support SLA. This is a meaningful divide for production teams with strict access or uptime requirements.

Pricing

InfluxDB uses a freemium model, with a free plan and a 30-day trial. The self-managed Enterprise trial is 30 days by default, and InfluxData says it can help extend it. The free and usage-based routes reduce the barrier to starting, but usage-based charges and quotas require attention as workloads grow.

InfluxDB 3 Core: custom pricing. The single-node option is intended for local development, prototyping, and edge deployments; it has no high availability or enterprise security.
Cloud Serverless: 0.00 USD per free to start, then usage-based, with a $250 free credit. Service quotas apply and there is no HA. The usage-based rates are 0.00 USD per month for Data In, 0.01 USD per month for Query Count, 0.00 USD per month for Storage, and 0.09 USD per month for Data Out, each billed pay for what you use. The more detailed usage terms price writes at $0.0025 per MB, queries at $0.012 per 100 executions, storage at $0.002 per GB-hour, and outbound transfer at $0.09 per GB, with no minimum commitment and $250 free credit when upgrading. This is the low-commitment managed choice, but quotas and variable charges matter for growing or predictable workloads.
Cloud Dedicated: custom pricing for a single-tenant managed cloud. SAML/SSO and private networking are add-ons.
Amazon Timestream for InfluxDB: custom pricing billed at AWS consumption rates to your AWS account. It is fully managed on AWS, with native IAM and VPC integration and high availability included, making it a fit for teams whose deployment already centers on AWS.
InfluxDB 3 Enterprise: custom pricing based on CPU configuration. The self-managed plan offers unlimited scale, no service quotas, high availability, and read replicas, with a 30-day free trial. Its pricing model favors teams that need control over deployment and enterprise operating features over a free or usage-based entry point.

Platforms

InfluxDB supports API, Linux, macOS, self-hosted, web, and Windows environments. Both self-managed and managed deployment paths are available, so teams can choose based on infrastructure constraints rather than being limited to one hosting model.

Who it's for

InfluxDB is best suited to teams collecting high-frequency timestamped data for industrial operations, observability platforms, or AI applications that need real-time data. Core works for local development, prototyping, and edge deployments where a single node and community support are acceptable. Teams requiring high availability, enterprise authentication, or a support SLA should consider Enterprise, Cloud Dedicated, or AWS-managed Timestream instead.

Pros and cons

Pro: Multiple deployment models span single-node Core, managed cloud, AWS-managed service, and self-managed Enterprise, giving teams room to match infrastructure needs.
Pro: SQL and InfluxQL, Python processing, varied ingestion methods, and 400+ Telegraf plugins offer useful flexibility for connecting data pipelines.
Pro: S3-compatible Parquet storage and stated support for high write volume and large series counts address substantial timestamped workloads.
Con: Core is single-node, without high availability or enterprise security, so it is not the right production option when those are requirements.
Con: Cloud Serverless has service quotas and no HA; usage-based pricing can also make costs less predictable as ingestion, queries, storage, or transfer rise.
Con: Enterprise and Dedicated use custom pricing, and key Cloud Dedicated security options are add-ons, making cost and configuration harder to compare upfront.

Alternatives

GreptimeDB is another freemium option with a free plan and a fully managed Enterprise plan from 290.00 USD per month, which may suit teams comparing a priced managed tier.

LinDB is a free, open-source alternative for teams prioritizing an Apache 2.0 option across self-hosted and hosted platforms.

QuestDB offers a free, self-managed, single-instance open-source core with community support; consider it if that deployment profile fits.

TDengine offers a free tier and an open-source TSDB-OSS release with clustering under AGPL, an alternative for teams considering that licensing and clustering model.

VictoriaMetrics has free open-source single-node and cluster versions, making it worth comparing when those open-source deployment options are a priority.

DolphinDB has a free Community Edition with a perpetual license, capped at two nodes, two CPU cores, and 8 GB RAM per node; it may suit teams whose requirements fit those bounds.

TimescaleDB offers a Performance plan at 30.00 USD per month, billed hourly pay-as-you-go, with a 30-day trial and up to four database services; compare it if those service and pricing terms suit your needs.

Grafana k6 is an alternative to consider for its stated virtual-user-hour-based free and Pro plans.

Verdict

Choose InfluxDB 3 if you need a time-series platform with multiple ingestion paths and the choice of managed, AWS-managed, or self-managed deployment. Its main advantage is that deployment flexibility extends from a free single-node edition to enterprise-scale options. Look elsewhere if you need high availability in the free Core edition or prefer a fixed, clearly priced managed plan.

	Apache IoTDB	InfluxDB
Free plan	No	Yes
Free trial	No	Yes
Paid from	—	—
Open source	No	No
Platforms	Web, Windows, Linux	api, Linux, macOS, self-hosted, Web, Windows
SQL support	Yes	Yes
Free plan	—	Yes

Apache IoTDB vs InfluxDB

Apache IoTDB

InfluxDB