InfluxDB 3

Tested with: InfluxDB 3 3.12 on Databasezy · zb CLI 0.1

InfluxDB 3 Core is the open-source edition of InfluxDB 3: a time-series database that ingests line protocol and answers SQL and InfluxQL queries, built on Apache Arrow, DataFusion and Parquet.

Overview

Each instance runs InfluxDB 3 Core as a single node that stores its Parquet files and write-ahead log on the instance’s volume. Everything happens over one HTTPS port: writes, SQL and InfluxQL queries, Arrow Flight queries from the client libraries, and database and token management. The revealed credential is the instance’s operator (admin) token. Databases are created on first write, or explicitly with the API.

InfluxDB 3 at a glance, from the engine catalogue
Status	Available
Category	Time-series
Versions	3.12 (newest is the default)
Protocol and port	HTTPS on `443`
Runtime	Single-node engine (influxdb)
Backups	data directory snapshot
Point-in-time recovery	No
Pause	Scale to zero
Free plan	No, paid plans only
Licence	MIT

When to use it

Infrastructure and application metrics, IoT telemetry and events with a timestamp.
Workloads that write line protocol from Telegraf or another agent and query recent data with SQL.

Core is optimised for recent data. For long-range analytics over large history, consider ClickHouse or QuestDB; for time series next to relational data, consider TimescaleDB.

Create an instance

Open the portal and choose New instance.
Pick InfluxDB 3 and a version (3.12).
Choose a size and region. Secure placement is listed only after your organization has signed the BAA.
Check the hourly price and monthly estimate, then confirm. The Connect tab fills in when the instance is ready.

zb instances create --engine influxdb --engine-version 3.12 \
  --size s1 --region us-east --name influxdb-demo --wait

# Reveal the credentials once and store them in your secret manager
zb instances credentials reveal influxdb-demo

curl -sS https://api.databasezy.com/v1/orgs/$ZB_ORG/projects/$ZB_PROJECT/instances \
  -H "Authorization: Bearer $ZB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "engine": "influxdb",
  "engine_version": "3.12",
  "size": "s1",
  "region": "us-east",
  "name": "influxdb-demo"
}'

The response is 201 with the instance in status requested, or 202 when a team approval policy applies. See the REST API reference.

Connect

Endpoint and credentials

How a InfluxDB 3 instance is reached: host, ports, TLS and credentials
Host	`influxdb-<id>.<region>.databasezy.com`, for example `influxdb-7f3k.us-east.databasezy.com`
Port `443`	HTTP API: line protocol writes, SQL and InfluxQL queries
Single-IP regions	Single-IP regions use `8443` for HTTP engines instead of `443`. The portal Connect page always shows the right port.
TLS	Required on every port; plaintext is refused. Verify the server: https:// (or the driver's TLS flag) with normal certificate verification; the certificate is publicly trusted.
Credentials	One generated API key (token) with no username, presented as Authorization: Bearer <token> (admin token). Shown once at creation; reveal or rotate it from the Connect tab.

Send the token as Authorization: Bearer <token>. Write line protocol to /api/v3/write_lp?db=<database> and query with /api/v3/query_sql or /api/v3/query_influxql. The v1 (/write, /query) and v2 (/api/v2/write) compatibility endpoints are there for existing agents and client libraries.

Drivers and clients

InfluxDB 3 listens on port 443 (HTTP API: line protocol writes, SQL and InfluxQL queries). Versions: 3.12. Replace the example host with the one on your instance's Connect tab; credentials are shown once at creation.

https://influxdb-7f3k.us-east.databasezy.com:443

import os
from influxdb_client_3 import InfluxDBClient3

client = InfluxDBClient3(
    host="https://influxdb-7f3k.us-east.databasezy.com",
    token=os.environ["ZB_TOKEN"],
    database="app",            # created on first write
)

client.write(record="cpu,host=web-1 usage_user=23.4")
table = client.query("select * from cpu where time > now() - interval '5 minutes'")
print(table.to_pandas())

