Diagrams that don'tlie to you.
Stop guessing what your architecture looks like. UIGraph syncs from your codebase so diagrams stay accurate and backed by actual data.
Serverless request flow. Catalog components on the canvas. Click a node, see the fields behind it.
Nobody trusts the diagram in the wiki.
01
Drawn once
Someone captures the architecture in a drawing tool and considers it done.
02
Three deploys later
The codebase moves on. The picture is now a liability, not a guide.
03
Nobody updates it
Fixing the diagram means wrestling with a static file nobody wants to open.
Real architecture, not just shapes.
A box just says "API Gateway." A UIGraph node carries the real thing — text, config, even live code — synced straight from your repo.
Click any node on the canvas to open its data panel.
Git is the source
Treat diagrams exactly like code. UIGraph reads your configuration and Mermaid files on every deploy. Prefer to edit visually on the canvas? Save, and UIGraph opens a pull request with the changes.
# architectureDiagrams
architectureDiagrams:
- name: Checkout flow
path: ./docs/checkout-flow.mmd
contextPath: ./docs/checkout-flow.context.json
- name: Gateway request flow
path: .uigraph/diagrams/gateway-request-flow/gateway-request-flow.mmdSynced on deploy
· checkout-flow.mmd → canvasMove from idea to diagram in seconds, not hours.
Stop manually dragging shapes or tweaking pixel alignment. UIGraph's AI handles the boilerplate and design so you can focus on system architecture.
Generate with AI
Type a simple prompt. AI selects the correct diagram type and builds the initial canvas instantly.
> OAuth2 login flow between client, auth server, and user database
Beautify with AI
Pick a preset — Dark & Bold, Soft Pastel, Blueprint — or describe the style in plain English. Restyles color, layout, and grouping. Structure never changes.
Never let your documentation drift.
The Drift Detector compares your visual canvas against your active codebase on every sync — a deprecated microservice, a removed edge, a renamed table. UIGraph surfaces the gap. It does not rewrite the diagram to close it.
Caught on every sync
A microservice is deprecated
The catalog component on the canvas no longer describes the service in the repo.
- component: inventory-svc
An edge is removed from the code
The diagram still draws a call that the current commit does not make.
- checkout-service → payments-api
A database table gets renamed
The field on the node still points at a name the schema no longer uses.
- table: users_v1+ table: users
Built for how your team already works
Ask the diagram, not a person.
Every UIGraph diagram is available through MCP for your coding agents, and through Slack for your team. Same synced graph, same answer, wherever the question comes from.
For coding agents
What does Payment Succeeded lead to?
Same answer in Claude, Cursor, or GitHub Copilot — same graph the canvas already has.
get_diagram("checkout-flow") → context.json · nodes · edges
For your team, in Slack
Ask the diagram in Slack
Tag @UIGraph in any channel. Questions like "Which service handles Payment Succeeded events?" or "What databases touch the Auth flow?" get answered where your team already works.
Diagram slices in the thread
The reply is not text alone. UIGraph embeds the exact diagram slice that explains the flow directly in the conversation.
Grounded in code
AI Assist answers from your active, synced context. Same data the canvas reads, not a wiki page from last quarter.
Map your systems with complete peace of mind.
A map of your system is sensitive. UIGraph is designed so you never have to hand your architecture to anyone outside your perimeter.
Runs in your perimeter
Self-host with Docker Compose for evaluation or Helm and Terraform for production on AWS. Your architecture data never leaves your VPC.
Source-available
The full stack is published under BUSL-1.1. Read every line before you run it. The CLI is MIT. No black boxes.
SAML SSO
Seamless access management with Okta, Microsoft Entra, Google, and other standard identity providers.
Strictly scoped access
UIGraph only requests the permissions needed to read your architecture metadata. Your core intellectual property remains yours.
Frequently asked questions
Read the docsDraw it once. Never redraw it again.
Join the engineering teams building better systems with living documentation.