Your architecture, alive.

Navo navigator looking across the open ocean at sunrise

Navo

Your architecture, alive.

YAML in Git becomes a living map and wiki. Graph, CLI, navo-mcp for agents. No platform team.

  • Unlimited viewers free
  • Git YAML as source of truth
  • Static SPA, private-network ready
  • MCP for AI agents

How Navo works

1

Describe

Write architecture in YAML — or generate a draft with navo scan / convert — and keep it in Git.

architecture.yaml
services:
  - id: api-gateway
    name: API Gateway
    type: service
    group: edge
    links:
      - auth-service
      - user-service
2

Compile

Navo validates schema and integrity, then builds a living architecture map for the SPA.

APIAuthUsersData
3

Explore

Explore the graph, open service detail, read wiki pages, annotate, and contribute via PR.

ADOTerraformTerragruntAnsibleAKSOpenShiftTFEJFrogESAWS

API Gateway

edge · service

healthy
OverviewLinksReposDocs

Central edge entrypoint routing auth and user traffic into the platform mesh.

Owner

Platform

Runtime

AKS

Repos

gateway-api

Wiki

ado.md

Capabilities

More than a diagram tool

Visualization, Git integration, AI imports, and agent-ready MCP - the living architecture platform for teams tired of stale slides and heavy IDPs.

Coming in the next release

A diagram you can actually read

Switch from the graph to a new HTML diagram view. Services show up as cards with clear labels and squared-off connections. Use it alongside the existing 2D and 3D views.

Navo HTML diagram view of the Sample Edge Stack. Service cards sit in Edge & Delivery, Platform Services, and Data groups, with labeled HTTPS, HTTP, Postgres, and Redis connections.
Sample Edge Stack in the HTML diagram’s columns layout.
Close-up of HTML diagram cards for Catalog API, Identity Provider, Orders API, PostgreSQL, and Redis Cache, with labeled wires between platform services and data stores.
Cards show the service name, a short summary, and the ports and protocols in use.

Readable cards

Each service is a card with a clear name, summary, and connection labels — not a tiny node you have to hover.

Two layouts

Keep the same positions as the 2D map, or switch to a left-to-right columns layout that groups related services.

Rearrange and export

Drag cards or groups to tidy the picture, then download a single HTML file of the diagram.

In the next release, open Graph controls and choose HTML. 2D and 3D stay as they are.

Use cases

Built for platform teams, architects, and AI-era workflows

Whether you are escaping stale diagrams, avoiding Backstage fatigue, or feeding agents real topology - Navo keeps architecture living next to code.

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.

  • 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.

  • 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.

  • 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

Explore all use cases →

Compare

Navo vs Backstage, IcePanel, and Lucidchart

Navo is the simplest Git-native architecture browser for teams that want a living map next to code - not a full internal developer portal and not another slide deck.

Feature comparison of Navo versus Backstage, IcePanel, and Lucidchart
CapabilityNavoBackstageIcePanelLucidchart
Git-native source of truthYAML in GitCatalog + pluginsCloud workspaceCloud diagrams
Interactive living mapPartial (plugins)Static / limited
In-app wiki next to the mapTechDocs
AI YAML / diagram importsVariesLimitedImport only
navo-mcp for AI agents (tools + resources)Emerging
CLI (bulk + AST → YAML)Scaffolders
Unlimited free viewersSelf-host ops costPer-seatPer-seat
Deploy modelStatic SPA / DockerHeavy IDP stackSaaSSaaS
Time to valueMinutesMonthsDaysHours
Requires platform team

Want the deep dive? Navo vs Backstage

Built for teams who need the full picture

  • Architecture lives in slides and dies in Confluence.

  • Only two people know how the platform fits together.

  • Diagrams drift from the real system.

fremen-platform-ref · v1.0.021 services
ADOTemplatesTFTGTFES3AKSAnsibleAAPPackerJFrogDelineaADOCPArgoKafkaESAzureAWSGCPVMware

Navo keeps your architecture living next to the code.

  • Git is the source of truth.

  • Validate in CI, deploy anywhere.

  • Static SPA - simple and secure.

  • Optional Elasticsearch for search.

  • Annotations stay local until you export for a PR.

  • Operator CLI for scan, convert, and deploy.

A workflow that fits how developers work

Edit YAML in Git

Define services, groups, edges, and docs — or seed maps with navo scan / convert.

Validate in CI

Catch issues early with schema and integrity checks.

Deploy Anywhere

Docker/nginx, operator CLI, Kubernetes, or static hosting.

Explore & Evolve

Graph, detail, wiki, annotate locally, and contribute via PR.

Built around Git, not around a platform team

Navo keeps architecture canonical in your repository. Search indexes and browser annotations are helpers - never a second source of truth.

Git remains canonical

Your architecture map lives in the repository. Navo reads compiled config - it never becomes a second source of truth.

Changes ship through pull requests

Annotate locally, export merged YAML, and open a PR. Reviewers validate schema in CI before merge.

Deploy as a static SPA

Ship with Docker and nginx, Kubernetes, or any static host. Private DNS and VPN-friendly for internal maps.

Unlimited viewers

Anyone with access can browse maps. Editors are the people who change architecture YAML - not every visitor.

Try free. Desktop binary. Team self-deploy.

Unlimited viewers on every plan. Desktop is a signed binary; Team delivers via ACR + minted license.

Free

Try live demos. Unlimited viewers. No card.

$0

  • Free Desktop download (Linux/Windows) — viewer mode until licensed
  • Live interactive demos — explore real maps in the browser
  • Unlimited viewers on every plan (browse without an editor seat)
  • Git YAML as source of truth (as shown in demos)
  • See graph, wiki, and Git-native workflow before you buy
Download free Desktop

