Backstage Argo CD plugin setup
Showing Argo CD sync and health status on Backstage entity pages: the Roadie and Red Hat plugin options, connecting to one or several Argo CD instances, linking applications to entities and credential handling.

Setting up widely used third-party and community Backstage plugins that connect the portal to delivery, incident, quality and cost tools, and vetting plugins before installing them.
Showing Argo CD sync and health status on Backstage entity pages: the Roadie and Red Hat plugin options, connecting to one or several Argo CD instances, linking applications to entities and credential handling.
Bringing PagerDuty on-call schedules and incidents into service pages with PagerDuty's own plugin, mapping services to entities and what access the API token needs.
Displaying SonarQube quality gates and metrics per component: the community plugin, the sonarqube.org/project-key annotation, connecting to SonarQube Server, and keeping the token out of the frontend.
Showing Jenkins job status and history on entity pages: the community plugin, the jenkins.io/job-full-name annotation, multiple Jenkins instances and API token scope.
Viewing and re-running GitHub Actions workflows from Backstage: the Spotify-maintained plugin, the github.com/project-slug annotation, and user OAuth tokens versus a shared credential.
Publishing an internal technology radar in Backstage: the Spotify Tech Radar plugin, where radar data comes from, and keeping it current through a review process.
Scoring services against standards such as owners, docs and dependencies: the Tech Insights plugin, fact retrievers and checks, and how scorecards drive catalog completeness.
Showing cloud cost by team or product in Backstage: the Spotify Cost Insights plugin, the cost data client you must implement, and pairing costs with catalog ownership.
Linking Grafana dashboards and alert states to catalog entities, connecting through the proxy or a backend plugin, and keeping Grafana credentials out of the browser.
Showing Snyk project issues on entity pages with the plugin maintained by Snyk, mapping projects to components and token handling.
Listing secrets paths for a component from HashiCorp Vault or OpenBao with the vault.io/secrets-path annotation, what the plugin shows and does not show, and the token policy it needs.
Showing Tekton PipelineRuns for a component from Kubernetes clusters with the Red Hat plugin, and how it relies on the Kubernetes plugin's cluster configuration.
A checklist before installing a plugin: who maintains it, whether it lives in community-plugins or a vendor repository, release activity, the permissions and credentials it needs, and why plugins run unsandboxed.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.