Rename Redpanda Self-Managed to Redpanda Streaming

JakeSCahill · claude · JakeSCahill · commit e683f0a42719 · 2026-05-12T16:46:54.000+01:00
- Add product-name attribute to antora.yml for future maintainability
- Replace all instances of 'Redpanda Self-Managed' with {product-name} in content
- Update hardcoded instances in README and CI files

Co-Authored-By: Claude Opus 4.5 &lt;noreply@anthropic.com&gt;
diff --git a/.github/workflows/test-docs.yml b/.github/workflows/test-docs.yml
@@ -80,7 +80,7 @@ jobs:
           create_issue_on_fail: true
           token: ${{ env.ACTIONS_BOT_TOKEN }}
 
-      - name: Test Redpanda Self-Managed quickstart
+      - name: Test Redpanda Streaming quickstart
         if: ${{ needs.setup.outputs.quickstart == 'true' || needs.setup.outputs.console == 'true' }}
         uses: doc-detective/github-action@v1
         with:
diff --git a/README.adoc b/README.adoc
@@ -16,7 +16,7 @@ image:https://img.shields.io/coderabbit/prs/github/redpanda-data/docs?utm_source
 </p></a>
 ++++
 
-This repository hosts the documentation content for Redpanda Self-Managed.
+This repository hosts the documentation content for Redpanda Streaming.
 
 == Contribute
 
@@ -94,7 +94,7 @@ npm run serve
 
 == Versioning
 
-Versioned content is stored in branches that track the version of Redpanda Self-Managed. Production branches use the *v/x.y* naming pattern. For example, branch `v/22.3` hosts the content for version 22.3.x of Redpanda Self-Managed. The `main` branch always contains docs for the latest release.
+Versioned content is stored in branches that track the version of Redpanda Streaming. Production branches use the *v/x.y* naming pattern. For example, branch `v/22.3` hosts the content for version 22.3.x of Redpanda Streaming. The `main` branch always contains docs for the latest release.
 
 The production {url-playbook}[docs site playbook] instructs Antora to automatically aggregate content in the following branches:
 
diff --git a/antora.yml b/antora.yml
@@ -6,6 +6,8 @@ nav:
 - modules/ROOT/nav.adoc
 asciidoc:
   attributes:
+    # Product name used throughout the documentation
+    product-name: Redpanda Streaming
     # Date of release in the format YYYY-MM-DD
     page-release-date: 2025-07-31
     # Only used in the main branch (latest version)
@@ -86,7 +88,7 @@ asciidoc:
       - page: develop/guide-nodejs/
         reason: Page moved to Redpanda Labs.
     # Data for the home page
-    page-home-intro: Redpanda is a Kafka-compatible event streaming platform built for data-intensive applications. Install Self-Managed Redpanda in your environment with the free Community Edition or with the Enterprise Edition for additional features like Tiered Storage, Continuous Data Balancing, and Audit Logging. 
+    page-home-intro: Redpanda is a Kafka-compatible event streaming platform built for data-intensive applications. Install Redpanda Streaming in your environment with the free Community Edition or with the Enterprise Edition for additional features like Tiered Storage, Continuous Data Balancing, and Audit Logging. 
     #page-home-image:
     page-home-intro-learn-more: get-started:intro-to-events.adoc
     page-home-primary-row-title: Deploy
@@ -118,7 +120,7 @@ asciidoc:
         url: 'manage:monitoring.adoc'
         link-text: 'Learn more'
       - title: 'rpk commands'
-        description: 'Redpanda CLI reference for Self-Managed Redpanda.'
+        description: 'Redpanda CLI reference for Redpanda Streaming.'
         url: 'reference:rpk/index.adoc'
         link-text: 'Learn more'
     page-home-tertiary-row-title: 'Labs'
diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
@@ -9,7 +9,7 @@
 ** xref:console:index.adoc[Introduction to Redpanda Console]
 ** xref:get-started:install-beta.adoc[Install Beta]
 ** xref:get-started:quickstarts.adoc[Quickstarts]
-*** xref:get-started:quick-start.adoc[Redpanda Self-Managed]
+*** xref:get-started:quick-start.adoc[{product-name}]
 *** xref:get-started:rpk-quickstart.adoc[]
 *** xref:get-started:docker-compose-labs.adoc[Docker Compose Labs]
 ** xref:get-started:licensing/index.adoc[Redpanda Licensing]
