Docs Cloud Billing Usage Metrics 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 Pricing for Serverless clusters depends on the data in, data out, data stored, partitions (virtual streams), and for Serverless Pro clusters only, the time the instance is up. Metric Description Uptime Tracks the number of hours the instance is running. Note: Serverless Pro only. There is no base cost for Serverless Standard. Ingress 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 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 Tracks the data in object storage per hour (in GB). Partitions Tracks the number of partitions used per hour. See also: Serverless Standard limits and Serverless Pro limits Dedicated metrics Pricing for Dedicated clusters depends on the time the instance is up, the data in, data out, and data stored. Metric Description Uptime Tracks the number of hours the instance is running. The cost varies based on the region and tier you select for your cluster. Ingress 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 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 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. Next steps Use GCP Commitments Use AWS Commitments Use Azure Commitments Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution Billing AWS: Use Pay As You Go