redpanda-data · JakeSCahill · May 7, 2026 · May 12, 2026
@@ -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:

@@ -12,7 +12,7 @@ asciidoc:
     # Header configuration
     page-header-data:
       order: 1
-      color: '#F77923'
+      color: '#ea580c'
       text-color: '#ffffff'
     # UI name for single-sourced content
     ui: Redpanda Cloud
@@ -26,7 +26,7 @@ After reading this page, you will be able to:
 
 With Redpanda AI agents, you declare the agent behavior you want and Redpanda handles execution and orchestration. Instead of writing Python or JavaScript, you define behaviors in YAML. You can orchestrate multiple specialized glossterm:subagent[,sub-agents], or bring your own frameworks like LangChain or LlamaIndex.
 
-What makes this practical at scale is xref:redpanda-cloud:develop:connect/about.adoc[Redpanda Connect]. More than 300 connectors with built-in filtering, enrichment, and routing give declarative definitions real power. Upcoming templates will provide default behaviors for common domains such as customer success, legal, and finance.
+What makes this practical at scale is xref:cloud-data-platform:develop:connect/about.adoc[Redpanda Connect]. More than 300 connectors with built-in filtering, enrichment, and routing give declarative definitions real power. Upcoming templates will provide default behaviors for common domains such as customer success, legal, and finance.
 
 The result is faster time-to-production, lower maintenance (declarative definitions instead of imperative code), and organizational consistency across teams.
 

@@ -53,4 +53,4 @@ The default Writer role provides broad access suitable for most use cases. If yo
 . Find the service account for your resource.
 . Edit the role bindings to use a more restrictive role or scope.
 
-For more information about roles and permissions, see xref:redpanda-cloud:security:authorization/rbac/rbac.adoc[Role-based access control] or xref:redpanda-cloud:security:authorization/gbac/gbac.adoc[Group-based access control].
+For more information about roles and permissions, see xref:cloud-data-platform:security:authorization/rbac/rbac.adoc[Role-based access control] or xref:cloud-data-platform:security:authorization/gbac/gbac.adoc[Group-based access control].
@@ -58,7 +58,7 @@ For integration pattern guidance, see xref:integration-overview.adoc[].
 
 === Internal pipeline-to-agent integration
 
-Redpanda Connect pipelines use the xref:redpanda-cloud:develop:connect/components/processors/a2a_message.adoc[`a2a_message`] processor to invoke agents for each event in a stream. This enables real-time interaction between streaming data and AI agents, enabling use cases like:
+Redpanda Connect pipelines use the xref:cloud-data-platform:develop:connect/components/processors/a2a_message.adoc[`a2a_message`] processor to invoke agents for each event in a stream. This enables real-time interaction between streaming data and AI agents, enabling use cases like:
 
 * Real-time fraud detection on every transaction.
 * Streaming data enrichment with AI-generated fields.
@@ -104,7 +104,7 @@ This flow ensures:
 
 External applications must authenticate using the service account credentials. Each agent has its own service account.
 
-For step-by-step authentication instructions, see xref:redpanda-cloud:security:cloud-authentication.adoc[].
+For step-by-step authentication instructions, see xref:cloud-data-platform:security:cloud-authentication.adoc[].
 
 === Internal integration
 

@@ -1,4 +1,5 @@
 = Register Your Own Agent (BYOA)
 :description: Connect your existing AI agent to Redpanda ADP for observability and governance.
+:page-byoc-only: true
 
 // TODO: Add content
@@ -1,5 +1,6 @@
 = Create an Agent
 :description: Declaratively configure an agent by choosing an LLM, writing a system prompt, connecting tools from built-in connectors, and setting execution parameters.
+:page-cloud-only: true
 :page-topic-type: how-to
 :personas: agent_developer, app_developer, streaming_developer
 :learning-objective-1: Configure an agent with model selection and system prompt

@@ -115,7 +115,7 @@ When integrating external applications with ADP agents, protect credentials and
 
 === Protect service account credentials
 