diff --git a/modules/console/pages/ui/add-license.adoc b/modules/console/pages/ui/add-license.adoc
@@ -39,7 +39,7 @@ If the existing license expires soon, you can click the *Upload license* button
 +
 image::console:license.png[]
 +
-When a new license is uploaded, enterprise features in Redpanda Self-Managed are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.
+When a new license is uploaded, enterprise features in {product-name} are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.
 
 After restarting Redpanda Console, enterprise features such as RBAC are unlocked. However, to enable and use these features, you must configure them. See xref:console:config/index.adoc[].
 
diff --git a/modules/deploy/pages/index.adoc b/modules/deploy/pages/index.adoc
@@ -1,5 +1,5 @@
 = Self-Managed Deployment
-:description: Learn about Redpanda Self-Managed deployments.
+:description: Learn about {product-name} deployments.
 :page-layout: index
 :page-aliases: deployment:index.adoc, deployment:index/index.adoc, deploy:deployment-option/index.adoc, deploy:deployment-option/index/index.adoc, deploy:index/index.adoc, deploy:deployment-option/self-hosted/index.adoc
 :page-categories: Deployment
diff --git a/modules/get-started/pages/docker-compose-labs.adoc b/modules/get-started/pages/docker-compose-labs.adoc
@@ -1,7 +1,7 @@
 = Docker Compose Labs
 :page-index-data: docker-labs-index
 :page-role: index-list
-:description: Explore this collection of hands-on labs for deploying and testing Redpanda Self-Managed using Docker Compose. Whether you're a beginner looking to get started or an experienced user aiming to deepen your knowledge, these labs provide step-by-step instructions and practical examples to enhance your skills.
+:description: Explore this collection of hands-on labs for deploying and testing {product-name} using Docker Compose. Whether you're a beginner looking to get started or an experienced user aiming to deepen your knowledge, these labs provide step-by-step instructions and practical examples to enhance your skills.
 
 {description}
 
diff --git a/modules/get-started/pages/intro-to-events.adoc b/modules/get-started/pages/intro-to-events.adoc
@@ -59,20 +59,20 @@ Raft facilitates communication between the nodes in a Redpanda cluster to make s
 +
 With the Bring Your Own Cloud (BYOC) offering, you deploy Redpanda in your own virtual private cloud, and all data is contained in your environment. Redpanda handles provisioning, monitoring, and upgrades, but you manage your streaming data without Redpanda's control plane ever seeing it.
 
-== Redpanda Self-Managed versions
+== {product-name} versions
 
-You can deploy Redpanda in a self-hosted environment (Redpanda Self-Managed) or as a fully managed cloud service (Redpanda Cloud).
+You can deploy Redpanda in a self-hosted environment ({product-name}) or as a fully managed cloud service (Redpanda Cloud).
 
-Redpanda Self-Managed version numbers follow the convention AB.C.D, where AB is the two-digit year, C is the feature release, and D is the patch release. For example, version 22.3.1 indicates the first patch release on the third feature release of the year 2022. Patch releases include bug fixes and minor improvements, with no change to user-facing behavior. New and enhanced features are documented with each feature release.
+{product-name} version numbers follow the convention AB.C.D, where AB is the two-digit year, C is the feature release, and D is the patch release. For example, version 22.3.1 indicates the first patch release on the third feature release of the year 2022. Patch releases include bug fixes and minor improvements, with no change to user-facing behavior. New and enhanced features are documented with each feature release.
 
-Redpanda Cloud releases on a continuous basis and uptakes Redpanda Self-Managed versions.
+Redpanda Cloud releases on a continuous basis and uptakes {product-name} versions.
 
 ifndef::env-cloud[]
 == Next steps
 
 * To spin up a Redpanda cluster to try it out, see xref:./quick-start.adoc[Redpanda Quickstart].
 * To learn more about Redpanda, see xref:./architecture.adoc[How Redpanda Works].
-* For information about a Redpanda Self-Managed deployment, see xref:./licenses.adoc[Redpanda Licensing].
+* For information about a {product-name} deployment, see xref:./licenses.adoc[Redpanda Licensing].
 * For information about a Redpanda Cloud deployment, see xref:cloud-data-platform:get-started:cloud-overview.adoc[].
 
 include::shared:partial$suggested-reading.adoc[]
