
# Redpanda BYOC

Managed Kafka-compatible streaming in your cloud account.

Canonical page: https://launchinyourcloud.com/directory/redpanda/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Redpanda BYOC

Managed Kafka-compatible streaming in your cloud account.

- Listing: https://launchinyourcloud.com/directory/redpanda/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Redpanda Cloud BYOC provisioning
- Architecture: Vendor-managed cluster in customer network
- Operations: Redpanda manages provisioning, monitoring and upgrades with the permissions you grant.
- Product website: https://www.redpanda.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

BYOC supports AWS and Google Cloud VPCs and Azure VNets. BYOVPC/BYOVNet lets the customer provision networking first. Review agent permissions and emergency support access. Redpanda Cloud's November update adds Load Factor dashboard metrics for BYOC deployments on version 26.2 or later. Treat the October BYOVNet, self-service scaling, and Azure tier announcements as separate earlier changes when planning upgrades.

This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.

BYOC uses a customer-cloud cluster and Kubernetes infrastructure. Redpanda’s separately hosted Serverless service is outside this listing.


### Category fit

- streaming: Managed Kafka-compatible streaming in your cloud account.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

Operating responsibility: Redpanda provisions, monitors and upgrades the cluster using delegated access to the customer cloud account. Customer-managed networking is a separate BYOVPC/BYOVNet option. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-20). Supporting source: BYOC managed control plane and customer data plane — https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/.


### Cloud deployment evidence

- Redpanda BYOC supported infrastructure (aws, azure, gcp): https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/
  Redpanda explicitly documents BYOC clusters in the customer AWS or Google Cloud VPC or Azure VNet, with a Redpanda-operated control plane. The architecture and provisioning requirements differ by provider; this is the BYOC offering, not Dedicated clusters in the vendor account.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- BYOC deployment options: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/

- BYOC cluster and Kubernetes architecture: https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/

- Redpanda Cloud what's new: https://docs.redpanda.com/cloud-data-platform/get-started/whats-new-cloud/

### Licensing sources

- https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/

### Infrastructure sources

- https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Edition-dependent. Redpanda documents an AWS Marketplace private-offer subscription workflow and links it to BYOC cluster creation. Confirm that the order is for the intended BYOC deployment, not a vendor-account cluster. Scope: Redpanda Cloud marketplace subscription and BYOC path; selected offer terms apply. Source: https://docs.redpanda.com/cloud-data-platform/billing/aws-commit/ (reviewed 2026-11-14).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Redpanda Cloud documents organisation user login through an OIDC-compliant identity provider with discovery. An organisation administrator configures and enables the connection, with optional enrolment and group-based permissions. The BYOC pricing page includes OIDC SSO in that service. Scope: Vendor-operated Cloud control-plane user SSO for a BYOC organisation; data-plane broker/client authentication is separate. Source: https://docs.redpanda.com/cloud-data-platform/security/cloud-authentication/ (reviewed 2026-11-21). Supporting source: BYOC service identity features — https://www.redpanda.com/pricing.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Redpanda documents a Cloud Terraform provider for networks, clusters and data-plane resources, with separate BYOVPC modules for AWS/GCP and a BYOVNet module for Azure. Select the BYOC cluster type, customer-managed resource configuration and throughput tier, pin provider/module versions and review replacement behavior. The provider automates the managed Cloud service, not installation of self-managed Community brokers. Scope: Redpanda Cloud BYOC control-plane automation and customer-cloud data plane; not self-managed Redpanda core Helm delivery. Source: https://docs.redpanda.com/cloud-data-platform/manage/terraform-provider/ (reviewed 2026-11-21). Deployment artifact: https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs. Artifact reference: Current Cloud provider documentation; pin the selected provider/module versions.

- Minimum footprint / sizing: Sources checked — unresolved. The BYOC tier reference maps throughput tiers to cloud machine types and directs buyers to a sizing calculator for broker count, machine type and RPU rate. Its connection examples are not a universal cluster minimum. A production configuration for 100 users/1 TB/HA still needs ingress/egress rate, partitions, retention, connections and recovery targets. Scope: Redpanda Cloud BYOC workload-based sizing; no complete reference-workload machine configuration verified. Source: https://docs.redpanda.com/cloud-data-platform/reference/tiers/byoc-tiers/ (reviewed 2026-11-21).

- License pricing: Documented. The vendor distinguishes Redpanda Cloud BYOC as a fully managed commercial service with an annual commitment and a sales-led trial/quote. Its customer-cloud infrastructure and agreed service charges require separate assessment; self-managed Community or Enterprise software terms are different offerings. Scope: Redpanda Cloud BYOC service pricing model; no Community licence or hosted Serverless price applied to BYOC. Source: https://www.redpanda.com/pricing (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






