Home / Compute
InfluxDB Cloud Serverless
www.influxdata.com/influxdb-pricing/Managed databasecompute/influxdb-cloud-serverlessJSONcomparereport an errorprovider JSON
- Free allowance
- Two offers on one page.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- request-ratethe ingest rate is the ceiling, not a volume: 5 MB per 5 minutes is about 1.4 GiB a day and cannot be burst, so a backfill of historical measurements fails at the rate limit even though the plan has no monthly volume cap.
- Evidence
- documented5 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | Two offers on one page. The Free Plan, quoted from the docs: 'New InfluxDB Cloud Serverless accounts start with the Free Plan that provides a limited number of resources and data usage' with 'Data-in: Rate of 5 MB per 5 minutes (average of 17 kb/s)', 'HTTP response payload rate: 300 MB data per 5 minutes', '2 buckets', and '30 days of data retention'. The paid path adds 'a $250 credit for 30 days upon upgrade'. unit minutes; metered on wall-clock; perpetual-free |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) the ingest rate is the ceiling, not a volume: 5 MB per 5 minutes is about 1.4 GiB a day and cannot be burst, so a backfill of historical measurements fails at the rate limit even though the plan has no monthly volume cap. source
|
|---|
| Identity | email no card: the pricing page lists 'No credit card required' beside the Cloud Serverless offer, and the sign-up docs limit a Free Plan user to one organization. No hold exists because no payment method is taken for the free plan. The signup fields are not quoted, so the email requirement is inferred rather than read, and debit and prepaid acceptance are not stated. |
|---|
| Egress | not stated |
|---|
| Interface | unknown HTTP API (v2-compatible /api/v2/write for writes, v1-compatible /query for InfluxQL) and Flight+gRPC clients for SQL and InfluxQL queries |
|---|
| Tooling | Flight+gRPC clients for SQL and InfluxQL queries and the HTTP API for writes; the API reference page names no client library |
|---|
| Composes with | a perpetual 30-day-retention time series with 2 buckets is the metrics sink for a free-tier application estate, and 17 kb/s is enough for a few hundred gauges at scrape intervals of a minute. |
|---|
| Reliability | no reliability event recorded |
|---|
| Notes | Retention is 30 days, so this cannot hold history. The vendor states the rate limits suit 5 to 10 sensors. |
|---|
| Parsed numbers | - has-free-tier 1
- request-rate 5 MB
|
|---|
Evidence 5
| date | source | what it proved |
|---|
| 2026-10-22 | docs.influxdata.com/influxdb3/cloud-serverless/admin/billing | Free Plan: 'Data-in: Rate of 5 MB per 5 minutes (average of 17 kb/s)', 'HTTP response payload rate: 300 MB data per 5 minutes', '2 buckets', '30 days of data retention', quoted |
| 2026-10-22 | www.influxdata.com/influxdb-pricing/ | Cloud Serverless lists '- $250 free credit to start', 'No minimum commitment', 'Multi-tenant - Service quotas apply - No HA' and 'No credit card required', quoted |
| 2026-10-22 | docs.influxdata.com/influxdb3/cloud-serverless/sign-up/ | 'Use it as much and as long as you like within the plan rate-limits. Limits are designed to let you monitor 5-10 sensors, stacks or servers comfortably. Users on the Free Plan are limited to one organization.', quoted |
| 2026-11-04 | docs.influxdata.com/influxdb3/cloud-serverless/reference/api | the documented query interfaces are HTTP /query and Flight+gRPC |
| 2026-11-04 | docs.influxdata.com/influxdb3/cloud-serverless/reference/api | clients are Flight+gRPC, none named |
More fields 1
| facets | {"class": "timeseries-free-tier","free_tier_kind": "perpetual-free","shape": {"vcpu": null,"ram_gib": null,"disk_gib": null}} |
|---|
Unknown values 6
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- retention stated: the field does not apply to this kind of offer