Red Hat Developer Hub 1.8

Quickly gain access and find what you need in Red Hat Developer Hub

Log in, navigate the Red Hat Developer Hub (RHDH) interface, and personalize your workspace to become productive immediately.

Red Hat Customer Content Services

Abstract

As a new developer, you will learn how to personalize your experience by customizing settings and starring frequently used items, enabling you to independently find the software catalog, templates, and documentation you need.

As a new developer, you will learn how to personalize your experience by customizing settings and starring frequently used items, enabling you to independently find the software catalog, templates, and documentation you need.

1. Understand the purpose and structure of Red Hat Developer Hub

To streamline your software development lifecycle, use Red Hat Developer Hub (RHDH) as your primary internal developer portal (IDP).

You can access a unified interface to manage infrastructure, tools, services, and technical documentation in a centralized location.

The developer experience challenge
Modern software development often involves fragmented workflows. Developers frequently switch contexts between code repositories, ticketing systems, CI/CD pipelines, and monitoring dashboards. This fragmentation creates information silos and increases the time required to find API documentation, service ownership details, or deployment status.
The RHDH solution

RHDH addresses these challenges by consolidating resources into a single, searchable portal. This centralization offers the following advantages:

  • Unified discovery: Users can locate applications, APIs, and documentation in one location.
  • Self-service capabilities: Developers can create projects and deploy services using automated templates, reducing reliance on manual ticketing.
  • Service visibility: The platform maps relationships between services, dependencies, and API contracts.
  • Extensibility: Users can integrate external tools, such as monitoring dashboards and pipelines, directly into the interface.

1.1. Checklist for your first RHDH instance in production

To establish a productive workflow in a production RHDH instance as a developer, you must verify your access permissions, confirm ownership of software entities, and personalize your interface. With this process, you can locate team services and utilize self-service capabilities immediately.

Log in and verify your profile

Because production environments often use different authentication providers (such as corporate SSO) than test environments, your first step is to confirm you are logged in as the correct user and that the platform recognizes your identity.

  • Authenticate: Access your organization’s RHDH URL and log in using your corporate credentials.
  • Check your identity: Click your avatar or name in the Global Header and select Settings. Verify that the User Entity matches your corporate identity.
  • Verify Ownership: Navigate to My Profile from the user menu. Check the Ownership card to ensure it lists the components, APIs, and systems you or your team are responsible for. If this list is empty, you may need to register your ownership in the Software Catalog.

Organize your workspace

To reduce navigation time across the software ecosystem, curate a list of high-priority resources.

  • Star your services: Locate your frequently used components in the Catalog and select the Star icon to add them to your favorites.
  • Access starred items: Use the Starred Items menu in the Global Header to open your favorite resources quickly.
  • Pin the Sidebar: If you switch frequently between tools, go to Settings and enable Pin Sidebar to keep the navigation menu permanently visible. See Personalizing the navigation experience in RHDH.

Explore production resources

Production instances provide access to live infrastructure data and technical guides required for operational tasks.

  • See production documentation: Use the Docs menu to find production-specific documentation, such as runbooks or deployment guides linked to your components.
  • Check production APIs: Navigate to the APIs page to confirm that production endpoint definitions are accurate and discoverable.
  • Test Self-Service templates: Click Create (+) in the Global Header to examine available Software Templates. Confirm that you have access to the templates required to generate new production services.

Next steps

  • Start your day: Navigate to the RHDH Home Page to view your personalized dashboard.
  • Learn the interface: Understand the Global Header and Sidebar tools.
  • Get AI assistance: If enabled in production, open Developer Lightspeed for RHDH to ask questions about your new environment.

1.2. Optimize developer productivity with RHDH core features

To streamline your software development lifecycle, use the integrated toolset within Red Hat Developer Hub (RHDH). These core capabilities allow you to perform self-service tasks and discover organizational resources from a centralized interface.

Developer workflow capabilities

By using the following features, you can reduce context switching and automate repetitive setup tasks:

Software Catalog
Use this centralized inventory to manage software components, APIs, and systems. You can visualize ownership, track dependencies, and monitor the lifecycle status of assets across the organization.
Software Templates
Automate the creation of new projects by using self-service templates. These templates bootstrap repositories, configure CI/CD pipelines, and apply organizational best practices to eliminate manual configuration.
TechDocs
Access "docs-as-code" documentation that renders directly within the portal. This ensures that technical guides remain synchronized with the codebase and are easily discoverable alongside their corresponding services.
Plugins
Extend the portal’s functionality by connecting it to your existing toolchain. You can monitor ArgoCD deployments, view Jira tickets, or review Quay registry scans without navigating away from the portal interface.
Global Search
Find specific components, documentation, or team members instantly by using a unified search engine that indexes the entire software ecosystem.