Tested with: InfluxDB 3 3.12 · influxdb3-python 0.x

[[outputs.influxdb_v2]]
  urls = ["https://influxdb-7f3k.us-east.databasezy.com"]
  token = "$ZB_TOKEN"
  organization = ""        # ignored by InfluxDB 3
  bucket = "app"           # the database name

Tested with: InfluxDB 3 3.12 · Telegraf 1.3x (v2 write API compatibility)

# Write line protocol, then query with SQL
curl -sS "https://influxdb-7f3k.us-east.databasezy.com:443/api/v3/write_lp?db=app" -H "Authorization: Bearer $ZB_TOKEN" \
  --data-binary 'cpu,host=web-1 usage_user=23.4'

curl -sS -G "https://influxdb-7f3k.us-east.databasezy.com:443/api/v3/query_sql" -H "Authorization: Bearer $ZB_TOKEN" \
  --data-urlencode "db=app" --data-urlencode "q=select * from cpu limit 5"

Tested with: InfluxDB 3 3.12 · curl 8

The official InfluxDB 3 client libraries (Python, Go, JavaScript, Java, C#) write over HTTPS and query over Arrow Flight, which is gRPC on the same port. If a Flight query fails through a proxy on your side, use the HTTP query endpoint shown in the curl tab.

See Connecting to Databasezy for the CA bundle and the IP allow-list.

Replacing the token

Credential rotation from the portal or API is not available for InfluxDB: InfluxDB 3 Core keeps the operator token it was created with and cannot be given a new one chosen by Databasezy, so the rotate request is refused with an explanation instead of handing you a token the server would not accept. To replace the token, regenerate it inside InfluxDB with the current one; the old token stops working at once and the response holds the new one:

curl -sS -X POST "https://influxdb-7f3k.us-east.databasezy.com:443/api/v3/configure/token/admin/regenerate" \
-H "Authorization: Bearer $ZB_TOKEN"

Store the new token yourself: from then on the token the portal reveals no longer works, and Databasezy cannot reset it.

Migrate in

Where you can migrate a InfluxDB 3 database from, how, and whether continuous sync is available
Source	How	Continuous sync	Guide status
Self-hosted server	Connection string, Local tools (zb migrate --from local)	No	Available
Another Databasezy instance	Instance to instance	No	Coming soon · phase 2

From InfluxDB 1.x or 2.x, export line protocol and write it into the new instance in batches:

# InfluxDB 2.x (run on the source host)
influxd inspect export-lp --bucket-id <bucket-id> --engine-path ~/.influxdbv2/engine --output-path export.lp
# InfluxDB 1.x
influx_inspect export -lponly -database telegraf -datadir /var/lib/influxdb/data -waldir /var/lib/influxdb/wal -out export.lp

split -l 10000 export.lp chunk_
for f in chunk_*; do
curl -sS "https://influxdb-7f3k.us-east.databasezy.com:443/api/v3/write_lp?db=telegraf" \
  -H "Authorization: Bearer $ZB_TOKEN" --data-binary @"$f"
done

Flux tasks and dashboards do not carry over: InfluxDB 3 queries are SQL or InfluxQL.

How migrations work explains preflight, verification and cutover, and engine conversions covers moves between compatible engines.

Backups and restore

Backups copy the data directory (Parquet files, catalog and write-ahead log) to Databasezy’s object storage while the server runs, so a backup is crash-consistent rather than quiesced. Native object-store snapshots are planned.

A backup restored into a new instance, and a branch, keep the tokens of the instance they came from: connect to them with the source instance’s token (or one you regenerated on the source). The new instance’s own revealed token is not accepted there; regenerate the operator token with the source’s token if you want a separate one.

InfluxDB 3 backups use data directory snapshot. They run inside the instance's namespace, stream straight to the cell's object storage and are checksummed on upload. How often they run and how long they are kept follows your plan's backup policy. A backup is always taken before a resize or a version upgrade.

Point-in-time recovery is not available for InfluxDB 3. A restore returns the data as of a scheduled or manual backup. Restores create a new instance by default and leave the original untouched; an in-place restore asks you to type the instance name and takes a pre-change backup first.

zb backups create influxdb-demo --label before-release      # manual snapshot
zb backups list influxdb-demo
zb backups restore influxdb-demo <backup-id> --name influxdb-demo-restore

Pause and scale to zero

InfluxDB 3 can scale to zero. A paused instance has no running pods and bills no compute; its storage and backups are kept and billed as usual. Connections are refused until you resume it.

zb instances pause influxdb-demo
zb instances resume influxdb-demo

See Pause and resume for schedules, wake times and billing while paused.

Limits, versions and lifecycle

Versions and lifecycle

Supported versions: 3.12 . New instances default to 3.12, the only version offered.
Minor and patch releases are applied for you in the maintenance window, always after a pre-change backup.
New majors are added within 60 days of the upstream release. A major reaches end of life on Databasezy six months after upstream ends support, with notices 90, 30 and 7 days ahead.

Sizes and limits

InfluxDB 3 is not offered on the Free plan; it runs on the paid sizes below. The size sets the CPU, memory, storage ceiling and connection limit; the gateway refuses connections over the limit with a protocol error. Storage grows in steps up to the ceiling, and you can resize at any time.

Sizes available for InfluxDB 3: vCPU, memory, storage ceiling, connection limit and monthly price
Size	vCPU	Memory	Max storage	Max connections	≈ $ / month
`s0`	0.25	1 GiB	20 GB	60	$10
`s1`	0.5	2 GiB	50 GB	100	$15
`s2`	1	4 GiB	200 GB	200	$60
`m2`	2	8 GiB	500 GB	400	$110
`m4`	4	16 GiB	1 TB	800	$210
`l8`	8	32 GiB	4 TB	1,500	$410
`l16`	16	64 GiB	8 TB	3,000	$960
`xl32`	32	128 GiB	16 TB	5,000	$1,870

Full details, including hourly prices and burst CPU, are in the size catalogue; plan quotas are in limits and quotas.

InfluxDB 3 Core has its own limits on the number of databases, tables and columns per table, and on how many Parquet files one query may scan; see the InfluxDB 3 Core documentation for the values in your version. Keep series keys (tags) low-cardinality where you can and filter queries by time.

Licence

Databasezy runs InfluxDB 3 under the MIT licence, as listed in the engine catalogue. Your data and schemas are yours whatever the server's licence; the licence governs the server software we run.

InfluxDB 3 Core is open source; upstream releases it under the MIT or Apache-2.0 licence at your option. InfluxDB 3 Enterprise features (compaction for long-range queries, high availability, read replicas) are not included.

Security

TLS on every connection. TLS 1.2 is the minimum and TLS 1.3 is preferred; plaintext is never offered. Verify the server, not just the encryption: use HTTPS with certificate verification. See TLS and the CA bundle.
IP allow-list. The gateway checks the client address before authentication, on every plan. Manage it under Network → Allow-list in the portal or with PUT /v1/orgs/{org}/instances/{id}/network.
Credentials. Generated inside the cell, shown once, never stored by the control plane. Rotate them with an overlap window so nothing breaks.
Secure hosting. Secure placement (HIPAA-ready) is a per-instance option once your organization has signed the BAA: dedicated nodes, customer-managed keys and immutable backups. See Secure hosting and the BAA.
Staff access. Databasezy staff cannot read your data without a grant you issue. See data confidentiality.

FAQ

Can I keep using Telegraf?

Yes. Point the influxdb_v2 output at the instance with the token, and use the database name as the bucket.

Does it support Flux?

No. InfluxDB 3 queries are SQL or InfluxQL.

Can I rotate the token?

Not from the portal or API (see Replacing the token); regenerate it inside InfluxDB and keep the new one.

Is InfluxDB on the Free plan?

No. It is a paid-plan engine.