KNOW THE HEALTH OF EVERY COMPONENT IN COMPASS.
Connect Atlassian Compass to Menza and ask about software components, owners, dependencies and scorecards in plain English — which services fail their scorecards, what depends on what, which components have no owner. Menza reads live through the official Compass API, and catalogue updates it proposes only go through once you approve.
- Reads developer data
- Can take action on Atlassian Compass, once you approve
- Connects via the official API
What can Menza do with Atlassian Compass?
Fix catalogue gaps with approval
Menza finds components missing owners, links or scorecard criteria, proposes the fixes, and applies them once you approve — so the catalogue stays trustworthy without a quarterly clean-up sprint.
See dependency risk clearly
Ask what depends on a component before you change it. Menza reads the dependency graph live and lists the services affected, with their owners, in one answer.
Track scorecard health over time
Menza reads scorecard results and metrics across components and teams, flagging where pass rates slide, so engineering standards are managed with numbers rather than nagging.
See these answers on your own Atlassian Compass data.
Menza working with Atlassian Compass.
Menza doesn't just answer questions about Atlassian Compass — it proposes the fix and, once you approve, does the work. You stay in control; nothing changes until you say go.
Menzajust now14 of your 92 components have no owner — six of them are dependencies of tier-1 services. I'll assign those six to the teams that own their upstream services.
Menza6m agoThe production-readiness scorecard pass rate slipped to 68% — twelve components lost points on documentation this month. I'll add the missing documentation links to the nine components that already have runbooks.
Connect Atlassian Compass in a couple of clicks.
Is my Atlassian Compass data secure?
Your credentials are encrypted at rest and never exposed to the AI. Menza reads your data through the provider's official API using the access you grant, and you stay in control of what it can do — read-only by default, with any actions gated behind your approval.
Read our privacy policy- Encrypted in transit and at rest
- Scoped access — you choose what Menza can see
- Read-only by default; any action needs your approval
- Credentials are encrypted and never shown to the AI
- Revoke access at any time
Connectors like Atlassian Compass.
Atlassian Compass questions, answered.
How does Menza connect to Atlassian Compass?
With your Atlassian account email and an API token — pasted once, encrypted at rest, and never shown to the AI. Menza queries the official Compass API server-side against your site, so the component catalogue answers questions without anyone opening it.
What can Menza answer about my Compass data?
Software components and their owners, dependency relationships in both directions, scorecard results, and component metrics. Ask "which tier-1 services fail production readiness?", "what depends on the auth service?" or "which components have no owner?" — answered from the live catalogue.
Is my Compass data safe with Menza?
Yes. Your token is encrypted at rest and never exposed to the AI, and Menza reaches only what your Atlassian permissions allow. This connector supports actions — catalogue updates — but any action waits for your explicit approval before a component record changes.
We have hundreds of components — will this still work?
Yes. Menza queries the Compass API rather than scrolling the UI, so questions across a large catalogue — unowned components, failing scorecards, dependency fan-out — resolve in one pass. The bigger the catalogue, the more time the questions save.