1.3. Distinguish RHDH from Backstage

While RHDH is built on the open-source Backstage project, it offers distinct advantages for enterprise environments. RHDH is a production-ready, supported distribution that removes the maintenance burden associated with the upstream project.

Operational comparison

Use the following comparison to determine which platform aligns with your team’s maintenance capacity and security requirements.

FeatureBackstageRHDH

Maintenance Model

Requires manual codebase maintenance and frequent manual upgrades.

Uses a zero-code model where Red Hat manages the base image and updates.

Support

Community-based support through forums and documentation.

Provides 24x7 enterprise-level support.

Plugin Architecture

Requires recompilation of the entire application to add or update plugins.

Uses a dynamic plugin architecture to allow updates without recompilation.

Security

Requires self-managed security patching and custom RBAC implementation.

Includes built-in Role-Based Access Control (RBAC) and rapid CVE resolution.

Deployment

Uses a standard Helm-based installer.

Uses a Kubernetes Operator-based installer for OpenShift and major cloud providers.

Choosing a platform for your organization

  • Choose Backstage if: Your organization has a dedicated platform engineering team to manage source code, implement security patches, and build custom integrations.
  • Choose RHDH if: You need a production-ready portal that prioritizes security and stability while allowing your team to focus on development tasks rather than platform maintenance.

Additional resources

2. Log in to Red Hat Developer Hub

To access your organization’s software catalog, templates, and documentation, you must authenticate with Red Hat Developer Hub (RHDH) using your configured identity provider. With secure authentication, you have the appropriate permissions to view and manage software entities linked to your role.

By logging in, you gain entry to a centralized portal that streamlines your development workflow. This secure access allows you to locate required software building blocks and documentation without navigating multiple disparate systems.

2.1. Logging in to RHDH

To access your organization’s software ecosystem, tools, and self-service templates, log in to the Red Hat Developer Hub (RHDH) web console. With a successful login, you can access resources permitted by your role-based access control (RBAC) settings.

Procedure

  1. Navigate to the RHDH URL provided by your administrator.
  2. On the login page, select the appropriate authentication method for your project:

    • Enterprise Authentication: Select this option to log in with your corporate credentials, such as Single Sign-On or Keycloak.
    • OAuth Provider: Select an external provider, such as GitHub or GitLab, if your organization manages developer identities through those services.
    • Guest Access: If available, select Enter as Guest for read-only exploration.

      Note

      Guest access typically has limited permissions and does not allow you to create or register new components.

  3. Enter your credentials and complete the required authentication prompts.

Verification

  • The portal redirects you to the Home page.
  • Your personalized dashboard appears, displaying your username and recently accessed items.

2.2. Select authentication methods for secure access

To access the specific tools, repositories, and permissions assigned to your role, you must authenticate to Red Hat Developer Hub (RHDH) using a supported provider. Selecting the correct authentication method ensures that the portal correctly associates your identity with your team’s software components and self-service capabilities.

Common authentication methods:

Corporate Single Sign-On (SSO)
Select this option to use your standard organizational credentials. This method typically provides full access to internal resources and links your portal identity to your official team membership.
Federated authentication
Use services such as Keycloak or Ping Federate to unify your login across multiple enterprise applications. This ensures that your permissions remain consistent as you navigate between the portal and external development tools.
OAuth providers
Select providers such as GitHub, GitLab, or Azure DevOps to link your developer identity directly to the portal. This is required if you need to perform actions in the Software Catalog that involve external version control systems.
Guest access

Use this restricted, read-only mode for initial platform exploration.

Important

Guest access is intended for demonstration purposes. While in this mode, you cannot register components, use Software Templates, or access restricted organizational data.

2.3. Navigate the RHDH interface

To locate resources, manage projects, and customize your workspace, use the two primary navigation areas in Red Hat Developer Hub (RHDH). By understanding these regions, you can navigate the software ecosystem and execute development tasks efficiently.

Using the Global Header

The top bar provides immediate access to high-frequency actions and personal settings.

  • Search: Use the input field to find components, APIs, documentation, and users across the entire ecosystem instantly.
  • Self-service (+): Select the plus icon to access templates for creating new software components or projects.
  • User profile: Click your avatar to adjust interface settings, set appearance preferences (such as Dark Mode), or log out.
  • Support and notifications: Access system alerts and platform help resources.

