Backstage Integration

Warden turns the Backstage portal your platform team already runs into the golden path for creating, documenting, and cataloguing capabilities. It lands the reviewed capability.yaml on the second of the Fleet's three surfaces. Available in the Enterprise edition.
Read the Warden docs

One golden path to a new capability

Warden ships a Backstage software template and a scaffolder backend module. A developer answers a short wizard and gets a repository, a spec, docs, and deployment manifests — instead of copy-pasting last quarter's repo.
A guided wizard: name the capability, pick the adapters it exposes, choose the APIs it consumes, and select the target repository.
Adapter pre-selection
Enterprise
Tick MCP, REST, and/or Agent Skills and the generated capability file arrives with the matching exposes blocks already in place.
TechDocs from day one
Enterprise
Generates mkdocs.yml and a docs tree, and sets the TechDocs annotation, so the capability has documentation from the moment the repository exists.
Deployment manifests
Enterprise
Scaffolds a Kubernetes ConfigMap and a Skipper Capability custom resource, so the path from portal to cluster is already laid.

OpenAPI in, OpenAPI out

Warden contributes two custom scaffolder actions, backed by the Ikanos CLI on your Backstage backend. Existing API entities become consumes blocks; the capability's REST adapter becomes a published OpenAPI document.
Pick API entities from the Backstage catalog and Warden converts them into Ikanos consumes files — only APIs with an OpenAPI spec are offered.
Export the exposed API
Enterprise
Generates an openapi.yaml document from the capability's exposed REST adapter, ready to register as an API entity.
Stays in sync
Enterprise
Scaffolds a GitHub Actions workflow that regenerates the OpenAPI document whenever the capability file changes on main.

Capabilities in the catalog you already open

Every scaffolded capability registers as a first-class Backstage entity, so it sits alongside the rest of your software and participates in the same dependency graph.
Registers the capability as a Component and the OpenAPI document it exposes as an API entity, wired together via providesApis.
Upstream relations
Enterprise
Links the component to every catalog API it consumes, so the upstream dependencies are visible in the graph before anything changes.
Adapter tags + Kubernetes link
Enterprise
Tags the component with the adapters it exposes and sets the Kubernetes annotation, so the Backstage Kubernetes plugin can surface the running workload.
Fleet explorer
Roadmap
A full-page dependency graph across the entire fleet, with impact tracing and duplicate detection so teams consolidate instead of rebuilding.

Governance, today and next

Capability specs are governed by Polychro today — inline in Crafter as you type, and in CI through the Polychro GitHub Action. Bringing those same rule packs into the portal is what comes next.
Polychro rule packs in the portal
Roadmap
Surface the same built-in and custom rulesets that already run in the IDE and CI as catalog-visible findings on every capability.
Scorecards
Roadmap
Score every capability against the Cost, Risk, and Velocity pillars, so quality is visible without opening the repository.
CI merge gates
Roadmap
Portal-managed governance policies enforced as merge gates. Policy as code, versioned in Git alongside the specs it governs.
Impact tracing
Roadmap
When a capability or upstream API changes, see every downstream consumer in the fleet before the change ships.

Ready to scaffold and catalog capabilities in Backstage?

Warden is available in the Enterprise edition. Read the integration guide in the Shipyard, or talk to us about a trial.
Read the Warden docs
Talk to us about a trial