Atlassian Compass is a cloud developer portal for components, scorecards and teams that Atlassian is phasing out in favor of DX. Pages here cover moving its catalog and scorecards to self-hosted Backstage.
Comparing Compass with self-hosted Backstage: component catalog and ownership, scorecards, integrations with Jira and Bitbucket, configuration as code, cloud-only hosting against running your own portal, and the effort Backstage takes.
Moving from Compass to Backstage: converting compass.yml files and UI-created components to catalog-info.yaml entities, mapping component types and relationships, re-creating teams from your identity provider, and rebuilding scorecards before Compass access ends.
Atlassian is phasing out Compass and moving its catalog and scorecards to DX. This page compares accepting the DX transition with moving to self-hosted Backstage or another portal, and the questions to settle before choosing.
Cost of ownership by component: Compass Standard and Premium per full user billed monthly, and an unknown DX price after the transition, against Backstage hosting, PostgreSQL, migration, plugin work and the platform team that runs it.
Getting your catalog out of Compass: components already defined in compass.yml files, components created in the UI that need exporting, scorecard definitions and team ownership, and how to turn them into a Backstage import plan.
Rebuilding Compass scorecards, such as production readiness, in Backstage with the Tech Insights plugins: facts, rule-based checks and maturity rankings, and what dashboards and alerts need extra work.
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.