Docs Cloud Billing Billing and Support Billing and Support 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. You can view detailed billing activity for each cluster and edit payment methods on the Billing page. Pricing information is available on redpanda.com. For questions about billing, contact billing@redpanda.com. Usage-based billing metrics Serverless Dedicated BYOC Pricing for Serverless clusters depends on the data in, data out, data stored, partitions (virtual streams), and the time the instance is up. The cost for each Serverless metric varies based on the region you select for your cluster. Metric Description Uptime Tracks the number of hours the instance is running. NOTE: Uptime is not charged if partitions = 0 and storage = 0. This condition is met when all topics are deleted. Ingress Tracks the data written into Redpanda (in GB). 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. Partitions Tracks the number of partitions used per hour. Storage Tracks the data in object storage per hour (in GB). See also: Serverless limits 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). All Kafka protocol requests (including message headers) are counted as ingress as soon as they are read by Redpanda’s proxy process. The cost varies based on the region you select for your cluster. 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 usage of object storage on an hourly basis during the billing period (in GB-hours). 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. Pricing for BYOC clusters depends on compute, data in, data out, and data stored. The rate decreases as usage increases. Metric Description Compute Tracks the server resources (vCPU and memory) a cluster uses on an hourly basis in Redpanda units (RPUs). Where: 1 RPU = 2 vCPU + 8 GB memory Ingress Tracks the data written into Redpanda (in GB). All Kafka protocol requests (including message headers) are counted as ingress as soon as they are read by Redpanda’s proxy process. Ingress to Iceberg topics Tracks the data written to Iceberg tables per hour (in GB). NOTE: This metric applies only if you write to Iceberg topics. This charge is in addition to the standard ingress charge. 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 usage of object storage on an hourly basis during the billing period (in GB-hours). 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. Redpanda Connect billing metrics Pricing per pipeline depends on: The number of compute units you allocate. The cost of a compute unit, which can vary based on the cloud provider and region you select for your cluster. Metric Description Compute Tracks the server resources (vCPU and memory) a pipeline uses in compute units per hour. Support plans All organizations in Redpanda require one of the following support plans: Support plan Features Basic Designed for non-production environments Provides minimal support: priority 3 tickets within 8 business hours response time and priority 4 tickets with no target response time Support availability is 8:00 AM to 5:00 PM Pacific Time, Monday through Friday, excluding federal US holidays Enterprise Designed for production environments needing continuous availability P1/P2 tickets may be submitted Support availability is 24/7, including holidays Premium Designed for mission-critical workloads 30-minute response times for production outages Includes a named Customer Success Manager to support planning and coordination, and 10 hours per month of consulting from a Solutions Architect Required for deployments with BYOVPC/BYOVnet clusters Next steps Use AWS Commitments Use Azure Commitments Use GCP Commitments Create a Serverless cluster Create a Dedicated cluster Create a BYOC cluster 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 🎉 Thanks for your feedback! Billing AWS: Use Commits