Cloud

BYOC Tiers and Regions

BYOC usage tiers

When you create a BYOC cluster, you choose its capacity. If your organization uses usage-based billing, describe your workload and let Redpanda recommend a configuration, rather than choosing a tier directly. See Size and Price a BYOC Cluster. Otherwise, you select a usage tier. Each tier defines a tested workload configuration with maximum (up to) values for throughput, partitions, and connections.

Tier Ingress Egress Partitions (pre-replication) Connections

Tier 1

20 MBps

60 MBps

2,000

9,000

Tier 2

50 MBps

150 MBps

5,600

22,500

Tier 3

100 MBps

200 MBps

11,200

45,000

Tier 4

200 MBps

400 MBps

22,600

90,000

Tier 5

400 MBps

800 MBps

45,600

180,000

Tier 6

800 MBps

1,600 MBps

90,000

180,000

Tier 7

1,200 MBps

2,400 MBps

112,500

270,000

Tier 8

1,600 MBps

3,200 MBps

112,500

360,000

Tier 9

2,000 MBps

4,000 MBps

112,500

450,000

  • Partition counts are based on clusters running Redpanda version 25.1 or higher and on the assumption that the replication factor is 3 (default). If you set a higher replication factor, the maximum value for partitions will be lower.

  • Redpanda supports compute-optimized tiers with AWS Graviton3 processors.

  • Depending on the workload, it may not be possible to achieve all maximum values. For example, a high number of partitions may make it more difficult to reach the maximum value in throughput.

  • Connections are regulated per broker for best performance. For example, in a tier 1 cluster with 3 brokers, there could be up to 3,000 connections per broker.

Machine types and RPUs

Each tier maps to a machine type from your cloud provider, with capacity measured in Redpanda Processing Units (RPUs). Workload-based sizing and usage-based pricing both use RPUs.

Each recommended configuration in the sizing calculator shows its machine type, broker count, and RPU rate. In the Control Plane API and the Redpanda Terraform provider, you select the machine type through its tier ID (throughput_tier).

BYOC supported regions

Each region lists its availability zones. AWS zones are shown as zone IDs (for example, use1-az1), the identifier the AWS API expects; GCP and Azure zones are shown as zone names (for example, europe-west1-b), matching what each provider’s console displays.

  • Google Cloud Platform (GCP)

  • Amazon Web Services (AWS)

  • Azure

Region Zones

asia-east1

asia-east1-a, asia-east1-b, asia-east1-c

asia-northeast1

asia-northeast1-a, asia-northeast1-b, asia-northeast1-c

asia-south1

asia-south1-a, asia-south1-b, asia-south1-c

asia-southeast1

asia-southeast1-a, asia-southeast1-b, asia-southeast1-c

australia-southeast1

australia-southeast1-a, australia-southeast1-b, australia-southeast1-c

europe-southwest1

europe-southwest1-a, europe-southwest1-b, europe-southwest1-c

europe-west1

europe-west1-b, europe-west1-c, europe-west1-d

europe-west2

europe-west2-a, europe-west2-b, europe-west2-c

europe-west3

europe-west3-a, europe-west3-b, europe-west3-c

europe-west4

europe-west4-a, europe-west4-b, europe-west4-c

europe-west9

europe-west9-a, europe-west9-b, europe-west9-c

me-central2

me-central2-a, me-central2-b, me-central2-c

northamerica-northeast1

northamerica-northeast1-a, northamerica-northeast1-b, northamerica-northeast1-c

southamerica-east1

southamerica-east1-a, southamerica-east1-b, southamerica-east1-c

southamerica-west1

southamerica-west1-a, southamerica-west1-b, southamerica-west1-c

us-central1

us-central1-a, us-central1-b, us-central1-c, us-central1-f

us-east1

us-east1-b, us-east1-c, us-east1-d

us-east4

us-east4-a, us-east4-b, us-east4-c

us-west1

us-west1-a, us-west1-b, us-west1-c

us-west2

us-west2-a, us-west2-b, us-west2-c
Region Zones

af-south-1

afs1-az1, afs1-az2, afs1-az3

ap-east-1

ape1-az1, ape1-az2, ape1-az3

ap-northeast-1

apne1-az1, apne1-az2, apne1-az4

ap-northeast-2

apne2-az1, apne2-az2, apne2-az4

ap-south-1

aps1-az1, aps1-az2, aps1-az3

ap-south-2

aps2-az1, aps2-az2, aps2-az3

ap-southeast-1

apse1-az1, apse1-az2, apse1-az3

ap-southeast-2

apse2-az1, apse2-az2, apse2-az3

ap-southeast-3

apse3-az1, apse3-az2, apse3-az3

ca-central-1

cac1-az1, cac1-az2, cac1-az4

eu-central-1

euc1-az1, euc1-az2, euc1-az3

eu-central-2

euc2-az1, euc2-az2, euc2-az3

eu-north-1

eun1-az1, eun1-az2, eun1-az3

eu-south-1

eus1-az1, eus1-az2, eus1-az3

eu-west-1

euw1-az1, euw1-az2, euw1-az3

eu-west-2

euw2-az1, euw2-az2, euw2-az3

eu-west-3

euw3-az1, euw3-az2, euw3-az3

me-central-1

mec1-az1, mec1-az2, mec1-az3

sa-east-1

sae1-az1, sae1-az2, sae1-az3

us-east-1

use1-az1, use1-az2, use1-az4, use1-az5, use1-az6

us-east-2

use2-az1, use2-az2, use2-az3

us-west-2

usw2-az1, usw2-az2, usw2-az3
Region Zones

australiaeast

australiaeast-az1, australiaeast-az2, australiaeast-az3

brazilsouth

brazilsouth-az1, brazilsouth-az2, brazilsouth-az3

centralus

centralus-az1, centralus-az2, centralus-az3

eastus

eastus-az1, eastus-az2, eastus-az3

eastus2

eastus2-az1, eastus2-az2, eastus2-az3

germanywestcentral

germanywestcentral-az1, germanywestcentral-az2, germanywestcentral-az3

japaneast

japaneast-az1, japaneast-az2, japaneast-az3

northeurope

northeurope-az1, northeurope-az2, northeurope-az3

norwayeast

norwayeast-az1, norwayeast-az2, norwayeast-az3

qatarcentral

qatarcentral-az1, qatarcentral-az2, qatarcentral-az3

southcentralus

southcentralus-az1, southcentralus-az2, southcentralus-az3

swedencentral

swedencentral-az1, swedencentral-az2, swedencentral-az3

uaenorth

uaenorth-az1, uaenorth-az2, uaenorth-az3

uksouth

uksouth-az1, uksouth-az2, uksouth-az3

westeurope

westeurope-az1, westeurope-az2, westeurope-az3

westus2

westus2-az1, westus2-az2, westus2-az3