Compass Is Being Discontinued.
Here Is What to Migrate To.
NOFire AI builds your catalog from live production signals. There is nothing to migrate: no YAML files to export, no catalog entries to re-create. Connect your stack and your catalog appears in 30 minutes.
Why Compass customers are leaving before Atlassian pulls the plug
The product is dead, and your next migration has already started
Atlassian ended Compass sales on May 13, 2026. Support ends December 31, 2027. Teams searching for a compass replacement in 2026 are not alone: those who migrated from Opsgenie to Compass are now being asked to migrate again, to a product with no proven feature parity. Every sprint you spend on Compass is a sprint you will spend undoing it.
YAML files drift from reality within weeks
Compass requires a compass.yml in every repo to register a service. Engineers skip updates during incident pressure and sprint crunch. Real-world adoption reports show 40 to 60 percent of catalog entries go stale within three to six months. Scorecards built on that data give false confidence about production readiness.
Self-service was removed, and the integration ceiling is low
Atlassian removed scaffolding templates from Compass on December 1, 2025, leaving it as a read-only catalog. Teams on GitHub, GitLab self-hosted, Azure DevOps, or non-Atlassian observability stacks hit thin integration layers. SSO and SCIM provisioning require a separate Atlassian Guard subscription, adding cost not in the original budget.
NOFire AI vs Compass: a direct feature comparison
Compass is a read-only catalog on a shutdown timeline. NOFire AI builds a living catalog from production signals with no migration deadline and no YAML to maintain.
| Capability | NOFire AI | Compass |
|---|---|---|
| Catalog data source | Observed from live production signals: DNS, L7 call graphs, Prometheus, CI/CD, incident history | Manually authored compass.yml files committed to each repo |
| Catalog accuracy over time | Continuous, automatic. Agents observe changes as they happen | Degrades as teams skip YAML updates. 40-60% staleness within 3-6 months is common |
| New service discovery | Appears automatically when agents detect new entities in the entity graph | Invisible until someone writes and merges a compass.yml |
| Production readiness scorecard | 4 binary checks against live signals: has_owner, has_metrics, has_alerts, is_spof | Rule-based checks against manually declared YAML fields; does not read live Prometheus or alert state |
| Dependency graph and blast radius | Built from observed L7 traffic patterns. PageRank-based blast radius calculated automatically | Requires manual dependency declarations in YAML. No blast radius inference |
| Self-service developer workflows | Continuous catalog updates, ownership assignment, and readiness tracking without manual input | Scaffolding templates removed December 1, 2025. Currently a read-only catalog |
| SSO and SCIM provisioning | Included. No separate identity product required | Requires a separate Atlassian Guard subscription at additional cost |
| Product roadmap investment | Active development. No migration deadlines imposed on customers | End-of-sale May 2026. End-of-support December 2027. No new features being built |
One panel. Every layer of service knowledge.
The service detail page in NOFire AI is populated entirely from what agents observe: entity graph, change events, Prometheus rules, incident history, and repository analysis. Nothing is declared. Nothing goes stale.
The checkout service orchestrates the end-to-end purchase flow, coordinating payment processing, inventory validation, and shipping arrangements. It acts as the central transaction coordinator, calling payment, product-catalog, cart, item validation, shipping, currency, email, kafka, and flagd.
2h ago
4d ago
9d ago
19d ago
Live health (SLO / error rate / saturation) arrives with the state engine.
Deterministic facts. LLM-narrated prose.
The catalog structure, dependencies, readiness, and blast radius come from your system, not from an LLM. The LLM only narrates what it cannot invent: prose about what the facts mean.
Every claim cited.
Known mitigations cite actual investigation IDs and change event records. If there is no evidence, the section says so. NOFire AI does not fill in gaps.
Provenance on every dependency.
Each dependency carries a label: runtime (observed from DNS/L7 call graphs), synthesized (inferred), or intent (declared). You see exactly how confident the catalog is.
Connect your stack. Your catalog appears.
No migration project. No catalog entries to write. No plugins to configure.
Connect your signals
Link your observability stack, Kubernetes, CI/CD, and incident tooling. NOFire AI starts reading your entity graph and change history immediately.
Agents distill knowledge
Deterministic extractors build a structured skeleton: ownership, dependencies with provenance, readiness checks, blast radius. No LLM invents facts.
Catalog stays current
Every deploy, incident, rollback, and ownership change is reflected automatically. Engineers read the catalog instead of maintaining it.
Switching from Compass
When does Atlassian Compass reach end of support?
Atlassian ended Compass sales on May 13, 2026. Support ends December 31, 2027. After that date, Compass receives no updates, security patches, or bug fixes. Teams currently on Compass need to complete a migration before the end-of-support deadline.
What is the best Atlassian Compass replacement?
The main options are Backstage (self-hosted, requires significant engineering investment), Cortex (enterprise, YAML-based), and NOFire AI, which builds the catalog automatically from production signals with no YAML files or migration project required. NOFire AI is the only option that removes the catalog maintenance burden entirely.
How long does it take to migrate from Compass to NOFire AI?
Most teams have a working catalog from live production signals within 30 minutes of connecting their first integration. There are no compass.yml files to migrate: NOFire AI discovers services from your entity graph, change events, and telemetry. The catalog builds itself from what is already running.
Does NOFire AI work with teams not using Atlassian tools?
Yes. NOFire AI integrates with Prometheus, Grafana, Datadog, Kubernetes, GitHub, GitLab, PagerDuty, and other standard observability and CI/CD tooling. It does not require Jira, Confluence, or any other Atlassian product.
Support ends December 2027. Replace Compass with a catalog that maintains itself.
NOFire AI connects to your observability stack and infers your catalog from live signals. Most teams have a working catalog in 30 minutes. No YAML to migrate, no catalog entries to re-create.