Usage Metrics
Redpanda Cloud uses various metrics to measure the consumption of resources.
-
All pricing is set in US dollars (USD).
-
All billing computations are conducted in Coordinated Universal Time (UTC). Billing accrues at hourly intervals. Any usage that is less than an hour is billed for the full hour.
| Pricing information is available on redpanda.com. For questions about billing, contact billing@redpanda.com. |
Serverless metrics
There is no base cost for a Serverless instance. Pricing for Serverless clusters depends on the data in, data out, data stored, and partitions (virtual streams).
| Metric | Description |
|---|---|
Ingress |
This tracks the data written into Redpanda (in GB). The cost varies based on the region you select for your cluster. All Kafka protocol requests (except message headers) are counted as ingress as soon as they are read by Redpanda’s proxy process. |
Egress |
This tracks the data read out of Redpanda (in GB). All Kafka protocol responses generated by the cluster (except message headers) are counted as egress as soon as the cluster processes the request, even if the client drops the connection before they are delivered. |
Storage |
This tracks the data in object storage per hour (in GB). |
Partitions |
This tracks the number of partitions used per hour. |
See also: Serverless limits
Dedicated metrics
Pricing for Dedicated clusters depends on the time the instance in up, the data in, data out, and data stored.
| Metric | Description |
|---|---|
Instance |
This tracks the number of hours the instance is running. The cost varies based on the region and tier you select for your cluster. |
Ingress |
This tracks the data written into Redpanda (in GB). The cost varies based on the region you select for your cluster. All Kafka protocol requests (including message headers) are counted as ingress as soon as they are read by Redpanda’s proxy process. |
Egress |
This tracks the data read out of Redpanda (in GB). All Kafka protocol responses generated by the cluster (including message headers) are counted as egress as soon as the cluster processes the request, even if the client drops the connection before they are delivered. The cost varies based on the number of availability zones (AZ) you select for your cluster. |
Storage |
This tracks the data in object storage per hour (in GB). Replication to object storage is implemented with Tiered Storage. All topics have a fixed replication factor of 3, but Redpanda counts each byte only once. |
See also: Cluster tiers