InfluxDB review

InfluxDB is a time-series database for continuous, high-resolution operational data. InfluxData says it is built to capture, analyze and act on that data in real time, with deployments available on-premises, at the edge or in the cloud.

The product is aimed at workloads where readings arrive over time and need to be queried or acted on quickly. Its listed capabilities include ingesting millions of series, real-time transformation and analysis, and capturing data at the edge for analysis elsewhere. InfluxData also says it can compress and downsample high-resolution data, evict cold data, and stream it to data lakes, warehouses and AI/ML pipelines.

There are several ways to buy or run it: the free, open-source InfluxDB 3 Core for local development and prototyping; usage-priced Cloud Serverless; custom-priced Cloud Dedicated and InfluxDB 3 Enterprise; and an AWS-billed option through Amazon Timestream for InfluxDB. Those are materially different deployment and billing choices, not one simple subscription tier.

InfluxDB makes sense when the workload is genuinely time-series data: ongoing readings, high-resolution measurements or operational telemetry. The product is designed around ingesting and analyzing series, rather than being presented as a general-purpose relational database. InfluxData lists edge-to-cloud continuity, compression and downsampling, plus automatic cold-data eviction and streaming to lakes, warehouses and AI/ML pipelines. Those are useful capabilities to assess if you need to keep recent data readily available while sending older data elsewhere.

Deployment choice is another practical advantage. The homepage says InfluxDB can run on-premises, at the edge or in the cloud. The pricing page also lists self-managed Enterprise, managed single-tenant Cloud Dedicated, Serverless and an AWS-billed option, so teams can evaluate different operating models.

For development and prototyping, InfluxDB 3 Core is free forever and runs on Linux, Mac and Docker, according to the pricing details. For Serverless evaluation, the listed offer includes $250 in free credit. These reduce the cost of trying the product, though neither establishes what a production workload will cost.

Fit depends on the data and query pattern. In one Reddit discussion, commenters said minute-resolution market data may not need a specialized time-series database; others pointed to performance concerns and query needs as reasons to compare alternatives. That is a reminder to size the workload before choosing.

The main purchasing drawback is price visibility. The pricing details list no standard monthly subscription price for Enterprise or Cloud Dedicated; both are custom. Serverless is metered, and annual usage-commitment discounts require contacting sales. Dedicated private networking and SAML/SSO are add-ons, but their prices are not published. Get a quote against your expected ingest, queries, storage and data transfer before treating this as a low-cost production stack.

Serverless lists a $250 free credit, then charges $0.0025 per MB written, $0.012 per 100 query executions, $0.002 per GB-hour stored and $0.09 per GB transferred out. Those rates make usage assumptions important. The pricing page does not give a fixed monthly cap. By contrast, Enterprise and Dedicated list no service quotas, but their custom pricing makes the cost of that capacity unclear upfront.

Core has sharper limits: the pricing details say it has no high availability, no enterprise security and community support. It is positioned for local development and prototyping, not as a like-for-like free production option.

Migration may also matter for existing users. In a Home Assistant Reddit thread, users discussed moving from InfluxDB v1 to v2 or v3, while a commenter said v1 remained maintained. Treat that as a community discussion, not a definitive support policy; check the current docs and your integration path before switching.

InfluxDB 3 Core is free forever for local development and prototyping, but it has no high availability or enterprise security. For production, the pricing page lists no standard subscription price for InfluxDB 3 Enterprise or Cloud Dedicated: both require a custom quote. Enterprise includes a 30-day free trial; Dedicated charges extra for private networking and SAML/SSO, with add-on prices not published. That is a sharp jump from free Core to quote-based production plans.

Cloud Serverless is metered, not a flat monthly plan: $0.0025 per MB written, $0.012 per 100 query executions, $0.002 per GB-hour stored, and $0.09 per GB transferred out. It includes $250 in free credit, and annual usage-commitment discounts require contacting sales. Watch write volume, query count, storage time, and egress: they all affect the bill. Amazon Timestream for InfluxDB is billed through AWS, with AWS credits and EDP discounts applying. Telegraf Enterprise is a separate product, listed as starting at $18,000 per year.

The published material does not specify migration tools, supported import or export formats, or compatibility with another database. Before switching, confirm how your existing data and queries map to InfluxDB, and test the route with a representative dataset. InfluxDB says cold data can be streamed to lakes, warehouses, and AI/ML pipelines, but that is not a documented full-database export or migration process.

Deployment options include on-premises, edge, and cloud, so where the database runs is not the only switching decision. Check how your team will handle retention, data movement, and any usage-based Serverless charges; private networking and SAML/SSO on Cloud Dedicated are paid add-ons. Core also lacks high availability, which may rule it out as a production destination. The published sources contain no Reddit posts or comments, so we can’t responsibly say what users report as reasons for leaving. Ask InfluxData for migration guidance and a production quote before committing.