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

@@ -1,4 +1,4 @@
-name: redpanda-adp
+name: agentic-data-plane
 title: Agentic Data Plane
 version: ~
 start_page: ROOT:index.adoc
@@ -9,10 +9,18 @@ asciidoc:
     # Environment flags for conditional content
     env-adp: true
     page-adp: true
+    # AI suggestions for chat drawer (component-specific)
+    ai-suggestion-1: "How do I build my first agent?"
+    ai-suggestion-2: "Set up MCP with Postgres"
+    ai-suggestion-3: "Rotate an API key safely"
+    ai-suggestion-4: "What's a token budget?"
     # Header configuration
-    page-header-data:
+    component-metadata:
+      title: "Agentic Data Plane"
+      description: "Build AI agents with real-time data"
       order: 1
-      color: '#F77923'
+      color: '#C1331A'
       text-color: '#ffffff'
+      icon: "sparkles"
     # UI name for single-sourced content
     ui: Redpanda Cloud
@@ -7,7 +7,7 @@
 :learning-objective-1: Identify the key components of Redpanda ADP and their purposes
 :learning-objective-2: Describe how each component addresses enterprise governance and reliability requirements
 :learning-objective-3: Determine whether Redpanda ADP fits your organization's requirements for AI agent deployment
-// TODO: Add 'redpanda-cloud:ai-agents:index.adoc' to page-aliases after ai-agents is removed from cloud-docs
+// TODO: Add 'cloud-data-platform:ai-agents:index.adoc' to page-aliases after ai-agents is removed from cloud-docs
 :page-aliases: develop:agents/about.adoc, develop:ai-agents/about.adoc
 
 As glossterm:AI agent[,AI agents] evolve from experimental prototypes to business-critical systems, companies face new challenges. How do you ensure your AI agents are reliable? How do you maintain control over costs and compliance? And how do you scale them across your organization without creating technical debt?
@@ -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:agents: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
 

@@ -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
 

@@ -1,5 +1,5 @@
 = AI Agents Overview
-:page-aliases: redpanda-cloud:ai-agents:agents/overview.adoc
+:page-aliases: cloud-data-platform:ai-agents:agents/overview.adoc
 :description: Learn how ADP agents use a declarative approach backed by 300+ built-in connectors to replace custom agent code.
 :page-topic-type: overview
 :personas: evaluator, agent_developer, app_developer, streaming_developer

@@ -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:agents: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:agents: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:agents:integration-overview.adoc[]
 * xref:agents:a2a-concepts.adoc[]
-* xref:redpanda-cloud:develop:connect/components/processors/about.adoc[]
+* xref:cloud-data-platform:develop:connect/components/processors/about.adoc[]
@@ -1,5 +1,5 @@
 = AI Agent Quickstart
-:page-aliases: redpanda-cloud:ai-agents:agents/quickstart.adoc
+:page-aliases: cloud-data-platform:ai-agents:agents/quickstart.adoc
 :description: Create your first AI agent in ADP that generates and publishes event data through natural language commands.
 :page-topic-type: tutorial
 :personas: agent_developer, evaluator

@@ -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 environment].
+* A xref:cloud-data-platform:get-started:cluster-types/byoc/index.adoc[BYOC environment].
 * 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,7 +32,7 @@ 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 environment].
+* A xref:cloud-data-platform:get-started:cluster-types/byoc/index.adoc[BYOC environment].
 * 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:get-started: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).

@@ -2,7 +2,7 @@
 :description: Point your application or AI agent at an AI Gateway provider's proxy URL. Covers the URL shape, the local development workflow with `rpk ai`, the OIDC client-credentials flow for CI and application code, and SDK examples for OpenAI, Anthropic, Google AI, AWS Bedrock, and OpenAI-compatible endpoints.
 :page-topic-type: how-to
 :personas: app_developer
-:page-aliases: redpanda-cloud:ai-agents:ai-gateway/builders/connect-your-agent.adoc
+:page-aliases: cloud-data-platform:ai-agents:ai-gateway/builders/connect-your-agent.adoc
 :learning-objective-1: Construct the proxy URL for an LLM provider you have configured
 :learning-objective-2: pass:q[Authenticate to AI Gateway with `rpk` for local development or with OIDC client credentials for CI and programmatic clients]
 :learning-objective-3: Send requests through the proxy URL with the SDK of your choice
@@ -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.

@@ -1,5 +1,5 @@
 = AI Gateway Quickstart
-:page-aliases: redpanda-cloud:ai-agents:ai-gateway/gateway-quickstart.adoc
+:page-aliases: cloud-data-platform:ai-agents:ai-gateway/gateway-quickstart.adoc
 :description: Get started with AI Gateway. Configure providers, create your first gateway with failover and budget controls, and route your first request.
 :page-topic-type: quickstart
 :personas: evaluator, app_developer, platform_admin

@@ -2,8 +2,8 @@
 :description: AI Gateway is ADP's managed proxy for LLM APIs. Create a provider for OpenAI, Anthropic, Google AI, AWS Bedrock, or an OpenAI-compatible endpoint, and point your applications at a Redpanda-hosted URL with managed secrets, authentication, and observability.
 :page-topic-type: overview
 :personas: platform_admin, app_developer, evaluator
