influxdata/ influxdb
View on GitHubScalable datastore for metrics, events, and real-time analytics
Scalable datastore for metrics, events, and real-time analytics
InfluxDB 3 Core is a database built to collect, process, transform, and store event and time series data. It is ideal for use cases that require real-time ingest and fast query response times to build user interfaces, monitoring, and automation solutions.
Common use cases include:
InfluxDB is optimized for scenarios where near real-time data monitoring is essential and queries need to return quickly to support user experiences such as dashboards and interactive user interfaces.
InfluxDB 3 Core’s feature highlights include:
Storage format: Apache Parquet on object storage (S3, Azure, GCP) or local disk
Query languages: SQL, InfluxQL, Flight SQL
Write format: Line protocol
API: HTTP on port 8181
Built with: Rust, Apache Arrow, DataFusion
Compatible with: InfluxDB 1.x and 2.x write APIs, InfluxDB 1.x query API (InfluxQL)
This repository contains multiple InfluxDB versions on separate branches:
| Version | Branch | Query Languages | Documentation |
|---------|--------|-----------------|---------------|
| v3 Core (this branch) | main | SQL, InfluxQL | docs.influxdata.com/influxdb3/core/ |
| v2.x | main-2.x | Flux, InfluxQL | docs.influxdata.com/influxdb/v2/ |
| v1.x | master-1.x | InfluxQL, Flux | docs.influxdata.com/influxdb/v1/ |
InfluxDB 3 Core has been generally available since April 2025. See v3.* tags and release notes for the latest version.
Join the InfluxDB3 Discord or the public channels below to share your feedback, feature requests, and bug reports.
Docker images, Debian packages, RPM packages, and tarballs are available on the InfluxData downloads page.
main-2.x branch.master-1.x branch.If you are interested in building from source, see the building from source guide for contributors.
For community support and feedback channels, see Bug reports and feedback.
The open source software we build is licensed under the permissive MIT or Apache 2 licenses at the user’s choosing. We’ve long held the view that our open source code should be truly open and our commercial code should be separate and closed.
Check out current job openings at www.influxdata.com/careers today!
No comments yet. Set the tone — say what you would want to know.