diff --git a/modules/get-started/pages/licensing/add-license-redpanda/index.adoc b/modules/get-started/pages/licensing/add-license-redpanda/index.adoc
@@ -1,3 +1,3 @@
 = Add an Enterprise Edition License to Redpanda
 :page-layout: index
-:description: Learn how to add an Enterprise Edition license to Redpanda Self-Managed.
+:description: Learn how to add an Enterprise Edition license to {product-name}.
diff --git a/modules/get-started/pages/licensing/add-license-redpanda/kubernetes.adoc b/modules/get-started/pages/licensing/add-license-redpanda/kubernetes.adoc
@@ -2,7 +2,7 @@
 :description: Learn how to add or update a Redpanda Enterprise Edition license in a Kubernetes environment.
 :env-kubernetes: true
 
-To enable xref:get-started:licensing/overview.adoc[enterprise features for Redpanda Self-Managed], you must have an Enterprise Edition license. This guide outlines how to apply or update an Enterprise Edition license for Redpanda Self-Managed in a Kubernetes environment.
+To enable xref:get-started:licensing/overview.adoc[enterprise features for {product-name}], you must have an Enterprise Edition license. This guide outlines how to apply or update an Enterprise Edition license for {product-name} in a Kubernetes environment.
 
 == Prerequisites
 
@@ -182,7 +182,7 @@ The process for updating a license depends on how it was originally applied:
 - <<inline-update, Update the license string inline in your Helm values or manifest file>>.
 - xref:console:ui/add-license.adoc[Use Redpanda Console]
 
-When a new license is uploaded, enterprise features in Redpanda Self-Managed are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.
+When a new license is uploaded, enterprise features in {product-name} are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.
 
 [[secret-update]]
 === Update the Kubernetes Secret
diff --git a/modules/get-started/pages/licensing/add-license-redpanda/linux.adoc b/modules/get-started/pages/licensing/add-license-redpanda/linux.adoc
@@ -1,7 +1,7 @@
 = Add an Enterprise Edition License to Redpanda in Linux
 :description: Learn how to add or update a Redpanda Enterprise Edition license in a Linux environment.
 
-To enable xref:get-started:licensing/overview.adoc[enterprise features for Redpanda Self-Managed], you must have an Enterprise Edition license. This guide outlines how to apply or update an Enterprise Edition license for Redpanda Self-Managed in a Linux environment.
+To enable xref:get-started:licensing/overview.adoc[enterprise features for {product-name}], you must have an Enterprise Edition license. This guide outlines how to apply or update an Enterprise Edition license for {product-name} in a Linux environment.
 
 == Prerequisites
 
@@ -62,7 +62,7 @@ To update an existing license, you can use one the following methods:
 - xref:reference:rpk/rpk-cluster/rpk-cluster-license-set.adoc[]
 - xref:console:ui/add-license.adoc[Redpanda Console]
 
-When a new license is uploaded, enterprise features in Redpanda Self-Managed are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.
+When a new license is uploaded, enterprise features in {product-name} are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.
 
 == Next steps
 
diff --git a/modules/get-started/pages/licensing/overview.adoc b/modules/get-started/pages/licensing/overview.adoc
@@ -14,7 +14,7 @@ Redpanda, Redpanda Console, and Redpanda Connect are available in community and
 
 [TIP]
 ====
-Go to the Redpanda Self-Managed quickstart to set up a local Redpanda cluster and try the Enterprise Edition free for up to 60 days.
+Go to the {product-name} quickstart to set up a local Redpanda cluster and try the Enterprise Edition free for up to 60 days.
 ====
 
 :tip-caption: Tip