-Store the client ID and secret in secure credential stores, not in code. Use environment variables or xref:redpanda-cloud:security:secrets.adoc[secrets management]. Rotate credentials if compromised and restrict access based on the principle of least privilege.
+Store the client ID and secret in secure credential stores, not in code. Use environment variables or xref:cloud-data-platform:security:secrets.adoc[secrets management]. Rotate credentials if compromised and restrict access based on the principle of least privilege.
 
 === Protect access tokens
 

@@ -18,7 +18,7 @@ This page focuses on pipelines calling agents (pipeline-initiated integration).
 
 == How pipelines invoke agents
 
-Pipelines use the xref:redpanda-cloud:develop:connect/components/processors/a2a_message.adoc[`a2a_message`] processor to invoke agents for each event in a stream. The processor uses the xref:a2a-concepts.adoc[A2A protocol] to discover and communicate with agents.
+Pipelines use the xref:cloud-data-platform:develop:connect/components/processors/a2a_message.adoc[`a2a_message`] processor to invoke agents for each event in a stream. The processor uses the xref:a2a-concepts.adoc[A2A protocol] to discover and communicate with agents.
 
 When the `a2a_message` processor receives an event, it sends the event data to the specified agent along with any prompt you provide. The agent processes the event using its reasoning capabilities and returns a response. The processor then adds the agent's response to the event for further processing or output.
 
@@ -140,4 +140,4 @@ This pipeline:
 * xref:mcp:overview.adoc[]
 * xref:integration-overview.adoc[]
 * xref:a2a-concepts.adoc[]