Desktop

Signed Tauri binary for your Mac, Windows, or Linux host.

$5

per editor / month

  • Checkout → download signed Desktop binary (macOS / Windows / Linux)
  • Interactive map (2D/3D) from Git YAML + in-app wiki
  • CLI: scan, convert (Lucid/Mermaid/draw.io), local/Docker
  • navo-mcp (read-only default, Git-backed)
  • Local annotate + export merged YAML for PRs
  • Unlimited viewers · individual editor SKU
Get Desktop
Recommended

Team

Mid-market self-deploy: minted license + ACR images and Helm.

$15

per editor / month

  • Checkout → mint NAVO- license → short-lived ACR pull token
  • Pull container images + Helm chart; license entitles update pulls
  • Self-deploy for your team (commercial editor seats)
  • Optional Elasticsearch (when enabled)
  • Priority support
  • Desktop binary included as a perk — primary delivery is container
  • Roadmap (not available yet): shared overlays, SSO, AI health checks
Start a Team trial

Enterprise

Regulated/private deploy via ACR + license, with support/SLA.

Custom

  • Same ACR + minted-license delivery path, sized for your boundary
  • Helm / ACR self-host + support and SLA discussion
  • Honest today: ship SPA / CLI / MCP containers inside your network
  • Roadmap (not available yet): RBAC, audit, dedicated server product
Talk to us

Looking for the full comparison? See pricing details

FAQ

Frequently asked questions

Straight answers about Git-native architecture browsing, Backstage alternatives, and MCP.

What is a Git-native architecture browser?

A Git-native architecture browser treats architecture definitions stored in Git (usually YAML) as the system of record, then renders them as an interactive map teams can explore. Navo compiles YAML into a living graph with service details and an in-app wiki — without a separate SaaS diagram store. 2D and 3D views ship today; a new HTML diagram view (readable cards and a single-file export) is coming in the next release.

How does Navo compare to Backstage?

Backstage is a full internal developer portal (catalog, scaffolder, plugins) that often needs a dedicated platform team. Navo is a focused Architecture Browser: YAML in Git → interactive map + wiki, with MCP for agents. Teams that just want the map use Navo in minutes instead of months of portal ops.

Does Navo support diagram imports and AST parsing?

Yes. The operator CLI supports diagram imports (Lucidchart, draw.io, Mermaid) and AST → YAML scan so brownfield systems can become living maps without redrawing everything by hand. A generative AI YAML helper is on the roadmap — not shipped yet.

What is Navo's MCP server for?

navo-mcp is Navo’s Model Context Protocol server. It exposes ArchitectureMap YAML to AI hosts through typed tools (list maps, load topology, find paths, validate drafts), navo:// resources, and workflow prompts. Agents get the same living map humans browse — with Git as the source of truth and read-only as the default.

Is Navo free for viewers?

Yes. Unlimited viewers can browse architecture maps on every plan. Free is $0 via live demos at /demo. Desktop ($5/editor/mo) is the signed Tauri binary path; Team ($15/editor/mo) is ACR + minted-license self-deploy for commercial editors.

Does Navo require Elasticsearch or a cloud dependency?

No. Git YAML remains canonical. Elasticsearch is an optional secondary index. Deploy Navo as a static SPA with Docker/nginx or any static host - including private networks behind VPN or private DNS.

How does Navo keep architecture maps up to date automatically?

Through CI/CD pipeline integration. After every merge the Navo CLI runs navo scan on application and IaC trees, commits updated YAML back to Git, and lets Argo CD or Flux redeploy a locked-down Navo SPA in Kubernetes. Maps stay current without manual diagram editing.

Can Navo import diagrams from Lucidchart, draw.io, or Mermaid?

Yes. The operator CLI supports navo convert for Lucidchart JSON, draw.io XML, and Mermaid markdown. Each format is translated into Navo's ArchitectureMap YAML so existing diagrams become interactive, version-controlled maps immediately.

What is the Navo operator CLI?

The Navo operator CLI (navo) is a Go binary that automates architecture map workflows. Key commands include scan (AST-based codebase → YAML), convert (Lucidchart, draw.io, Mermaid → YAML), start/stop/status for local and Docker, and init for bootstrapping new projects. It runs in CI/CD pipelines or on developer machines.

Can I deploy Navo in a private Kubernetes cluster?

Yes. Navo is designed for private, locked-down deployments. Ship the static SPA as a Docker image with ClusterIP or internal ingress only, NetworkPolicy deny-by-default, non-root containers, and read-only root filesystem. No public cloud dependency or external SaaS is required.

How does Navo compare to IcePanel?

IcePanel is a SaaS-hosted C4 modelling workspace with per-seat pricing. Navo is a Git-native architecture browser you self-host: YAML stays in your repo, the interactive graph deploys as a static SPA or Docker image, and unlimited viewers browse for free. Navo adds an operator CLI for codebase scanning, MCP for AI agents, and an in-app wiki - without SaaS lock-in.

Does Navo work with AI agents and MCP?

Yes. navo-mcp works with any stdio MCP host — Cursor, VS Code, Claude Desktop, Claude Code, Gemini CLI, Grok, and similar agents. Default toolsets cover maps, graph queries (including find_path), and validation. Write and ops (scan/convert via the CLI) are opt-in behind explicit flags. MCP ships with Desktop and commercial Team/Enterprise deployments.

What tools does navo-mcp provide?

Default read-only tools include get_server_info, get_workspace_context, list_maps, get_map_summary, get_map, search_maps, get_node, list_nodes, get_edges, find_path, list_groups, validate_map, and validate_yaml. Opt-in write_map, scan_codebase, and convert_diagram require --allow-write and toolset configuration. See /docs#mcp and /features/mcp.

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.