diff --git a/modules/get-started/pages/quick-start.adoc b/modules/get-started/pages/quick-start.adoc
@@ -1,4 +1,4 @@
-= Redpanda Self-Managed Quickstart
+= {product-name} Quickstart
 :description: Learn how to quickly start working with a local Redpanda cluster that comes with a free 30-day license for Enterprise Edition. You can also extend the trial license for a further 30 days.
 :page-aliases: install-upgrade:index.adoc, install-upgrade:index/index.adoc, install-upgrade:start-streaming.adoc, quickstart:console-installation, quickstart:quick-start-docker.adoc, quickstart:quick-start-linux.adoc, quickstart:quick-start-macos.adoc, quickstart:quick-start-windows.adoc, getting-started:quick-start-docker.adoc, getting-started:quick-start-linux.adoc, getting-started:quick-start-windows.adoc, getting-started:quick-start-macos.adoc, console:installation.adoc, get-started:quick-start/quick-start-console.adoc, get-started:quick-start/quick-start-macos.adoc, get-started:quick-start/quick-start-linux.adoc, get-started:quick-start/quick-start-docker.adoc, manage:console/quickstart.adoc, console:quickstart.adoc, console:labs.adoc
 :page-categories: Deployment, Development, rpk, Redpanda Console
@@ -8,11 +8,11 @@
 // ========================AUTOMATED TESTS===================================
 // The comments in this file are used to run automated tests of the documented steps. Tests are run using GitHub Actions on each pull request that changes this file in the upstream repository. For more details about the testing tool we use, see https://doc-detective.com/.
 
-// (test start {"testId": "quickstart", "description": "Redpanda Self-Managed quickstart"})
+// (test start {"testId": "quickstart", "description": "{product-name} quickstart"})
 
 {description}
 
-Redpanda Self-Managed is a modern streaming platform, compatible with Kafka APIs, designed for speed, simplicity, and efficiency. In this quickstart, you:
+{product-name} is a modern streaming platform, compatible with Kafka APIs, designed for speed, simplicity, and efficiency. In this quickstart, you:
 
 - Deploy a three-broker Redpanda cluster.
 - Explore streaming data in Redpanda Console.
@@ -29,7 +29,7 @@ This quickstart uses Docker to run Redpanda, which is only for development and t
 
 == Enterprise features
 
-The Enterprise Edition of Redpanda Self-Managed adds advanced capabilities to help scale, manage, optimize, and secure your cluster.
+The Enterprise Edition of {product-name} adds advanced capabilities to help scale, manage, optimize, and secure your cluster.
 
 All new Redpanda clusters include a built-in 30-day Enterprise Edition license, so you can evaluate enterprise features. Some features highlighted in this quickstart require an enterprise license:
 
@@ -82,9 +82,9 @@ https://docs.microsoft.com/en-us/windows/wsl/install[Windows Subsystem for Linux
 
 :note-caption: Note
 
-== Deploy Redpanda Self-Managed
+== Deploy {product-name}
 
-To download, extract, and start Redpanda Self-Managed in Docker, run:
+To download, extract, and start {product-name} in Docker, run:
 
 [,bash,subs="attributes+"]
 ----
@@ -803,7 +803,7 @@ rpk connect run <path-to-config>
 https://www.redpanda.com/contact[Contact Redpanda^] to discuss using Redpanda Enterprise Edition in production.
 
 - xref:labs:ROOT:index.adoc[Try more examples in Redpanda Labs]
-- xref:get-started:licensing/overview.adoc[Learn more about enterprise features for Redpanda Self-Managed]
+- xref:get-started:licensing/overview.adoc[Learn more about enterprise features for {product-name}]
 - xref:deploy:redpanda/manual/production/index.adoc[Deploy for development or production]
 
 == Suggested reading
diff --git a/modules/get-started/pages/rpk-install.adoc b/modules/get-started/pages/rpk-install.adoc
@@ -12,7 +12,7 @@ The `rpk` tool is a single binary application that provides a way to interact wi
 * Set up access control lists (ACLs) and other security features
 
 ifndef::env-cloud[]
-For Redpanda Self-Managed deployments, the `rpk` binary is automatically installed on each Redpanda broker, so you can use the locally installed `rpk` binary to communicate with the local Redpanda cluster.
+For {product-name} deployments, the `rpk` binary is automatically installed on each Redpanda broker, so you can use the locally installed `rpk` binary to communicate with the local Redpanda cluster.
 
 You can also install `rpk` on your local machine as a standalone binary. With this setup, you can connect to a Redpanda cluster on your local machine and to an external one on a remote server. If you use `rpk` as a standalone binary to communicate with a Redpanda cluster, your installed version of `rpk` must match the version of Redpanda running in your cluster.
 endif::[]