Using the left navigation sidebar

The sidebar organizes core platform features into distinct functional sections.

  • Home: Navigate to your personalized dashboard to view recently accessed items and team updates.
  • Catalog: Browse the inventory of software components, services, and resources to visualize ownership and dependencies.
  • Docs: Access the technical documentation library (TechDocs) to read guides linked to specific software entities.
  • APIs: Explore and test available API definitions in the centralized browser.
  • Create: Open the template gallery to scaffold new projects using organizational "golden paths".

3. Find software components using the Software Catalog

To integrate with existing software, verify ownership, or prevent redundant development, use the Software Catalog in Red Hat Developer Hub (RHDH). This centralized inventory of your organization’s software ecosystem helps you discover assets without searching through disparate documentation or repositories.

By using the Software Catalog, you can achieve the following outcomes:

  • Reuse existing code: Locate shared libraries and components to prevent duplication of effort.
  • Understand dependencies: Visualize connections between services and API contracts.
  • Identify ownership: Find the specific team or individual responsible for an asset to facilitate collaboration.

3.1. Finding components in RHDH

To identify existing software building blocks, view source code, or check lifecycle status, use the catalog filters in Red Hat Developer Hub (RHDH). Filtering the catalog ensures you can locate production-ready components and documentation without performing manual searches across multiple repositories.

Procedure

  1. Navigate to the RHDH interface.
  2. In the left navigation sidebar, click Catalog.
  3. Click the Kind filter and select Component.
  4. Optional: Click the Type filter to narrow the list to a specific functional category, such as Library, Website, or Tool.
  5. Enter the component name in the Search bar at the top of the Catalog page.
  6. Select the component card from the results to view its Overview, Docs, and Relationships.

3.2. Analyzing microservice dependencies and status in RHDH

To identify backend applications and microservices, view their deployment status, and understand their API relationships, use the filters in the Red Hat Developer Hub (RHDH) Software Catalog. Filtering for services ensures you can verify architectural connections and ownership without manually tracing code across disparate repositories.

Procedure

  1. Navigate to the RHDH interface.
  2. In the left navigation sidebar, click Catalog.
  3. Click the Kind filter and select Component.
  4. Click the Type filter and select Service.
  5. Optional: Narrow the list by selecting a specific Owner or Lifecycle, such as production or experimental.
  6. Select a service card to open the detailed entity view.
  7. Review the Overview tab to identify the assigned owner and access links to the source code repository.
  8. Select the Dependencies or Relations tab to see upstream and downstream connections for that service.

3.3. Finding API definitions for integration testing in RHDH

To verify endpoints, schemas, and server URLs for your services, locate and inspect API contracts in Red Hat Developer Hub (RHDH). Reviewing these definitions allows you to validate required parameters and data models in a rendered format without manually searching through source code repositories.

Procedure

  1. Navigate to the RHDH interface.
  2. In the left navigation sidebar, click APIs.

    Note

    You can also find these resources by clicking Catalog and selecting API from the Kind filter.

  3. Select an API from the list to open the detail view.
  4. Select the Overview tab to examine the metadata, assigned owner, and lifecycle status.
  5. Select the Definition tab to view the rendered specification, such as an interactive Swagger or AsyncAPI interface.

4. Importing and using an existing Software Template for faster development

To standardize and accelerate the creation of new software, use Software Templates in Red Hat Developer Hub (RHDH). You can generate consistent software components, publish them to Git repositories, and register them in the Software Catalog to make sure they are discoverable across your organization.

Each template uses a YAML definition to present a functional interface for inputting project metadata. Software Templates run a sequential series of actions, such as scaffolding code or creating repositories, which you can configure to run conditionally based on user input.

4.1. Creating a Software Template by using the Template Editor

Use the Red Hat Developer Hub Template Editor to create a Software Template.

Alternately, you can use the Template Editor to do any of the following actions:

  • File > Open template directory
  • File > Create template directory
  • File > Close template editor
  • Use the Custom Fields Explorer button to test custom fields in your templates.yaml file
  • View Installed Actions Documentation

