InfluxDB

InfluxDB 3 is a time series database and platform for high-frequency data with timestamps. It supports native SQL and InfluxQL, along with a built-in Python processing engine. Data can be ingested through line protocol, HTTP API, client libraries, Telegraf, or the influxdb3 CLI; InfluxData lists more than 400 Telegraf plugins and official libraries for Python, JavaScript, Go, Java, and C#. The platform stores compressed Parquet files in object storage with S3 API compatibility. Deployment choices include open-source single-node Core, self-managed Enterprise, managed Cloud Serverless or Cloud Dedicated, and Amazon Timestream for InfluxDB. InfluxData describes uses in industrial operations, observability, and AI applications that need real-time data. Core is intended for development, prototyping, and edge use, but has no high availability or enterprise security and is community supported. Cloud Serverless offers a free option with service quotas and no high availability. Enterprise and Cloud Dedicated include a technical support SLA; managed and self-managed products offer encryption and granular access controls.

InfluxDB 3 offers several deployment models and ingestion paths for time series workloads. Check the Core and Cloud Serverless limits, or consider Enterprise and Cloud Dedicated if their support and availability provisions fit your needs.

InfluxDB 3 may suit teams handling timestamped data for industrial operations, observability, or AI applications. Its different deployment choices also give teams options for self-managed, managed, and single-node use.

InfluxDB 3 is a time-series database for teams working with high-frequency, timestamped data. It is best suited to industrial, observability, and AI workloads that need real-time data and flexible deployment. Its range of hosting options is a strength, but availability, security, and support vary by edition, and Serverless costs depend on usage.

Overview

InfluxDB 3 targets demanding ingestion and query workloads: InfluxData says it supports millions of writes per second, billions of series without cardinality limits, and query responses under 10 milliseconds. Those capabilities make it worth considering for large time-series workloads, though the right deployment still depends on each team's availability and operational requirements.

Deployment options range from open-source, single-node Core to self-managed Enterprise, managed single-tenant Cloud Dedicated, multi-tenant Cloud Serverless, and Amazon Timestream for InfluxDB on AWS. That breadth gives teams a choice between managing infrastructure and using a hosted service, but Core lacks high availability and enterprise security.

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

Key features

Querying and ingestion

Native SQL sits alongside InfluxQL, with a built-in Python processing engine for teams that want processing within the platform. 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 provide several routes for connecting existing systems.

Storage and deployment

InfluxDB stores data in compressed Parquet files in object storage with S3 API compatibility. That design is relevant to teams already using S3-compatible storage, while the deployment choices let organizations decide how much infrastructure to operate themselves. Core is a single-node edition for development, prototyping, and edge deployments; it is not a high-availability choice and does not include enterprise security.

Security and support

InfluxData says its products are 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, so teams requiring those controls should factor the add-on terms into their choice. Core is community supported; Enterprise and Cloud Dedicated include a technical support SLA.

Pricing

InfluxDB uses a freemium model. Cloud Serverless starts free, includes $250 in free credit, and then charges by usage; service quotas apply and it has no high availability. The published usage 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. Separate rate entries show Data In at no cost, Query Count at $0.01 a month, Storage at no cost, and Data Out at $0.09 a month, each billed pay for what you use. Readers should estimate their write, query, storage, and transfer volumes before choosing Serverless; the free starting point does not remove quota or usage considerations.

• InfluxDB 3 Core: A single-node option with no published price. It is intended for local development, prototyping, and edge use, not workloads requiring high availability or enterprise security. Support is community based.
• Cloud Serverless: free, then usage-based, with service quotas, no high availability, and $250 free credit. This fits teams that want managed multi-tenant cloud without a fixed minimum commitment, provided its quotas and availability model suit them.
• Cloud Dedicated: Custom pricing for managed single-tenant cloud. It is a fit for teams seeking dedicated hosting and a technical support SLA; SAML/SSO and private networking are add-ons.
• InfluxDB 3 Enterprise: Custom pricing based on CPU configuration for self-managed use. It includes unlimited scale, no service quotas, high availability, and read replicas, and has a 30-day free trial by default. InfluxData says it can help extend the trial.
• Amazon Timestream for InfluxDB: Price is based on AWS consumption and billed to the AWS account. It is fully managed on AWS, with native IAM and VPC integration and high availability included.

The 30-day trial applies to self-managed Enterprise. Teams comparing plans should weigh Serverless quotas and lack of HA against the higher operational control of self-managed Enterprise or the managed availability options.

Platforms

InfluxDB supports API, Linux, macOS, self-hosted, web, and Windows environments. That range covers teams integrating through APIs, running their own deployment, or using the web-based managed offerings.

Who it's for

InfluxDB is a strong candidate for organizations collecting high-frequency time-series data across industrial operations, observability platforms, or AI applications. Its SQL support, multiple ingestion routes, and deployment range suit teams that need to connect varied data sources and choose between self-management and managed services. Core can serve local development, prototypes, and edge deployments. Look elsewhere if a single-node system without HA is inadequate and a managed service with quotas is also unsuitable.

Pros and cons

• Pros: Multiple deployment models let teams choose self-managed, single-tenant, multi-tenant, AWS-managed, or open-source single-node operation.
• Pros: SQL, InfluxQL, a Python processing engine, and broad Telegraf and client-library support give teams several ways to query, process, and ingest data.
• Pros: Enterprise offers high availability and read replicas without service quotas; Cloud Dedicated includes a technical support SLA.
• Cons: Core is single-node, community supported, and lacks high availability and enterprise security, limiting its fit for production needs with those requirements.
• Cons: Cloud Serverless has service quotas and no high availability, while its usage-based charges make cost dependent on workload volume.
• Cons: Dedicated cloud pricing is custom, and some Cloud Dedicated security options require add-ons, making it less straightforward to budget than the free entry point.

Alternatives

GreptimeDB is another freemium option with a free plan and a fully managed Enterprise plan priced at $290 a month; consider it if that managed-plan structure and its supported platforms fit your requirements.

LinDB is a free, open-source option under Apache 2.0 with Linux, macOS, Windows, web, API, and self-hosted support; it suits readers prioritizing a free software model.

Amazon Timestream is a paid alternative with on-demand pricing and no minimum fees or upfront commitments; consider it if that pricing approach better matches your workload.

DolphinDB offers a free Community Edition under a perpetual license, limited to up to two nodes, two CPU cores, and 8 GB RAM per node; it may fit readers whose needs fall within those limits.

Grafana k6 has a free Linux plan limited to 500 virtual user hours per month and a Pro plan at $19 a month; consider it when those stated plan terms match your needs.

QuestDB offers a free, self-managed, single-instance Apache 2.0 core with community support; it may suit readers looking for that open-source arrangement.

TDengine has a fully open-source TSDB-OSS with clustering capabilities under the AGPL license; consider it if those open-source terms and clustering are a priority.

VictoriaMetrics offers open-source single-node and cluster versions; it is another option for readers seeking open-source software.

Verdict

InfluxDB 3 is a solid choice for teams handling high-frequency time-series data that need multiple ingestion paths, SQL alongside InfluxQL, and a choice of self-managed or managed deployment. Its Enterprise and Dedicated options address availability and support needs, while Core and Serverless provide lower-commitment ways to start with important limits. Look elsewhere if you need predictable pricing without workload estimates, or if neither Serverless quotas nor the custom-priced higher tiers fit your requirements.