Skip to content
Databasezy
← All engines

InfluxDB 3

Time-series Available

Time-series with SQL

InfluxDB 3 Core ingests line protocol and answers SQL queries on recent data quickly. Built on Apache Arrow and Parquet for metrics, events and sensor data.

Good for

  • Infrastructure metrics
  • IoT telemetry
  • Application events

Sample query

influxdb3 · influxdb-7f3k.us-east.databasezy.com
Sample
> SELECT date_bin(INTERVAL '1 minute', time) AS minute,
         avg(usage_user) AS cpu
  FROM cpu
  WHERE host = 'web-1' AND time > now() - INTERVAL '3 minutes'
  GROUP BY minute ORDER BY minute;
Sample result of the InfluxDB 3 query above
minute cpu
2026-10-04T09:41:00Z 23.4
2026-10-04T09:42:00Z 27.9
2026-10-04T09:43:00Z 24.1
3 rows · 6.7 ms Illustrative data and timing

InfluxDB on Databasezy

  • Line protocol ingest

    Write points over HTTP with the same line protocol Telegraf and most agents speak.

  • SQL queries

    Query with SQL, including date_bin for time bucketing.

  • Arrow and Parquet

    Columnar storage keeps recent data fast to scan.

  • Data directory snapshots

    Parquet files and the WAL are copied to object storage on your plan's schedule.

Connect to InfluxDB

Hosts, ports and the CA bundle come from the portal or the CLI after you create an instance. Credentials are shown once and never stored by our control plane.

From the CLI

1. Create the instance
zb instances create --engine influxdb --name influxdb-7f3k --wait
2. Download the CA bundle
zb ca > databasezy-ca.pem
3. Print the endpoint
zb connect influxdb-7f3k --print

At a glance

Category
Time-series
Versions
3.12
Wire protocol
http · port 443
Runtime
Single-node adapter (influxdb)
Backup
Data directory snapshot to object storage
Pause
Scale to zero
Free tier
No
Licence
MIT

Connection strings and drivers

Endpoint
https://influxdb-7f3k.us-east.databasezy.com  (TLS; API key)
HTTP
curl -H "Authorization: Bearer <token>" "https://influxdb-7f3k.us-east.databasezy.com/api/v3/query_sql?db=app&q=SELECT+1"
Write line protocol
curl -H "Authorization: Bearer <token>" "https://influxdb-7f3k.us-east.databasezy.com/api/v3/write_lp?db=app" --data-binary 'cpu,host=web-1 usage_user=23.4'

Choose where it runs

Placement is chosen per database, so a regulated workload and a side project can live in the same organisation.

  • Standard hosting

    Shared cells with namespace isolation, default-deny network policy and an IP allow-list. Available on every paid plan.

    • Usage-based compute, billed per running hour
    • Spend cap to stop surprises
  • Secure hosting (HIPAA)

    This database runs on dedicated nodes in a separate HIPAA cell, under a signed Business Associate Agreement. Available on Team and Enterprise.

  • From the CLI or API

    Script instances in CI with the zb CLI or the REST API. Pick the placement per instance.

    secure placement
    zb instances create --engine influxdb --placement secure --wait

InfluxDB on each plan

Usage-based pricing with a spend cap: you pay a plan fee plus what your instances use.

Free tier

InfluxDB 3 is not on the free plan. It starts on Solo, where a monthly compute credit covers one s0 instance.

Sizes

From s0 (0.25 vCPU, 1 GiB) at $10/mo up to xl32 (32 vCPU, 128 GiB). Resize without changing the connection string.

All sizes and prices

Backups

Data directory snapshot to object storage. Snapshots only: point-in-time recovery is not available for this engine.

Migrate to InfluxDB from

Copy a database in with a connection string, a file upload or the CLI. Preflight checks the source first and verification compares the copy.

InfluxDB questions

Which InfluxDB versions can I run?

3.12 today. Minor and patch updates are applied in your maintenance window after a pre-change backup.

Which extensions, modules or plugins are available?

We run InfluxDB 3 Core, the open-source edition. Enterprise-only features of InfluxDB 3, such as compaction for long-range queries, high availability and read replicas, are not included.

How are backups handled?

Backups use Data directory snapshot to object storage. Paid plans run scheduled backups (Solo: daily, 7-day retention; Team: daily, 14-day retention). InfluxDB 3 does not support point-in-time recovery; you restore from the most recent snapshot into a new instance.

Is the connection encrypted?

Always. The gateway terminates TLS (1.3 where your client supports it, 1.2 at minimum) and re-encrypts traffic to the database. Plain-text connections are refused. Verify the server with our CA bundle from the portal or zb ca, and restrict access further with the IP allow-list included on every plan.

Can I pause it when I'm not using it?

Yes. On paid plans you pause on demand or on a schedule. A paused instance bills storage and backups but no compute, and wakes in 10 to 40 seconds.

What are the limits?

InfluxDB 3 is not on the free plan. Paid sizes run from s0 (0.25 vCPU, 1 GiB, 60 connections, $10/mo) to xl32 (32 vCPU, 128 GiB, 5,000 connections), with up to 16 TB of disk.

Does it work with Telegraf? What about Flux?

Telegraf works through the v2 write compatibility API with the instance token. Flux does not: InfluxDB 3 queries are SQL or InfluxQL.

What you get on each plan

Plan features as they apply to InfluxDB 3.

InfluxDB 3 features by plan
Feature Free Solo Team Enterprise
InfluxDB on this plan NoYesYesYes
Plan fee —$25/mo$599/moCustom
Largest size —xl32xl32xl32
Included per instance —8 GB8 GBNegotiated
Max disk per instance —1 TB16 TB16 TB
Scheduled backups —Daily, 7-day retentionDaily, 14-day retentionHourly, 35-day retention · cross-region copy · immutable
Point-in-time recovery —Not available for this engineNot available for this engineNot available for this engine
Pause —On demand or on a scheduleOn demand or on a scheduleOn demand or on a schedule
Secure hosting (HIPAA) ——Available with a BAAAvailable with a BAA
Support —EmailPriority24x7 dedicated
Uptime SLA ——99.9%99.95%

Start with InfluxDB today

Pick a size, set a spend cap and connect in minutes.