Procedure

  1. In your Red Hat Developer Hub navigation menu, click Catalog > Self-service. Alternatively, to go to Self-service page, in your header menu, click the (+) icon.
  2. Click the More options icon and select Manage Templates.

    Template Editor
    Note
    • The following options on the Managed Templates page do not create a software component in your Red Hat Developer Hub instance:

      • Template Form Playground: Use to create and test the templates.yaml file
      • Custom Field Explorer: Use to test custom fields
  3. On the Managed Templates page, select any of the following options:

    • Load Template Directory: Use to load an existing templates.yaml file

      • In your local file manager, navigate to the folder where your templates.yaml file is stored and click Select.
    • Create New Template: Use to create a templates.yaml file

      1. In your local file manager, navigate to the folder where you want the Template Editor to create a templates.yaml file and click Select.
      2. On the Template Editor page, select the templates.yaml file.
      3. (Optional) You can preview and test your template specifications.

        1. On the Fill in some steps tab, enter text into the required fields and click Next.
        2. On the Repository Location tab, enter text into the required fields and click Review.
        3. Modify the YAML definition for the parameters of your template. For more information about these parameters, see Section 4.2, “Creating a Software Template as a YAML file”.
        4. Review the information for accuracy, then click Create.
      4. After the Software Template is created, import your Software Template in your RHDH instance.

Verification

  1. Click the Catalog tab in the navigation panel.
  2. In the Kind drop-down menu, select Template.
  3. Confirm that your template is shown in the list of existing templates.

4.2. Creating a Software Template as a YAML file

You can create a Software Template by defining a Template object as a YAML file.

The Template object describes the Software Template and its metadata. It also contains required input variables and a list of actions that are executed by the scaffolding service.

Template object example

apiVersion: scaffolder.backstage.io/v1beta3
kind: Template
metadata:
  name: template-name 1
  title: Example template 2
  description: An example template for v1beta3 scaffolder. 3
spec:
  owner: backstage/techdocs-core 4
  type: service 5
  parameters: 6
    - title: Fill in some steps
      required:
        - name
      properties:
        name:
          title: Name
          type: string
          description: Unique name of the component
        owner:
          title: Owner
          type: string
          description: Owner of the component
    - title: Choose a location
      required:
        - repoUrl
      properties:
        repoUrl:
          title: Repository Location
          type: string
  steps: 7
    - id: fetch-base
      name: Fetch Base
      action: fetch:template
      # ...
  output: 8
    links:
      - title: Repository 9
        url: ${{ steps['publish'].output.remoteUrl }}
      - title: Open in catalog 10
        icon: catalog
        entityRef: ${{ steps['register'].output.entityRef }}
# ...

1
Specify a name for the Software Template.
2
Specify a title for the Software Template. This is the title that is visible on the Software Template tile in the Self-service view.
3
Specify a description for the Software Template. This is the description that is visible on the Software Template tile in the Self-service view.
4
Specify the ownership of the Software Template. The owner field provides information about who is responsible for maintaining or overseeing the Software Template within the system or organization. In the provided example, the owner field is set to backstage/techdocs-core. This means that this Software Template belongs to the techdocs-core project in the backstage namespace.
5
Specify the component type. Any string value is accepted for this required field, but your organization should establish a proper taxonomy for these. Red Hat Developer Hub instances may read this field and behave differently depending on its value. For example, a website type component may present tooling in the Red Hat Developer Hub interface that is specific to just websites.

The following values are common for this field:

service
A backend service, typically exposing an API.
website
A website.
library
A software library, such as an npm module or a Java library.
6
Use the parameters section to specify parameters for user input that are shown in a form view when a user creates a component by using the Software Template in the Red Hat Developer Hub console. Each parameters subsection, defined by a title and properties, creates a new form page with that definition.
7
Use the steps section to specify steps that are executed in the backend. These steps must be defined by using a unique step ID, a name, and an action. You can view actions that are available on your Red Hat Developer Hub instance by visiting the URL https://<rhdh_url>/create/actions.
8
Use the output section to specify the structure of output data that is created when the template is used. The output section, particularly the links subsection, provides valuable references and URLs that users can utilize to access and interact with components that are created from the template.
9
Provides a reference or URL to the repository associated with the generated component.
10
Provides a reference or URL that allows users to open the generated component in a catalog or directory where various components are listed.

4.3. Creating a software component using Software Templates

You can create a software component using standard Software Templates. The scaffolding process runs in your Red Hat Developer Hub instance.

Prerequisites

  • You are logged in to the Red Hat Developer Hub instance.

Procedure

  1. In your Red Hat Developer Hub navigation menu, click Catalog > Self-service.
  2. On the Self-service page, click Choose on the Templates tile to initiate the scaffolding process for a template.
  3. Follow the wizard instructions, entering the required details, and selecting from pre-defined options.
  4. Optional: In the Deployment Information step, you have an option to Create Workbench for OpenShift AI.

    Note

    This option is only available for certain templates.

  5. In the Review step, verify the parameters you have entered and click Create.

    The scaffolding process begins. You can view the logs during the process or click Cancel to abort the operation.