diff --git a/modules/home/pages/index.adoc b/modules/home/pages/index.adoc
@@ -1,4 +1,4 @@
-= Redpanda Self-Managed Documentation
+= {product-name} Documentation
 :page-role: component-home-v2
 :description: Home page for the Redpanda docs site.
 
diff --git a/modules/manage/pages/cluster-maintenance/disk-utilization.adoc b/modules/manage/pages/cluster-maintenance/disk-utilization.adoc
@@ -19,7 +19,7 @@ Redpanda provides several ways to manage disk space, with varying degrees of fle
 
 == Configure message retention
 
-By default, all topics on Redpanda Self-Managed clusters retain 24 hours of data on local disk, while Redpanda Cloud topics retain 6 hours of data. Redpanda makes use of dynamic xref:#space_management[space management] strategies to save on disk space. If data is written fast enough, however, it's possible to exhaust local disk space even when using Tiered Storage. Proper configuration of message retention properties for your use case can prevent this from happening.
+By default, all topics on {product-name} clusters retain 24 hours of data on local disk, while Redpanda Cloud topics retain 6 hours of data. Redpanda makes use of dynamic xref:#space_management[space management] strategies to save on disk space. If data is written fast enough, however, it's possible to exhaust local disk space even when using Tiered Storage. Proper configuration of message retention properties for your use case can prevent this from happening.
 
 Retention properties control the minimum length of time messages are kept on disk before they're deleted or compacted. Setting message retention properties is the best way to prevent old messages from accumulating on disk to the point that the disk becomes full. You can configure retention properties to delete messages based on the following conditions:
 
diff --git a/modules/manage/pages/iceberg/use-iceberg-catalogs.adoc b/modules/manage/pages/iceberg/use-iceberg-catalogs.adoc
@@ -64,7 +64,7 @@ endif::[]
 ifndef::env-cloud[]
 === Limitations
 
-The Iceberg integration for Redpanda Self-Managed supports multiple Iceberg catalogs, with progressive levels of release maturity. Each catalog integration is tested and released independently.
+The Iceberg integration for {product-name} supports multiple Iceberg catalogs, with progressive levels of release maturity. Each catalog integration is tested and released independently.
 
 The following shows the current status of Iceberg catalog integrations. Check this list regularly as Redpanda continues to expand GA coverage for Iceberg topics.
 
diff --git a/modules/manage/pages/schema-reg/manage-schema-reg.adoc b/modules/manage/pages/schema-reg/manage-schema-reg.adoc
@@ -1,5 +1,5 @@
 = Use Schema Registry
 :page-layout: index
-:description: Learn how to add, delete, and update schemas in Redpanda Self-Managed.
+:description: Learn how to add, delete, and update schemas in {product-name}.
 
 {description}
diff --git a/modules/manage/pages/security/iam-roles.adoc b/modules/manage/pages/security/iam-roles.adoc
diff --git a/modules/manage/partials/remote-read-replicas.adoc b/modules/manage/partials/remote-read-replicas.adoc
diff --git a/modules/reference/pages/api-reference.adoc b/modules/reference/pages/api-reference.adoc
diff --git a/modules/reference/partials/rpk-cloud/rpk-cloud-auth-use.adoc b/modules/reference/partials/rpk-cloud/rpk-cloud-auth-use.adoc
diff --git a/modules/upgrade/partials/versioning.adoc b/modules/upgrade/partials/versioning.adoc
diff --git a/tests/docker-compose/transform/README.adoc b/tests/docker-compose/transform/README.adoc

Original file line number	Diff line number	Diff line change
`@@ -39,7 +39,7 @@ If the existing license expires soon, you can click the Upload license button`
`39`	`39`	`+`
`40`	`40`	`image::console:license.png[]`
`41`	`41`	`+`
`42`		`-When a new license is uploaded, enterprise features in Redpanda Self-Managed are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.`
	`42`	`+When a new license is uploaded, enterprise features in {product-name} are unlocked immediately without requiring a cluster restart. However, to unlock enterprise features in Redpanda Console, you must restart the Redpanda Console instance.`
`43`	`43`
`44`	`44`	`After restarting Redpanda Console, enterprise features such as RBAC are unlocked. However, to enable and use these features, you must configure them. See xref:console:config/index.adoc[].`
`45`	`45`