Overview

InfluxDB 3 is a time-series database for high-frequency, timestamped data, best suited to teams building observability, industrial, or real-time AI applications. Its range of managed and self-managed deployments is useful, but Core and Serverless make meaningful trade-offs in availability, security, and service limits.

InfluxData says the platform supports millions of writes per second, billions of series without cardinality limits, and query responses under 10 milliseconds. Those capabilities make it a candidate for demanding workloads, though the right deployment matters: Core is a single-node option, while Enterprise, Dedicated, and AWS-managed Timestream offer different paths to scale or high availability.

It supports retention policies and horizontal scaling. Browse related Time-Series Databases, IoT Analytics Software, Metrics Monitoring Tools, OLAP Software, Columnar Databases, and Database Software.

Key features

Ingestion, querying, and storage

Data can enter through line protocol, HTTP API, client libraries, Telegraf, or the influxdb3 CLI. More than 400 pre-built Telegraf plugins and official Python, JavaScript, Go, Java, and C# libraries give teams several established routes to connect data sources and applications. SQL is supported alongside InfluxQL, and a built-in Python processing engine adds an option for processing data within the platform.

InfluxDB stores data as compressed Parquet files in object storage with S3 API compatibility. That storage design may suit organizations already working with object storage, while users should weigh their deployment and service limits rather than assume every edition has the same operating characteristics.

Deployment, security, and support

Choices range from self-managed Enterprise and single-node Core to managed Cloud Dedicated, Cloud Serverless, and Amazon Timestream for InfluxDB on AWS. This breadth is a strength for teams with different infrastructure preferences; it also makes edition-level distinctions central to the buying decision. Core has no high availability or enterprise security and is intended for development, prototyping, and edge deployments. Cloud Serverless is multi-tenant, subject to service quotas, and has no HA.

InfluxData states that it is ISO 27001, ISO 27018, and SOC 2 certified, and that end-to-end encryption and granular access controls are available 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 is community supported; Enterprise and Cloud Dedicated include a technical support SLA. Buyers who need enterprise controls or contracted support should choose accordingly rather than treating the editions as interchangeable.

Pricing

InfluxDB uses a freemium model, with a free option, usage-based paid service, and a 30-day trial. The self-managed Enterprise trial is 30 days by default, and InfluxData says it can help extend it.

InfluxDB 3 Core: Single-node; price not listed. Its lack of HA and enterprise security makes it better suited to local development, prototypes, and edge use than production deployments that require resilience.
Cloud Serverless: Start for free, then pay based on usage; the free offer includes $250 free credit. It is multi-tenant, service quotas apply, and there is no HA. The usage-based rate card gives Data In at 0.00 USD per month, Query Count at 0.01 USD per month, Storage at 0.00 USD per month, and Data Out at 0.09 USD per month, each billed pay for what you use. The separate usage-based terms state $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 and $250 free credit when upgrading. This suits workloads that can accept quotas and no HA; usage-based costs require attention as data and queries grow.
Cloud Dedicated: Custom pricing for a single-tenant managed cloud. SAML/SSO and private networking are add-ons; the fit is teams that want a managed single-tenant deployment and can obtain a custom quote.
Amazon Timestream for InfluxDB: Price not listed; AWS consumption pricing is billed to the AWS account. It is fully managed on AWS, includes high availability, and integrates with native IAM and VPC, making it a fit for teams prioritizing those AWS deployment attributes.
InfluxDB 3 Enterprise: Custom pricing based on CPU configuration. This self-managed option offers unlimited scale, no service quotas, high availability, and read replicas; it also includes a 30-day free trial. It is the stronger fit for teams that need those controls and can manage deployment themselves.

Platforms

InfluxDB supports API, Linux, macOS, self-hosted, web, and Windows environments. The mix of self-hosted and managed deployment options gives infrastructure teams flexibility, while users should match platform choice to the edition's availability, quota, security, and support terms.

Who it's for

InfluxDB is worth considering for teams handling high-frequency timestamped data in industrial operations, observability platforms, or real-time AI applications. Its broad ingestion options and SQL support help accommodate varied pipelines. It is less suitable when a single-node Core installation must provide high availability, or when a Serverless deployment's quotas and lack of HA conflict with requirements.

Pros and cons

Pro: Multiple ingestion paths, 400+ Telegraf plugins, and official libraries for five named languages help connect diverse data sources and applications.
Pro: SQL and InfluxQL, plus a built-in Python processing engine, give teams more than one way to query and process data.
Pro: Enterprise offers high availability and read replicas without service quotas, while managed options include a single-tenant deployment and an AWS-managed service with HA.
Con: Core is single-node and has neither HA nor enterprise security, limiting its fit to development, prototyping, and edge deployments.
Con: Cloud Serverless has service quotas and no HA, so its free entry point does not suit every production requirement.
Con: Enterprise and Dedicated use custom pricing, while Serverless is usage-based; buyers need to choose an edition and account for its terms rather than rely on one simple flat plan.

Alternatives

Choose QuestDB if a free, Apache 2.0, self-managed single-instance database with community support better matches the requirement. VictoriaMetrics is another freemium option with open-source single-node and cluster versions. Consider DolphinDB if its free Community Edition's perpetual license and stated limit of two nodes, each with two CPU cores and 8 GB RAM, fit the intended deployment. TDengine offers a fully open-source TSDB-OSS with clustering under the AGPL license. LinDB is a free, Apache 2.0 open-source option. Grafana k6 is an alternative to consider for its stated free allowance of 500 virtual user hours per month. Choose TimescaleDB if its self-hosted Performance plan at 30.00 USD per month, pay-as-you-go hourly, fits better; it includes a 30-day free trial, no credit card required, and up to four database services, eight CPU per service, and 32 GB RAM. Prometheus is a free, Apache 2.0 open-source monitoring and alerting toolkit.

Verdict

InfluxDB 3 is a strong choice for teams that need a time-series platform with multiple ingestion routes, SQL and InfluxQL, and a choice of managed or self-managed deployment. Its main reason to choose it is that breadth; its main reason to look elsewhere is that availability, quotas, security, support, and pricing change substantially by edition. Pick the deployment only after matching those trade-offs to the workload.

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

InfluxDB vs Milvus

InfluxDB

Milvus