Verification

  • If your software component is created successfully, a success page similar to the example in the following image appears:

    template-creation-successful

Troubleshooting

  • If the component creation fails, review the logs on the error page. Click Start Over to return to the Self-service page while retaining your entered values.

    template-creation-not-successful

4.4. Searching and filtering Software Templates in your Red Hat Developer Hub instance

You can search and filter for the Software Template to create a software component.

Procedure

  1. In the Red Hat Developer Hub navigation menu, click Catalog > Self-service.
  2. In the Search box, enter the name of the Software Template.
  3. Optional: To filter results, select a category from the Categories dropdown list.

4.5. Importing an existing Software Template to Red Hat Developer Hub

You can use the Catalog Processor to import an existing Software Template into your Red Hat Developer Hub instance.

Prerequisites

  • You have created a directory or repository that contains at least one template YAML file.
  • Optional: To use a template stored in GitHub, you have configured Developer Hub integration with GitHub.

Procedure

  1. Open your RHDH app-config.yaml configuration file.
  2. In the catalog.rules section, add a rule to allow Templates kinds, as shown in the following example:

    # ...
    catalog:
      rules:
        - allow: [Template]
      locations:
        - type: url
          target: https://<repository_url/template-name>.yaml
    # ...

    where:

    catalog.rules.allow
    Specify the Template rule to allow new Software Templates in the catalog.
    catalog.locations.type
    Specify the url type when importing templates from a repository (for example, GitHub or GitLab).
    catalog.locations.target
    Specify the full URL to the template file.

Verification

  1. In the Red Hat Developer Hub navigation menu, click Catalog.
  2. From the Kind list, select Template.
  3. Verify that your template appears in the Template list.

5. Finding and viewing Technical Documentation (TechDocs)

To manage and consume software documentation efficiently, locate and view TechDocs directly in the Red Hat Developer Hub (RHDH) portal. You can review architecture diagrams, installation guides, and component details alongside corresponding software entities in a single interface

By centralizing documentation, you ensure that technical resources are always accessible within the context of the services you develop. This direct access eliminates the need to navigate disparate repositories when verifying software requirements or implementation details.

5.1. Searching for relevant content in TechDocs

To view technical content, locate specific documents in TechDocs by using the search bar or filters.

The TechDocs Documentation page displays all documentation imported into your Red Hat Developer Hub instance. You can locate documentation by using keywords or filters:

  • Search: Enter a keyword in the search bar to find documents containing that term.
  • Filter by Owner: View documents owned by a specific user or group.
  • Filter by Tags: View documents containing a specific tag.
  • Filter by Owned: View documents owned by you or a group to which you belong.
  • Filter by Starred: View documents you added to favorites.

The All field displays the total number of documents that have been imported into TechDocs. If you search or filter, this field updates to show the number of of documents that meet the search and filter criteria that you applied.

Prerequisites

  • The TechDocs plugin is enabled and configured.
  • Documentation is imported into TechDocs.
  • You have the required roles and permissions to add and view documentation to TechDocs.

Procedure

  1. In the Red Hat Developer Hub navigation menu, click Docs.
  2. On the Documentation page, use the search bar, filters, or both to locate the document that you want to view.

5.2. Accessing and reading documentation in TechDocs

In TechDocs, a document might be part of a book that contains other documents that are related to the same topic.

Clicking the name of a document in the table on the Documentation page opens the document in a book page. The name of the book is displayed on the book page.

You can use the elements on the book page to search, view, and navigate the documentation in the book.

Prerequisites

  • The TechDocs plugin is enabled and configured.
  • Documentation is imported into TechDocs.
  • You have the required roles and permissions to add and view documentation to TechDocs.
  • Optional: TechDocs add-ons are installed and configured.

Procedure

  1. In the Red Hat Developer Hub navigation menu, click Docs.
  2. In the Documentation table, click the name of the document that you want to view.
  3. On the book page, navigate the document using the following tools:

    • Search bar: Find keywords within the document.
    • Table of contents: Skip to specific sections of the current document.
    • Navigation menu: Open other documents in the book.
    • Next: Go to the next sequential document in the book.
    • Add-ons: Use installed add-ons to perform additional actions.

6. Discover and test available APIs

