Redpanda BYOC

Managed Kafka-compatible streaming in your cloud account.

3 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Redpanda Cloud BYOC provisioning

    External vendor control plane

  2. Operated by

    Vendor or service partner

    Redpanda manages provisioning, monitoring and upgrades with the permissions you grant.

Deployment boundaries by provider
  • AWS: Customer cloud account · Vendor / partner-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Redpanda BYOC supported infrastructure ↗ · Source checked 2026-11-12

  • Azure: Customer cloud account · Vendor / partner-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Redpanda BYOC supported infrastructure ↗ · Source checked 2026-11-12

  • Google Cloud: Customer cloud account · Vendor / partner-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Redpanda BYOC supported infrastructure ↗ · Source checked 2026-11-12

Redpanda provisions, monitors and upgrades the cluster using delegated access to the customer cloud account. Customer-managed networking is a separate BYOVPC/BYOVNet option.

Operating responsibility source ↗ · Checked 2026-11-20

BYOC managed control plane and customer data plane ↗

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodRedpanda Cloud BYOC provisioning
InfrastructureServers / containers
BYOC uses a customer-cloud cluster and Kubernetes infrastructure. Redpanda’s separately hosted Serverless service is outside this listing.
Licensing modelCommercial Only
This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.
LicenseCommercial

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

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.

Redpanda Cloud marketplace subscription and BYOC path; selected offer terms apply · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

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.

Vendor-operated Cloud control-plane user SSO for a BYOC organisation; data-plane broker/client authentication is separate · Source ↗ · BYOC service identity features ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Redpanda Cloud BYOC control-plane automation and customer-cloud data plane; not self-managed Redpanda core Helm delivery · Source ↗ · Deployment artifact ↗ (Current Cloud provider documentation; pin the selected provider/module versions) · Reviewed 2026-11-21

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

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.

Redpanda Cloud BYOC workload-based sizing; no complete reference-workload machine configuration verified · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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.

Redpanda Cloud BYOC service pricing model; no Community licence or hosted Serverless price applied to BYOC · Source ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Show all fields (7 not researched)
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

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.

Category fit

Streaming
Managed Kafka-compatible streaming in your cloud account.

Compare within Streaming

  • Aiven for Apache Kafka BYOCManaged Apache Kafka brokers in the customer's cloud account, operated by Aiven.
    • AWS
    • Azure
    • Google Cloud
    Vendor-operated BYOC · Commercial Only
  • Apache KafkaDistributed event streaming platform for durable publication, storage and consumption of event streams.
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Apache PulsarDistributed publish-subscribe messaging and streaming platform for persistent event workloads.
    • AWS
    Customer-operated · Open Source / Open Core
  • Cloudera on CloudCloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.
    • AWS
    • Azure
    • Google Cloud
    Shared operations · vendor control plane · Commercial Only
  • Confluent Platform Self-ManagedSelf-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only

These products address related workflows; read their category-fit notes before comparing scope. See all of Streaming →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Redpanda BYOC supported infrastructure ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory