WSO2 is now Choreo LabsLearn more

Trusted AI Governance
Build

Create agents and AI apps with the tools and languages your teams already use.

Connect

Link agents securely to your APIs, data, models and business systems.

Run

Deploy, observe and operate agents and AI apps reliably at any scale.

Govern

Control identity, access, cost and policy for every agent in production.

Agent Management

Developer Platform

  • API Management Cloud

    Design, secure and publish APIs with governance and analytics built in.

    Sign Up Now
  • Integration Cloud

    Connect apps, data and AI agents with low-code and pro-code integration.

    Sign Up Now
  • Identity & Access Management Cloud

    Secure sign-in and access for customers, partners, workforce and agents.

    Sign Up Now
  • Agent Management Cloud

    Build, run and govern AI agents with full visibility and control.

    Sign Up Now
  • Developer Platform Cloud

    Ship cloud-native apps faster on an internal developer platform.

    Sign Up Now

Self-Hosted

Full control over your stack. Deploy directly to your own servers, bare metal, cloud, or Kubernetes environment. Your data never leaves your perimeter.

Product Downloads
Choreo Labs
AI Governance
Platform
Solutions
Resources

For Backstage Teams

Your portal is ready. Now build the platform behind it.

Backstage gives developers a great experience layer. OpenChoreo adds the platform behind it, turning developer actions into governed, production-ready workloads across your Kubernetes environments.

The Problem Statement

The hard part starts after the catalog

You invested in Backstage, and it delivered. But as developers start asking harder questions, the limitations of a portal without a platform underneath it become clear.

The Path Forward

The three stages of Backstage maturity

STEP 1

Just a Catalog: Service Discovery

Services are registered. Docs and ownership are centralized. It's far better than tribal knowledge, but it's still read-only. Developers look things up; they don't act from here.

STEP 2

An Interactive Map: Live Visibility

Plugins surface live Kubernetes status, recent deployments, CI/CD results. Developers can see what's running in Kubernetes, but the moment they need to act on it, the complexity leaks through.

STEP 3

An Actionable Platform: Self-Service Execution

A runtime sits beneath Backstage. Developers deploy, promote, and configure from the portal. Golden paths are enforced at the infrastructure level. Runtime state flows back automatically.

OpenChoreo is the runtime that bridges Stage 1 and Stage 3, adding the missing execution layer beneath your Backstage portal. No rip-and-replace. It's designed to plug directly into your existing catalog.

Read the Docs

How It Works

From point-to-point integrations to a platform architecture

Most Backstage deployments grow organically. Each new capability wired in manually, one integration at a time. OpenChoreo replaces that with a layered architecture that scales.

Learn more about OpenChoreo
  1. Start with Backstage

    You adopt Backstage as your developer portal. Teams register services, docs get centralized, then the requests come in. CI status, live Kubernetes health, observability links. Each answer becomes a new point-to-point integration. This is the messy middle.

  2. Add a control plane

    Instead of wiring Backstage to every tool, a control plane sits between your portal and your infrastructure. Developers and platform engineers work with high-level abstractions; the control plane compiles these into Kubernetes config and feeds runtime state back into Backstage automatically.

  3. Organize your runtime

    Behind the control plane, your runtime separates into purpose-built planes: the Workflow Plane for CI/CD, the Data Plane for running workloads, and the Observability Plane for logs, metrics, and traces — all scoped back to each component in Backstage.

Platform Maturity Assessment

Where does your Backstage deployment stand?

Answer 9 questions to find out whether you're running a catalog, an interactive map, or a true actionable platform, and what it would take to close the gap.

Discovery & VisibilityQuestion 1 of 9

How do developers in your organization find information about services — who owns them, what APIs they expose, whether they're healthy?

What changes when you add a runtime.

OpenChoreo doesn't replace Backstage; it gives it an engine.

Backstage and OpenChoreo
  • CI/CD and GitOps, built in

    Stop wiring pipelines to clusters. OpenChoreo handles the full path from source code to production, with Backstage showing the result, not just a link to another tool.

  • Observability wired to your catalog

    Logs, metrics, and traces appear scoped to each Backstage component and environment. Developers get the full picture via a single pane of glass, with no configuration required.

  • Golden paths that stay golden

    OpenChoreo enforces relationships between components and environments at the infrastructure level. Standards aren't just documented, they're compiled into every deployment.

  • Zero rip-and-replace

    OpenChoreo integrates with your existing Backstage catalog and the tools already registered in it. Your current investments stay intact; the runtime fills the gap.

  • AI agents as first-class platform participants

    When your platform has well-defined abstractions and a control plane, AI agents can interact with it just like developers do: creating components, triggering deployments, querying service dependencies, and surfacing root causes via MCP servers and agent skills. Good platform architecture is what makes AI actually useful in your infrastructure.

OpenChoreo is a CNCF Sandbox project. It is an open-source developer platform for Kubernetes with an active contributor community. The architecture described here is also documented in the CNCF Platform Engineering Maturity Model.

1-Week Quick Start

See it working in your environment, free

  1. Day 1–2

    Onboard sample services

    We work with your team to connect a set of real services to OpenChoreo, demonstrating a complete code-to-cloud flow in your environment.

  2. Day 2–3

    Populate Backstage natively

    Watch those services automatically appear in your Backstage portal with live logs, metrics, GitOps state, and deployment history, no manual wiring.

  3. Day 3–4

    Validate golden paths

    Test our architectural abstractions and see how they eliminate the need for glue code while enforcing your org's standards at the infrastructure level.

  4. Day 4–5

    Expert debrief & roadmap

    Our platform architects walk you through findings, answer your team's questions, and co-design a migration path that respects your existing toolchain.

Try it on your own cluster, free for a week

No commitment. No rip-and-replace. Runs in your own environment.