To integrate with existing services and understand component communication, use the Red Hat Developer Hub (RHDH) API browser to locate, inspect, and validate API definitions in a centralized interface. You can review API contracts and test endpoints to verify responses directly from the portal.

Apart from viewing specifications, you can use the interactive interface to test available endpoints and review data models. This ensures your application correctly interfaces with backend services before you begin integration.

6.1. Finding components in RHDH

To find existing software building blocks, view source code, or check lifecycle status, use the catalog filters in Red Hat Developer Hub (RHDH). Filtering the catalog ensures you can locate production-ready components and documentation without performing manual searches across multiple repositories.

Procedure

  1. Navigate to the RHDH interface.
  2. In the left navigation sidebar, click Catalog.
  3. Click the Kind filter and select Component.
  4. Optional: Click the Type filter to narrow the list to a specific functional category, such as Library, Website, or Tool.
  5. Enter the component name in the Search bar at the top of the Catalog page.
  6. Select the component card from the results to examine its Overview, Docs, and Relationships.

6.2. Verifying service integration using interactive API testing

To verify API behavior and debug service responses, use the interactive test interface in Red Hat Developer Hub (RHDH). Validating endpoints directly within the portal ensures they return the expected status codes and data models, which eliminates the need to configure external testing tools during the initial integration phase.

Prerequisites

  • You have the required credentials or tokens if the API requires authentication.

Procedure

  1. Navigate to the specific API you must validate and select the Definition tab.
  2. Locate the operation you want to verify and select the header to expand the details.
  3. Click Try it out to enable the interactive input fields.
  4. Enter the required parameters or the request body JSON in the provided fields.
  5. Click Execute.
  6. Examine the Server response section to verify the status code, response body, and headers.

If you receive 401 (Unauthorized) or 403 (Forbidden) errors, you must verify your credentials with the API owner or check the authorization header requirements in the specification.

6.3. Select supported API specifications in RHDH

To ensure your API definitions are discoverable and interactive within the Red Hat Developer Hub (RHDH) portal, you must use a supported specification format. Selecting the appropriate format based on your service architecture allows the platform to render documentation and provide testing interfaces for other developers.

Supported API formats

  • OpenAPI: Use this standard format (formerly Swagger) for defining RESTful APIs. RHDH renders these specifications into interactive documentation, allowing users to execute requests directly from the Definition tab.
  • AsyncAPI: Use this format for event-driven architectures and message-based services. This ensures that producers and consumers can visualize message schemas and broker details within the Software Catalog.
  • GraphQL: Use this format to define GraphQL schemas. This allows developers to explore your data graph, including queries, mutations, and types, from a centralized location.
Note

Support for specific formats, such as AsyncAPI or GraphQL, depends on your organization’s instance configuration and enabled plugins. If a specification does not render, verify your catalog-info.yaml metadata or contact your platform administrator.

Additional resources

8. Get AI-assisted help in RHDH

To assist with development tasks, platform questions, and debugging, use Red Hat Developer Lightspeed for Red Hat Developer Hub, a generative AI virtual assistant integrated directly into Red Hat Developer Hub (RHDH). You can use the conversational interface to ask platform-specific questions, analyze logs, generate code, and create test plans, which reduces the time spent searching through official documentation or disparate tools.

Capabilities

The scope of questions you can ask depends on your configuration:

  • Question Validation enabled (default): Supports general questions about Red Hat Developer Hub. For example:

    • “Tell me about Red Hat Developer Hub.”
    • “What are the benefits of RHDH?”
    • “Can I use RHDH on an OpenShift Container Platform?”
    • “How do I install plugins on Red Hat Developer Hub?”
  • Question Validation disabled: Supports broader tasks such as log analysis, code generation, and creating Kubernetes deployments. For example:

    • “Analyze this log for me…”
    • “Suggest libraries and frameworks I can use to build Event Driven Architecture microservices.”
    • “I’m not familiar with this language, so explain to me what this code snippet is doing…”
    • “Create a Kubernetes deployment for this service…”
    • “Create a test plan for the following scenarios and conditions…”
    • “Create a Jira record that describes the following feature…”
    • “Draft the end-user documentation describing how to use the following cli command…”
Note

The Question Validation feature is enabled by default if you are using the quay.io/redhat-ai-dev/llama-stack image without overriding the run.yaml configuration file in the image. To disable Question Validation, you must mount a run.yaml file to the container with the following sections removed:

  • Safety
  • Shields
  • External_providers_dir set to null

Prerequisites

  • You have the Developer Lightspeed for RHDH plugin configured in your RHDH instance.

