DOC-893 Document feature UBB-BYOC (#350)

micheleRP · Feediver1 · web-flow · commit 5c19bbcd44a8 · 2025-10-17T12:47:25.000-06:00
* DOC-893 Document feature UBB-BYOC

# Conflicts:
#	modules/get-started/pages/cloud-overview.adoc

* add placeholder section for Iceberg metrics in BYOC

* coderabbit fix

* revert back to original navigation

* clean up

* add to what's new

* Define RPU + minor edits

* Iceberg metric: tracks data written to Iceberg tables/hour (in GB).

* minor edits

* minor edit

* edits from Denis review

* add support plans: basic, enterprise, premium

* rename Billing and Support

* Update modules/billing/pages/billing.adoc

Co-authored-by: Joyce Fee &lt;102751339+Feediver1@users.noreply.github.com&gt;

* fixed header row bold

* calrify basic support hours

* minor edit

* update response time for basic support

* adjust table size

* formatting edit

* Edit Cluster metrics &gt; Usage-based billing metrics

* RPU review feedback

---------

Co-authored-by: Joyce Fee &lt;102751339+Feediver1@users.noreply.github.com&gt;
diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
@@ -449,10 +449,10 @@
 
 * xref:billing:index.adoc[Billing]
 ** xref:billing:billing.adoc[]
-** xref:billing:aws-pay-as-you-go.adoc[AWS: Use Pay As You Go]
 ** xref:billing:aws-commit.adoc[AWS: Use Commits]
 ** xref:billing:azure-commit.adoc[Azure: Use Commits]
 ** xref:billing:gcp-commit.adoc[GCP: Use Commits]
+** xref:billing:aws-pay-as-you-go.adoc[AWS: Use Pay As You Go]
 
 * xref:get-started:partner-integration.adoc[]
 
diff --git a/modules/billing/pages/aws-commit.adoc b/modules/billing/pages/aws-commit.adoc
@@ -2,7 +2,7 @@
 :description: Subscribe to Redpanda in AWS Marketplace with committed use.
 :page-aliases: deploy:deployment-option/cloud/manage-billing/aws-commit.adoc
 
-You can subscribe to Redpanda Cloud through AWS Marketplace and use your existing marketplace billing and credits to quickly provision Dedicated clusters. View your bills and manage your subscription directly in the marketplace.
+You can subscribe to Redpanda Cloud through AWS Marketplace and use your existing marketplace billing and credits to quickly provision clusters. View your bills and manage your subscription directly in the marketplace.
 
 With a usage-based billing commitment, you sign up for a minimum spend amount. Commitments are minimums: 
 
@@ -45,4 +45,5 @@ You can now create resource groups, clusters, and networks in your organization.
 == Next steps
 
 * xref:get-started:cluster-types/serverless.adoc#create-a-serverless-cluster[Create a Serverless cluster]
+* xref:get-started:cluster-types/byoc/index.adoc[Create a BYOC cluster]   
 * xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster-aws.adoc#create-a-dedicated-cluster[Create a Dedicated cluster]
diff --git a/modules/billing/pages/azure-commit.adoc b/modules/billing/pages/azure-commit.adoc
@@ -1,7 +1,7 @@
 = Use Azure Commitments
 :description: Subscribe to Redpanda in Azure Marketplace with committed use.
 
-You can subscribe to Redpanda Cloud through Azure Marketplace and use your existing marketplace billing and credits to quickly provision Dedicated clusters. View your bills and manage your subscription directly in the marketplace.
+You can subscribe to Redpanda Cloud through Azure Marketplace and use your existing marketplace billing and credits to quickly provision clusters. View your bills and manage your subscription directly in the marketplace.
 
 With a usage-based billing commitment, you sign up for a monthly or an annual minimum spend amount. Commitments are minimums: 
 
@@ -40,4 +40,5 @@ You can now create resource groups, clusters, and networks in your organization.
 
 == Next steps
 
+* xref:get-started:cluster-types/byoc/index.adoc[Create a BYOC cluster]   
 * xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster.adoc[Create a Dedicated cluster]
diff --git a/modules/billing/pages/billing.adoc b/modules/billing/pages/billing.adoc
@@ -1,18 +1,25 @@
-= Usage Metrics
+= Billing and Support 
 :description: Learn about the metrics Redpanda uses to measure consumption in Redpanda Cloud.
 :page-aliases: deploy:deployment-option/cloud/manage-billing/billing.adoc
 
 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.
 
 NOTE: Pricing information is available on https://www.redpanda.com/price-estimator[redpanda.com^]. For questions about billing, contact billing@redpanda.com.
 
-== Serverless metrics
+== Usage-based billing metrics
 
+[tabs]
+======
+Serverless::
++
+--
 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.
 
+[cols="1,3",options="header"]
 |=== 
 | Metric | Description  
 
@@ -35,17 +42,20 @@ All Kafka protocol responses generated by the cluster (_except_ message headers)
 |===
 
 See also: xref:get-started:cluster-types/serverless.adoc#serverless-usage-limits[Serverless limits]
+--
 
-== Dedicated metrics
-
+Dedicated::
++
+--
 Pricing for Dedicated clusters depends on the time the instance is up, the data in, data out, and data stored.
 
+[cols="1,3",options="header"]
 |=== 
 | Metric | Description 
 
 | Uptime | Tracks the number of hours the instance is running. 
 
-The cost varies based on the xref:reference:tiers/byoc-tiers.adoc[region and tier] you select for your cluster.   
+The cost varies based on the xref:reference:tiers/dedicated-tiers.adoc[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.
@@ -56,28 +66,96 @@ The cost varies based on the region you select for your cluster.
 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). 
+| 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 glossterm:Tiered Storage[]. All topics have a fixed replication factor of 3, but Redpanda counts each byte only once.
+
+|===
+--
+
+BYOC::
++
+--
+Pricing for BYOC clusters depends on compute, data in, data out, and data stored. The rate decreases as usage increases.
+
+
+[cols="1,3",options="header"]
+|=== 
+| 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 glossterm:Tiered Storage[]. All topics have a fixed replication factor of 3, but Redpanda counts each byte only once.
 
+
 |=== 
+--
+======
+
 
-== Redpanda Connect pipeline metrics (Dedicated and Serverless)
+== Redpanda Connect billing metrics
 
 Pricing per pipeline depends on:
 
 - The number of xref:develop:connect/configuration/resource-management.adoc[compute units] you allocate.
-- The cost of a compute unit, which varies based on the cloud provider and region you select for your cluster.
+- The cost of a compute unit, which can vary based on the cloud provider and region you select for your cluster.
 
+[cols="1,3",options="header"]
 |===
 | Metric | Description
 
-| Compute | Tracks the server resources (CPU and memory) a pipeline uses in compute units per hour.
-
+| 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:
+
+[cols="1,3",options="header"]
+|===
+| Support plan | Features
+
+| Basic 
+a| * 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 
+a| * Designed for production environments needing continuous availability
+* P1/P2 tickets may be submitted  
+* Support availability is 24/7, including holidays
+
+| Premium 
+a| * 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
 
-* xref:billing:gcp-commit.adoc[]
 * xref:billing:aws-commit.adoc[]
-* xref:billing:azure-commit.adoc[]
+* xref:billing:azure-commit.adoc[]
+* xref:billing:gcp-commit.adoc[]
+* xref:get-started:cluster-types/serverless.adoc#create-a-serverless-cluster[Create a Serverless cluster]
+* xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster-aws.adoc#create-a-dedicated-cluster[Create a Dedicated cluster]
+* xref:get-started:cluster-types/byoc/index.adoc[Create a BYOC cluster]
diff --git a/modules/billing/pages/gcp-commit.adoc b/modules/billing/pages/gcp-commit.adoc
@@ -2,7 +2,7 @@
 :description: Subscribe to Redpanda in Google Cloud Marketplace with committed use.
 :page-aliases: deploy:deployment-option/cloud/manage-billing/gcp-commit.adoc
 
-You can subscribe to Redpanda Cloud through Google Cloud Marketplace and use your existing marketplace billing and credits to quickly provision Dedicated clusters. View your bills and manage your subscription directly in the marketplace.
+You can subscribe to Redpanda Cloud through Google Cloud Marketplace and use your existing marketplace billing and credits to quickly provision clusters. View your bills and manage your subscription directly in the marketplace.
 
 With a usage-based billing commitment, you sign up for a monthly or an annual minimum spend amount. Commitments are minimums: 
 
@@ -44,4 +44,5 @@ You can now create resource groups, clusters, and networks in your organization.
 
 == Next steps
 
-* xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster-aws.adoc[Create a Dedicated cluster]
+* xref:get-started:cluster-types/byoc/index.adoc[Create a BYOC cluster]
+* xref:get-started:cluster-types/create-dedicated-cloud-cluster.adoc[Create a Dedicated cluster]
diff --git a/modules/develop/pages/connect/configuration/resource-management.adoc b/modules/develop/pages/connect/configuration/resource-management.adoc
@@ -1,12 +1,12 @@
-= Manage Pipeline Resources on BYOC and Dedicated Clusters
+= Manage Pipeline Resources on Clusters
 :description: Learn how to set an initial resource limit for a standard data pipeline (excluding Ollama AI components) and how to manually scale the pipeline’s resources to improve performance.
 :page-aliases: develop:connect/configuration/scale-pipelines.adoc
 
 {description}
 
 == Prerequisites
 
-- A running xref:get-started:cluster-types/byoc/index.adoc[BYOC] or xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster.adoc[Dedicated] cluster.
+- A running Redpanda Cloud cluster.
 - An estimate of the throughput of your data pipeline. You can get some basic statistics by running your data pipeline locally using the xref:redpanda-connect:components:processors/benchmark.adoc[`benchmark` processor].
 
 === Understanding compute units
@@ -17,7 +17,7 @@ For sizing purposes, one compute unit supports an estimated message throughput o
 
 You can allocate a maximum of 72 compute units per pipeline. You can add compute units in increments of one up to 15 compute units. Beyond this, scaling options increase to 33 and then to 72 compute units. This scaling strategy is based on the number of machine cores required to provision resources, which scale from two to four, and then to eight cores.
 
-Server resources are charged at an xref:billing:billing.adoc#redpanda-connect-pipeline-metrics-dedicated-and-serverless[hourly rate in compute unit hours (compute/hour)].
+Server resources are charged at an xref:billing:billing.adoc#redpanda-connect-pipeline-metrics[hourly rate in compute unit hours (compute/hour)].
 
 |===
 | Number of compute units | CPU | Memory
diff --git a/modules/get-started/pages/cloud-overview.adoc b/modules/get-started/pages/cloud-overview.adoc
@@ -10,7 +10,7 @@ TIP: For more detailed information about the Redpanda platform, see xref:get-sta
 
 Redpanda Cloud offers three fully-managed cloud deployment options, each designed for different use cases:
 
-* **<<Serverless>>**: Fastest way to get started with automatic scaling and pay-as-you-go billing
+* **<<Serverless>>**: Fastest way to get started with automatic scaling
 * **<<Dedicated>>**: Production clusters in Redpanda's cloud with enhanced isolation
 * **<<Bring Your Own Cloud (BYOC)>>**: Maximum control and security by deploying in your own cloud environment
 
@@ -129,9 +129,9 @@ When you create a Dedicated cluster, you select the supported xref:reference:tie
 Redpanda Sales::
 +
 --
-To request a private offer with possible discounts for monthly or annual committed use, contact https://www.redpanda.com/price-estimator[Redpanda Sales^]. With a usage-based billing commitment, you sign up for a minimum spend amount through xref:billing:aws-commit.adoc[AWS Marketplace], xref:billing:azure-commit.adoc[Azure Marketplace], or xref:billing:gcp-commit.adoc[Google Cloud Marketplace]. You can then provision Dedicated clusters in Redpanda Cloud, and you can view invoices and manage your subscription in the marketplace.
+To request a private offer with possible discounts for monthly or annual committed use, contact https://www.redpanda.com/price-estimator[Redpanda Sales^]. With a usage-based billing commitment, you sign up for a minimum spend amount through xref:billing:aws-commit.adoc[AWS Marketplace], xref:billing:azure-commit.adoc[Azure Marketplace], or xref:billing:gcp-commit.adoc[Google Cloud Marketplace]. 
 
-Redpanda creates a cloud organization for you and sends you a welcome email.
+Redpanda creates a cloud organization for you and sends you a welcome email. You can then provision Dedicated clusters in Redpanda Cloud, and you can view invoices and manage your subscription in the marketplace.
 --
 AWS Marketplace::
 +
diff --git a/modules/get-started/partials/gpq-quotas.adoc b/modules/get-started/partials/gpq-quotas.adoc
@@ -7,4 +7,4 @@ Headroom formulas:
 * vCPU spare = `3 x (vCPUs per node)`
 * Local SSD spare (GB) = `3 x (Storage size per node in GB)`
 
-For example, with per-node storage *1500 GB* (4 × 375 GB Local SSD) and instance type *n2d-standard-4* (4 vCPUs), keep *4500 GB* Local SSD and *12 vCPUs* of spare quota.
+For example, with per-node storage *1500 GB* (4 × 375 GB Local SSD) and machine type *n2d-standard-4* (4 vCPUs), keep *4500 GB* Local SSD and *12 vCPUs* of spare quota.
