Red Hat · Software · YoctoIT tech page

Developer Hub

The developer portal (Backstage): golden paths, service catalog and self-service for development teams.

FOCUS · PLATFORM ENGINEERINGThe 'how we do it here' in a portal: onboarding in hours, not weeks
Request the Free Assessment Learn more
YoctoIT material for clients and partners · Red Hat, RHEL, OpenShift, Ansible and the other products mentioned are trademarks of Red Hat, Inc. o di sue affiliate.
01 · What it is

Red Hat Developer Hub, made clear.

Developer Hub is Red Hat's enterprise Backstage: the catalog of all services with owners and documentation, golden path templates creating a new service already compliant (repo, pipeline, deploy), and plugins bringing CI, clusters and tickets into a single view. The platform stops being tribal.

Catalogo
every service on record: owner, docs, dependencies, status
Golden path
the template that generates the service already done right: you start compliant
Self-service
environments and deploys on demand within guardrails: fewer tickets, more flow
Red Hat Developer Hub
OFFICIAL RED HAT BRANDING · DEVELOPER HUB
INTERFACCIA REALE · BACKSTAGE (BASE DI DEVELOPER HUB) · FONTE: BACKSTAGE.IO
REAL INTERFACE · BACKSTAGE (THE BASE OF DEVELOPER HUB) · SOURCE: BACKSTAGE.IO
02 · How to use it well

The things that make the difference.

The portal

Developersa single front door
Catalogo
Templates
CI/CD plugins
what exists · how it's created · how it's doing
Developer Hub (Backstage)RBAC, docs-as-code
OpenShift & toolchainthe underlying platform
The platform with a human interface

A catalog actually populated

An empty portal dies in a month: automatic discovery and verified ownership are the real work.

Templates that are worth it

Golden paths encode our baselines: security, observability and CI already inside the new service.

TechDocs

Documentation in the repo, rendered in the portal: it lives with the code, not on a dead wiki.

DevEx metrics

Lead time and onboarding measured: the portal must save time, and prove it.

03 · In depth

Enterprise Backstage: catalog and templates

Developer Hub is the supported build of Backstage: the software catalog records services/APIs/resources from YAML in the repo (catalog-info) with automatic Git discovery; Golden Path templates (scaffolder) create the new service already with repo, pipeline and deploy; TechDocs publishes documentation from the code; dynamic plugins (no rebuild!) integrate ArgoCD, Tekton, clusters and tickets. RBAC and SSO close the governance loop.

  • catalog-info.yaml — the service's record in the repo: owner, APIs, dependencies
  • Scaffolder — the template generating compliant repo+CI+deploy in minutes
  • TechDocs — MkDocs from the repo: docs that live with the code
  • Plugin dinamici — integrations installable at runtime: no Backstage forks
  • RBAC — who sees and who creates: the multi-team portal governed
  • Discovery Git — GitHub/GitLab orgs scanned: the catalog populates itself
04 · Numbers and lifecycle

The numbers that matter.

70%
the typical onboarding speed-up with golden paths
3/anno
the supported RHDH releases
0
rebuilds for dynamic plugins
1
front door for the developers: the rest behind it
The developer portal pays off if it's cared for: a populated catalog, templates with OUR baselines and measured adoption.
05 · Use cases

Where it really pays off.

Growing teams

Developer onboarding from weeks to hours.

Many microservices

Who owns what, finally written down.

Standardization

The 'this is how it's done' applied by templates, not by reminders.

Developer experience is infrastructure: we build it with Developer Hub on top of your OpenShift.