8.1. Starting a chat with Developer Lightspeed for RHDH for the first time

You can start a chat with Developer Lightspeed for RHDH for quick answers on a number of topics depending on your settings. You can manually start a chat with the Developer Lightspeed for RHDH or use the following sample prompts we have provided to help you get started:

  • Getting Started with Red Hat Developer Hub
  • Deploy with Tekton
  • Create an OpenShift Deployment

Procedure

  1. In the RHDH navigation menu, click Lightspeed.
  2. Start a chat using one of the following methods:

    • Manual entry: Type your query in the Send a message field and press Enter.
    • Sample prompts: Click a prompt tile, such as Deploy with Tekton, to start a predefined task.
    • File attachment: Click the Attach icon to upload a file (.yaml, .json, or .txt) for analysis.

Verification

  • The chat window updates to display your query and the response from Developer Lightspeed for RHDH.

8.2. Starting a chat in Developer Lightspeed for RHDH after the first chat

After you have started a chat with the Developer Lightspeed for RHDH for the first time, you can reset the chat context for a new topic. Even if you log out and log back in, your previous chats are automatically saved in your history.

Procedure

  1. In your RHDH navigation menu, click Lightspeed.
  2. In the Developer Lightspeed for RHDH virtual assistant interface, click New chat.

8.3. Viewing chat history in Developer Lightspeed for RHDH

Your chats with Developer Lightspeed for RHDH are automatically saved in your RHDH instance. You can easily revisit your chat history at any time, switch between chats, or resume a previous chat.

Procedure

  1. In the RHDH navigation menu, click Lightspeed. Developer Lightspeed for RHDH opens with your previous chat.
  2. Select a chat title from the history list to view the full conversation.
  3. Optional: Use the Search previous chats…​ field to filter the history list by keyword.

Verification

  • The selected conversation loads in the main window, allowing you to view the history or continue the chat.

8.4. Deleting a chat in Developer Lightspeed for RHDH

You can remove specific chats from your chat history in Developer Lightspeed for RHDH.

Prerequisites

  • You have the Developer Lightspeed for RHDH plugin configured in your RHDH instance.

Procedure

  1. In your RHDH navigation menu, click Lightspeed. Developer Lightspeed for RHDH opens with your previous chat.
  2. In Developer Lightspeed for RHDH, click the vertical ellipsis (⋮) next to the chat title you want to remove.
  3. Select Delete.

Verification

  • The chat title is removed from the history list.

8.5. Get the best results for assistant queries

To resolve technical blockers and accelerate development tasks, you must structure your queries to provide specific context to the AI assistant. Using precise prompts ensures that Developer Lightspeed for RHDH generates relevant code snippets, architectural advice, or platform-specific instructions.

Use the following strategies to improve the accuracy of the assistant’s output during your development workflow:

Specify technologies
Instead of asking "How do I use templates?", ask "How do I create a Software Template that scaffolds a Node.js service with a CI/CD pipeline".
Provide context
Include details about your environment, such as "I am deploying to OpenShift; how do I configure my catalog-info.yaml to show pod health?".
Leverage conversation context
Ask follow-up questions to refine a previous answer. For example, if the assistant provides a code snippet, you can ask "Now rewrite that using TypeScript interfaces."
Validate with citations
Examine the provided documentation links and citations in the response to verify that the generated advice aligns with your organization’s official standards.
Improve assistant accuracy
Rate the utility of responses by selecting the Thumbs up or Thumbs down icons. This feedback helps tune the model for your organization’s specific requirements.
Important

To maintain security standards, do not include sensitive personal information, plain-text credentials, or confidential business data in your queries.

9. Viewing available extensions and plugins in RHDH

To integrate your daily tools and customize your development experience, explore the extensions and plugins available in Red Hat Developer Hub (RHDH). By discovering global features in the navigation sidebar or reviewing entity-specific data in the catalog, you can extend portal capabilities to include information from external services such as Jira, Jenkins, or ArgoCD.

9.1. Understand extensions and plugins

To integrate your development toolchain into a single interface, use extensions and plugins in Red Hat Developer Hub (RHDH). While core features such as the Software Catalog and TechDocs are pre-installed, you can utilize additional plugins to interact with external services directly from the portal.

9.2. Accessing platform-wide tools in RHDH using global plugins

To manage technology standards, track project costs, or access AI assistance, use the global plugins located in the main navigation sidebar of Red Hat Developer Hub (RHDH). These plugins provide features that apply across the entire portal rather than to a specific software entity.

