Overview

InfluxDB 3 is designed for data where timestamps are central. InfluxData says it supports millions of writes per second, billions of series without cardinality limits, and query responses under 10 ms. Those capabilities make it a candidate for demanding real-time workloads, though actual results will depend on deployment and workload.

Choices range from single-node Core to self-managed Enterprise, managed Cloud Dedicated and Cloud Serverless, and AWS-managed Amazon Timestream for InfluxDB. That breadth is useful for teams with different operating preferences, but it is not a uniform product: Core has no high availability or enterprise security, while Cloud Serverless has service quotas and no high availability.

InfluxDB supports SQL and InfluxQL, retention policies, and horizontal scaling. Browse related categories: Time-Series Databases, IoT Analytics Software, Metrics Monitoring Tools, OLAP Software, Columnar Databases, and Database Software.

Key features

Querying and ingestion

Native SQL sits alongside InfluxQL, and a built-in Python processing engine adds an option for in-database processing. Data can arrive through 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 established integration routes.

Storage and scale

Data is stored as compressed Parquet files in object storage with S3 API compatibility. That architecture will appeal to teams already working with object storage, while the stated performance claims make the product relevant to high-volume time-series workloads. Horizontal scaling is supported, but Core remains explicitly single-node.

Security 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 includes SAML/SSO and OAuth. Cloud Dedicated offers SAML/SSO and private networking as add-ons. Core is community supported; Enterprise and Cloud Dedicated include a technical support SLA. That makes Core a weaker fit where enterprise security or contractual technical support is essential.

Pricing

InfluxDB uses a freemium model. Core has no listed price and is single-node. Cloud Dedicated has custom pricing for a single-tenant managed service. Enterprise is self-managed, custom-priced based on CPU configuration, and offers unlimited scale, no service quotas, high availability, and read replicas. Its 30-day free trial is extendable with InfluxData's help.

Cloud Serverless starts at 0.00 USD per free, with $250 free credit, then usage-based charges. It is multi-tenant, subject to service quotas, and has no high availability, so it is a lower-commitment way to start rather than a fit for every availability requirement. Usage-based rates are $0.0025 per MB written, $0.012 per 100 query executions, $0.002 per GB-hour, and $0.09 per GB transferred out, with no minimum commitment. The usage components are priced separately: Data In is 0.00 USD per month, Query Count 0.01 USD per month, Storage 0.00 USD per month, and Data Out 0.09 USD per month, each billed pay for what you use.

Amazon Timestream for InfluxDB uses AWS consumption pricing billed to the AWS account. It is fully managed on AWS and includes high availability, with native IAM and VPC integration. InfluxDB 3 Core is the leanest option for local development, prototyping, and edge deployments, but gives up high availability and enterprise security. Enterprise's trial lasts 30 days by default; the separate Cloud Serverless offer has $250 free credit.

Platforms

InfluxDB supports API, Linux, macOS, Windows, web, and self-hosted use. Its deployment choices span self-managed and managed services, including an AWS-managed option. This is a broad fit for teams that want to choose their operating model, though the features available vary by edition.

Who it's for

InfluxDB is best suited to teams collecting timestamped data for industrial operations, observability, or AI applications that need real-time information. Core is a sensible starting point for development, prototypes, and edge deployments where a single node is enough. Cloud Serverless suits users who want managed service and pay-as-you-go pricing and can accept quotas and no high availability. Organizations that need high availability, no service quotas, or read replicas should consider Enterprise; AWS-centric teams may prefer the managed Timestream option.

Pros and cons

Pros: SQL and InfluxQL support, a Python processing engine, and several ingestion paths give teams flexibility in working with time-series data.
Pros: More than 400 Telegraf plugins and official libraries for five named languages ease connection to varied data sources and applications.
Pros: Multiple deployment models let teams choose self-hosting, managed cloud, or AWS-managed operation.
Cons: Core is single-node, without high availability or enterprise security, limiting its suitability for production needs that depend on either.
Cons: Cloud Serverless has service quotas and no high availability, so its free entry point is not a substitute for an availability-focused deployment.
Cons: Enterprise and Dedicated pricing is custom, while Serverless charges vary with ingestion, queries, storage, and data transfer, making costs dependent on usage.

Alternatives

QuestDB is worth considering if a free, Apache 2.0, self-managed single-instance database with community support fits the requirement. VictoriaMetrics is another freemium option with open-source single-node and cluster versions. DolphinDB offers a perpetual-license Community Edition capped at two nodes, each with two CPU cores and 8 GB RAM, a more bounded free option. TDengine is an alternative with a fully open-source TSDB-OSS edition that includes clustering under AGPL.

LinDB is a free Apache 2.0 option. Prometheus is a free, Apache 2.0 monitoring and alerting toolkit, making it the more focused choice when that is the need. GreptimeDB is an alternative with a managed Enterprise plan from 290.00 USD per month. Grafana k6 is another freemium tool to consider.

Verdict

Choose InfluxDB 3 if you need a time-series platform with multiple query and ingestion paths and want to select between self-managed, managed, and AWS-based deployments. The main reason to look elsewhere is operational certainty: Core lacks high availability, Serverless has quotas and no HA, and the options with high availability carry custom or AWS consumption pricing.

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

Apache IoTDB vs InfluxDB

Apache IoTDB

InfluxDB