Architecture Graph
Platform Architecturelive
Pan, zoom, filter, and explore your entire system.
Navo
Your architecture, alive.
The Git-native Architecture Browser — YAML in, interactive map out. No platform team required.
How Navo works
1
Describe
Write your architecture in YAML and keep it in Git.
architecture.yaml
services:
- id: api-gateway
name: API Gateway
type: service
group: edge
links:
- auth-service
- user-service2
Compile
Navo validates your config and creates a living architecture map.
3
Explore
Explore the map, read docs, and understand how it all connects.
API Gateway
edge · service
OverviewLinksReposDocs
Central edge entrypoint routing auth and user traffic into the platform mesh.
Owner
Platform
Runtime
AKS
Repos
gateway-api
Wiki
ado.md
Powerful surfaces. One source of truth.
Service Detail
API Gateway
edge · service
OverviewLinksReposDocs
Central edge entrypoint routing auth and user traffic into the platform mesh.
Owner
Platform
Runtime
AKS
Repos
gateway-api
Wiki
ado.md
Click any node to see summaries, links, repositories, and 5W narratives.
In-App Wiki
Deploy runbook
1. Validate config
Run schema checks in CI before merge.
2. Compile map
Generate architecture.json from YAML.
3. Redeploy SPA
Ship the static build to nginx.
Read runbooks and docs in context without leaving the app.
Share & Contribute
Export changes
3 ready- + link: ado → delinea
- ~ note: terraform runners
- + wiki: openshift.md
Annotate locally and export changes for a pull request.
Multi-System Maps
Select system
Platform Architecture
- Platform Architecture
- Production Services
- Product Stack
- Sandbox
Switch between architectures and keep everything in Git.
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
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.
A workflow that fits how developers work
Edit YAML in Git
Define services, groups, links, and docs.
Validate in CI
Catch issues early with schema checks.
Deploy Anywhere
Docker, Kubernetes, or static hosting.
Explore & Evolve
Understand systems, annotate, and contribute.
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.
Start free. Scale when your team needs more.
Unlimited viewers on every plan. Pay only for editors who change the map.
Community
Everything you need to map architecture in Git.
$0
- Open source
- Full interactive graph
- Git YAML
- Wiki reader
- Docker deployment
- MCP server
- AI YAML generator
- Unlimited viewers
Team
Collaboration and health checks for growing teams.
$15
per editor / month
- Everything in Community
- Shared overlays
- Annotation history
- SSO
- AI architecture health checks
- Optional Elasticsearch read path
- Priority support
- Unlimited viewers
Enterprise
Self-hosted controls for regulated environments.
Custom
- Self-hosted server
- RBAC
- Audit logs
- CI/CD auto-compile
- Custom branding
- SLA
- Enterprise support
- Unlimited viewers
Looking for the full comparison? See pricing details
Ready to make your architecture alive?
Join engineers who use Navo to see, share, and evolve their systems.