One tab for developers
Catalog, architecture, observability, deployments, and operational workflows stay in one connected interface.
Explore
Backstage-Powered Developer Portal
Backstage gives developers one tab instead of 100. OpenChoreo gives platform engineers one platform instead of 100 tools. Together, they turn an informational portal into an actionable developer platform.
One platform for engineers
OpenChoreo turns golden paths, policy, orchestration, and runtime control into a coherent internal platform.
One model behind both
The same abstractions drive the portal view, the control plane, and the Kubernetes resources underneath.
01
Control Plane
A Platform Behind the Portal
The portal isn't just displaying information; there's a platform behind it. A control plane compiles developer intent into Kubernetes resources, enforces policies during compilation, continuously reconciles drift, and aggregates runtime state back to the portal. Intent flows down, reality flows up.
02
Catalog
Projects, Components, and More in the Catalog
Projects, components, endpoints, resources, and dependencies aren't just static catalog entries. They carry runtime semantics: a project becomes an isolation boundary, an endpoint gets visibility-driven network policies, and a dependency becomes enforced traffic flow. What's in the catalog is what's running in the cluster.
03
Architecture
Visualize Your Application Architecture
Your components, endpoints, and dependencies are rendered as a live graph that reflects actual permitted traffic flow, not just intended relationships. Developers declare the architecture. The platform enforces it. The portal shows it.
04
Observability
Built-In Observability
Logs, metrics, and traces feed back through the same abstractions developers already understand. The control plane compiled those abstractions to Kubernetes, so it can map runtime data back to the right component in the right environment without another context switch.
05
Platform AI Agents
AI-Powered Root Cause Analysis
The built-in SRE Agent analyzes logs, metrics, and traces and uses LLMs to surface likely root causes. It works because it has access to the control plane's unified view, where abstractions, runtime state, and observability data are already connected.
06
Shift-Down Self-Service
Developer Self-Service Actions
Scaffold new components, trigger builds, and promote across environments from the portal. Golden paths aren't just templates that run once during scaffolding; they're enforced continuously by the control plane.
07
Developer Workflows
Build from the Portal
Trigger builds and track their progress from the same interface where you manage your components. The workflow plane handles execution with Cloud Native Buildpacks and Argo Workflows. The portal is where developers interact.
08
Environments and Promotion
Build, Deploy, and Promote
Deploy to any environment and promote across stages such as development, staging, and production from the portal. The control plane compiles your abstractions for each environment and reconciles the target state. Developers see what's deployed where without touching kubectl.
09
Authorization
Role-Based Access Control
Define who can see, deploy, and manage what with scoped RBAC that works across the portal, the control plane, and your workload clusters. Permissions follow your namespace structure.
10
Ownership and Multi-Tenancy
Namespaces for Ownership and Isolation
Namespaces provide a logical grouping of users and resources aligned to your organizational structure. They define ownership and access boundaries without exposing the underlying cluster topology.
11
Platform View
Platform at a Glance
Namespaces, data planes, environments, component types, and traits are laid out in one view. This is the vocabulary you define as a platform engineer, and the portal makes it visible to everyone.
12
GitOps
YAML When You Want It
Every portal action has a declarative equivalent. The portal and YAML aren't competing interfaces; they're two views of the same abstractions, which keeps the experience GitOps-friendly by design.
13
Kubernetes Abstractions
Peek Under the Hood
Kubernetes isn't hidden. Inspect pods, events, and resource states directly from the portal. The control plane compiles your abstractions into Kubernetes primitives and lets you see exactly what it produced. The abstraction helps, but never hides.
One Tab. One Platform. Everything Connected.
Backstage gives developers the portal. OpenChoreo gives platform engineers the platform behind it.