-* xref:redpanda-cloud:develop:connect/components/processors/about.adoc[]
+* xref:cloud-data-platform:develop:connect/components/processors/about.adoc[]
@@ -36,7 +36,7 @@ The challenge: users phrase requests differently ("Where's my package?", "Track
 
 == Prerequisites
 
-* A xref:redpanda-cloud:get-started:cluster-types/byoc/index.adoc[BYOC cluster].
+* A xref:cloud-data-platform:get-started:cluster-types/byoc/index.adoc[BYOC cluster].
 * xref:ai-gateway:gateway-quickstart.adoc[AI Gateway configured] with at least one LLM provider enabled (this tutorial uses OpenAI).
 
 == Design the MCP tools

@@ -32,9 +32,9 @@ When a customer calls saying "I see a $247.83 charge from 'ACME CORP' but I neve
 
 == Prerequisites
 
-* A xref:redpanda-cloud:get-started:cluster-types/byoc/index.adoc[BYOC cluster].
+* A xref:cloud-data-platform:get-started:cluster-types/byoc/index.adoc[BYOC cluster].
 * xref:ai-gateway:gateway-quickstart.adoc[AI Gateway configured] with at least one LLM provider enabled (this tutorial uses OpenAI GPT-5.2 or Claude Sonnet 4.5 for reasoning).
-* The xref:redpanda-cloud:manage:rpk/rpk-install.adoc[Redpanda CLI (`rpk`)] installed (for testing the pipeline with sample data).
+* The xref:cloud-data-platform:manage:rpk/rpk-install.adoc[Redpanda CLI (`rpk`)] installed (for testing the pipeline with sample data).
 * Completed xref:tutorials/customer-support-agent.adoc[] (foundational multi-tool concepts).
 
 == Create MCP tools for each domain

@@ -19,7 +19,7 @@ After completing this guide, you will be able to:
 
 * A configured LLM provider. If you haven't created one yet, see xref:ai-gateway:configure-provider.adoc[Configure an LLM provider].
 * For local development, nothing else. You'll install `rpk ai` in the next section.
-* For CI or programmatic clients: a Redpanda Cloud service account with OIDC client credentials. See xref:redpanda-cloud:security:cloud-authentication.adoc[Authenticate to Redpanda Cloud].
+* For CI or programmatic clients: a Redpanda Cloud service account with OIDC client credentials. See xref:cloud-data-platform:security:cloud-authentication.adoc[Authenticate to Redpanda Cloud].
 +
 // TODO: confirm whether ADP hosts its own service-account IAM post-standalone, or continues to share Redpanda Cloud Organization IAM.
 * A development environment with your chosen programming language.

@@ -19,7 +19,7 @@ After reading this page, you will be able to:
 
 * A Redpanda Connect pipeline host (today: a Redpanda BYOC cluster with Connect enabled). Ability to manage secrets on that host.
 // TODO: Replace with the standalone-ADP ingestion target once defined (may no longer require a Redpanda Cloud cluster).
-* The latest version of xref:redpanda-cloud:manage:rpk/rpk-install.adoc[`rpk`] installed
+* The latest version of xref:cloud-data-platform:manage:rpk/rpk-install.adoc[`rpk`] installed
 * Custom agent or application instrumented with OpenTelemetry SDK
 * Basic understanding of the https://opentelemetry.io/docs/specs/semconv/gen-ai/gen-ai-agent-spans/[OpenTelemetry span format^] and https://opentelemetry.io/docs/specs/otlp/[OpenTelemetry Protocol (OTLP)^]
 
@@ -64,7 +64,7 @@ When these agents send traces to `redpanda.otel_traces`, you gain unified observ
 
 === Trace format requirements
 
-Custom agents must emit traces in OTLP format. The xref:redpanda-connect:components:inputs/otlp_http.adoc[`otlp_http`] input accepts both OTLP Protobuf (`application/x-protobuf`) and JSON (`application/json`) payloads. For <<use-grpc,gRPC transport>>, use the xref:redpanda-connect:components:inputs/otlp_grpc.adoc[`otlp_grpc`] input.
+Custom agents must emit traces in OTLP format. The xref:connect:components:inputs/otlp_http.adoc[`otlp_http`] input accepts both OTLP Protobuf (`application/x-protobuf`) and JSON (`application/json`) payloads. For <<use-grpc,gRPC transport>>, use the xref:connect:components:inputs/otlp_grpc.adoc[`otlp_grpc`] input.
 
 Each trace must follow the OTLP specification with these required fields:
 
@@ -197,7 +197,7 @@ Configure your custom agent to send OpenTelemetry traces to the pipeline endpoin
 
 === Authenticate to the pipeline
 
-The OTLP pipeline authenticates with a service account access token (today, while ingestion runs on a Redpanda BYOC cluster). Obtain an access token using your service account credentials as described in xref:redpanda-cloud:security:cloud-authentication.adoc#authenticate-to-the-cloud-api[Authenticate to the Cloud API].
+The OTLP pipeline authenticates with a service account access token (today, while ingestion runs on a Redpanda BYOC cluster). Obtain an access token using your service account credentials as described in xref:cloud-data-platform:security:cloud-authentication.adoc#authenticate-to-the-cloud-api[Authenticate to the Cloud API].
 // TODO (standalone-ADP): Update the auth model when the standalone ADP ingestion path is defined.
 
 Include the token in your requests:
@@ -621,5 +621,5 @@ If requests succeed but traces do not appear in `redpanda.otel_traces`:
 
 * xref:observability:transcripts.adoc[]
 * xref:agents:monitor.adoc[Observability for declarative agents]
-* xref:redpanda-connect:components:inputs/otlp_http.adoc[OTLP HTTP input reference]
-* xref:redpanda-connect:components:inputs/otlp_grpc.adoc[OTLP gRPC input reference]
+* xref:connect:components:inputs/otlp_http.adoc[OTLP HTTP input reference]
+* xref:connect:components:inputs/otlp_grpc.adoc[OTLP gRPC input reference]
@@ -1,6 +1,6 @@
 = Modify the Wasm Transform in the Quickstart
 
-This directory contains the Go source code (`transform.go`) for the data transform that is used in the Redpanda Self-Managed quickstart.
+This directory contains the Go source code (`transform.go`) for the data transform that is used in the Redpanda Streaming quickstart.
 If you're following the quickstart, you *do not* need to modify or rebuild this code. The Docker Compose configuration automatically deploys a pre-built transform called `regex.wasm`.
 
 However, if you want to customize the data transform logic, continue reading.