Compass

At a glance

Compass is a cloud software catalog for tracking components, owners, dependencies and health standards. Its useful audience is now existing customers planning a transition: sales ended on 13 May 2026, and the vendor is moving catalog and scorecard capabilities to DX Fabric. For a new setup, skip Compass as a fresh purchase and assess a supported alternative. For an existing installation, the migration details deserve your time before more work goes into the catalog.

Good fit

Teams already using Compass who need to understand what moves and what must be rebuilt. A component catalog connects a service or repository with its owner, relationships and health information; scorecards apply criteria to those components. The migration guide says catalog metadata and dependencies can transfer to DX, but scorecards must be recreated. That distinction makes an inventory of your existing rules more valuable than assuming a complete copy.

Consider something else when

You are choosing an internal developer portal for a new team, or expect every integration to survive migration unchanged. The official migration comparison lists gaps in some Jira links and says operations and alerts move to Jira Service Management, rather than DX. Existing Compass access can end with your contract; the planned end-of-support date of 31 December 2027 is not a promise that every customer retains access until then.

Start here

For an existing site, start with one representative component: list its owner, dependencies, custom fields, scorecards and operational links. Compare that inventory with the migration guide before scheduling onboarding through your administrator and account team. The documented connector imports catalog data and requires keys for both services. Check team assignments too: the guide says a user belongs to one DX team and team leads need review. No account or migration was exercised for this guide.

Cost and requirements

Compass is cloud-only; its licensing page does not offer a Data Center deployment. Full users are billable, while basic users have more limited access. For an existing customer, confirm the remaining contract and DX terms with the account team rather than treating the public price calculator as a new-customer offer. Migration transfers organizational catalog data between services and requires authorized credentials; inspect the connector scope before handing over keys.

Limits to know

The public pricing interface and current migration documentation were inspected, not an authenticated catalog. The pricing page has conflicting retention copy: Premium says two years in its heading but one year in the expanded explanation. Do not use that page alone to guarantee how long historical metrics or scores remain. The migration guide describes a month with both products after onboarding, but timing, commercial terms and the completeness of your particular migration need confirmation.

Related work

• Jira Service Management: destination for operations and alerts (complement)

Still unclear

• Which DX commercial terms and cutover date apply to your existing contract, and what retention commitments cover the history you need to preserve?