Procedure

  1. Log in to your RHDH instance.
  2. In the left navigation sidebar, locate the standard or custom items that represent specific global extensions, such as:

    • Tech Radar: Use this to visualize your organization’s approved and deprecated technologies.
    • Cost Insights: Use this to track and analyze cloud infrastructure spending for your projects.
    • Developer Lightspeed: Access this conversational interface for AI-assisted development help and platform queries.
    • Learning Paths: Access training and educational resources to improve your technical skills.

9.3. Viewing entity plugins in RHDH

To review data specific to a particular resource in RHDH, use entity plugins that appear when viewing components, services, or APIs in the Software Catalog.

Procedure

  1. Navigate to the RHDH interface.
  2. In the left navigation sidebar, click Catalog.
  3. Select a Component or Service card.
  4. Review the tabs at the top of the entity page to view configured plugins:

    • CI/CD: Displays build status and history from tools such as Jenkins or GitHub Actions.
    • Kubernetes: Shows deployment status and pod health.
    • Topology: Visualizes the relationships and status of running resources.

Next steps

  • If a build failed in the CI/CD tab, select the build number to view the logs in the source provider.
  • If a pod is failing in the Kubernetes tab, examine the error events to troubleshoot the deployment.

9.4. Identifying integrations in the RHDH extensions marketplace

To enhance your development workflow with additional tools, browse the extensions marketplace in Red Hat Developer Hub (RHDH). Identifying available plugins allows you to see which integrations are currently active or which supported tools your team can request to improve project visibility and automation.

Procedure

  1. In the left navigation sidebar, click Extensions.
  2. Browse the marketplace to review the following categories:

    • Installed: Review the integrations currently active in your instance, such as Jira, ArgoCD, or GitHub.
    • Available: Examine additional integrations supported by the platform that are not yet enabled for your workspace.
Note

End users typically cannot install plugins. If you locate a plugin in the marketplace or the Backstage Plugin Directory that your team requires, contact your administrator to request its enablement.

Additional resources

  • Introduction to plugins[Introduction to plugins]

10. Customize your RHDH interface settings

To suit your working environment and verify your account details, adjust the interface settings and review your user profile in Red Hat Developer Hub (RHDH).

10.1. Customizing your workspace interface in RHDH

To optimize your working environment for productivity and visual comfort, adjust the interface settings in Red Hat Developer Hub (RHDH). Personalizing these settings ensures that the portal aligns with your system preferences and navigation habits.

Procedure

  1. In the Global Header, click your avatar or name to open the user menu.
  2. Select Settings.
  3. In the Appearance section, configure the following options:

    • Theme: Select Light, Dark, or Auto to synchronize the portal with your operating system preferences.
    • Language: Select your preferred interface language from the list.
    • Pin Sidebar: Enable this toggle to keep the left navigation menu permanently expanded, or disable it to maximize your primary workspace area.

10.2. Verifying identity and ownership in RHDH

To confirm your access permissions and review software components assigned to your account, examine your user profile in Red Hat Developer Hub (RHDH). Verifying ownership ensures that you are correctly associated with your team’s services and that you have the necessary authority to manage those assets within the Software Catalog.

Procedure

  1. In the Global Header, click your avatar or name to open the user menu.
  2. Select My Profile.
  3. Review the About card to verify that your account details, such as email and team tags, are accurate.
  4. Examine the Ownership card to identify the software components, APIs, and systems currently linked to your identity.
  5. Use the relations toggle to switch between the following views:

    • Direct Relations: View only the entities where you are explicitly listed as the owner.
    • Aggregated Relations: View all entities inherited through your team memberships or group hierarchies.

11. Managing starred items in RHDH for quick access

To streamline your daily workflow and reduce navigation time, use the starring feature in Red Hat Developer Hub (RHDH). By starring key components, APIs, and services in the Software Catalog, you create a personalized list of high-priority resources accessible directly from your sidebar or homepage.

This personalization ensures that you can locate the specific tools and documentation you use most frequently without performing repetitive searches across the software ecosystem.

11.1. Starring key components in the Software Catalog

You can add frequently used components to the Your Starred Entities card for quick access.

Procedure

  1. In the Red Hat Developer Hub navigation menu, select Catalog.
  2. Locate the components you want to add as a favorite.
  3. In the Actions column for that component, click the Add to favorites (star) icon.

Verification

  • Navigate to the Home page and verify the component is listed in the Your Starred Entities card.

Legal Notice

Copyright © 2025 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.