-// TODO: Add 'redpanda-cloud:ai-agents:ai-gateway/what-is-ai-gateway.adoc' to page-aliases after ai-agents is removed from cloud-docs
-:page-aliases: redpanda-cloud:ai-agents:ai-gateway/gateway-architecture.adoc, redpanda-cloud:ai-agents:ai-gateway/cel-routing-cookbook.adoc, redpanda-cloud:ai-agents:ai-gateway/mcp-aggregation-guide.adoc, redpanda-cloud:ai-agents:ai-gateway/builders/discover-gateways.adoc
+// TODO: Add 'cloud-data-platform:ai-agents:ai-gateway/what-is-ai-gateway.adoc' to page-aliases after ai-agents is removed from cloud-docs
+:page-aliases: cloud-data-platform:ai-agents:ai-gateway/gateway-architecture.adoc, cloud-data-platform:ai-agents:ai-gateway/cel-routing-cookbook.adoc, cloud-data-platform:ai-agents:ai-gateway/mcp-aggregation-guide.adoc, cloud-data-platform:ai-agents:ai-gateway/builders/discover-gateways.adoc
 :learning-objective-1: Describe what AI Gateway is and how a managed proxy differs from direct upstream calls
 :learning-objective-2: Explain how LLM providers, secrets, and OIDC authentication fit together in AI Gateway
 :learning-objective-3: Identify use cases where AI Gateway fits, and use cases where it does not

@@ -64,4 +64,4 @@ When `adp_enabled` is set, the source provisions ADP components in the cluster,
 == Next steps
 
 * xref:get-started:byoc-quickstart.adoc[Start the ADP BYOC quickstart]
-* xref:redpanda-cloud:get-started:cluster-types/byoc/aws/create-byoc-cluster-aws.adoc[Create a BYOC environment on AWS] in Redpanda Cloud docs
+* xref:cloud-data-platform:get-started:cluster-types/byoc/aws/create-byoc-cluster-aws.adoc[Create a BYOC environment on AWS] in Redpanda Cloud docs
@@ -22,7 +22,7 @@ Review xref:get-started:byoc-prereqs.adoc[ADP BYOC prerequisites].
 
 == Create or select a BYOC environment on AWS
 
-Use a Redpanda Cloud BYOC environment on AWS. For the general AWS BYOC environment creation flow, see xref:redpanda-cloud:get-started:cluster-types/byoc/aws/create-byoc-cluster-aws.adoc[Create a BYOC environment on AWS].
+Use a Redpanda Cloud BYOC environment on AWS. For the general AWS BYOC environment creation flow, see xref:cloud-data-platform:get-started:cluster-types/byoc/aws/create-byoc-cluster-aws.adoc[Create a BYOC environment on AWS].
 
 Before you configure ADP resources, confirm that ADP is enabled for the cluster. The provisioner switch is `adp_enabled`.
 

@@ -2,4 +2,4 @@
 :description: pass:q[Install or update `rpk` to interact with Redpanda from the command line.]
 :env-cloud:
 
-include::ROOT:get-started:rpk-install.adoc[tag=single-source]
+include::streaming:get-started:rpk-install.adoc[tag=single-source]
@@ -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 environment). 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 environment). 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,3 +1,3 @@
 = rpk cloud cluster select
 
-include::ROOT:reference:partial$rpk-cloud/rpk-cloud-cluster-select.adoc[tag=single-source]
+include::streaming:reference:partial$rpk-cloud/rpk-cloud-cluster-select.adoc[tag=single-source]
@@ -1,3 +1,3 @@
 = rpk cloud cluster
 
-include::ROOT:reference:partial$rpk-cloud/rpk-cloud-cluster.adoc[tag=single-source]
+include::streaming:reference:partial$rpk-cloud/rpk-cloud-cluster.adoc[tag=single-source]
@@ -1,3 +1,3 @@
 = rpk cloud login
 
-include::ROOT:reference:partial$rpk-cloud/rpk-cloud-login.adoc[tag=single-source]
+include::streaming:reference:partial$rpk-cloud/rpk-cloud-login.adoc[tag=single-source]
@@ -1,3 +1,3 @@
 = rpk cloud logout
 
-include::ROOT:reference:partial$rpk-cloud/rpk-cloud-logout.adoc[tag=single-source]
+include::streaming:reference:partial$rpk-cloud/rpk-cloud-logout.adoc[tag=single-source]
@@ -1,3 +1,3 @@
 = rpk cloud
 
-include::ROOT:reference:partial$rpk-cloud/rpk-cloud.adoc[tag=single-source]
+include::streaming:reference:partial$rpk-cloud/rpk-cloud.adoc[tag=single-source]
@@ -1,4 +1,4 @@
 = rpk profile
 :page-aliases: reference:rpk/rpk-profile.adoc
 
-include::ROOT:reference:rpk/rpk-profile/rpk-profile.adoc[tag=single-source]
+include::streaming:reference:rpk/rpk-profile/rpk-profile.adoc[tag=single-source]