Use cases

Who uses a Git-native Architecture Browser?

Mid-market and enterprise engineering orgs that want living maps without IDP tax - plus teams preparing architecture context for AI agents.

Platform teams

Platform team at scale

Give every squad a shared living map of the platform without standing up Backstage or hiring a portal team. Git stays the source of truth; stakeholders browse for free.

Outcomes

  • Onboard new engineers against a current map, not stale slides
  • Review architecture changes in pull requests
  • Share one URL for unlimited viewers behind VPN

Architects

Migration from Lucidchart / Confluence

Stop redrawing boxes every quarter. Import diagrams and generate YAML with AI, then keep the map alive next to the code that implements it.

Outcomes

  • Brownfield systems become YAML maps faster
  • Diagrams stop drifting from production reality
  • Docs live in the in-app wiki beside each service

AI / platform leads

AI agents querying architecture

Moor Cursor, Claude, VS Code, and other MCP hosts to navo-mcp so agents list maps, walk graph paths, and validate drafts against the same Git YAML the SPA renders — not hallucinated topology.

Outcomes

  • Typed tools for maps, nodes, edges, find_path, and validate
  • Read-only by default; write and scan/convert opt-in
  • navo:// resources and prompts for grounded agent workflows

Keep architecture living next to code

Reduce architecture drift and meetings. Unlimited viewers free. Try live demos, then Desktop for a signed binary or Team for ACR + license self-deploy — Git stays the source of truth.