Your architecture diagramsare lying.
They were true the day you drew them. DiagramOps connects your repos, Notion, Confluence, and Google Docs — and catches the moment your diagrams and runbooks stop matching reality, with the evidence and a proposed fix. Nothing changes without your review.
DiagramOps: 7-day free trial, then $149/mo — includes 3 team workspaces and 250 drift checks a month. The Mermaid editor stays free — no signup, no card.
POST /api/checkout now requires currency, but the payment diagram and the runbook still document the old contract.
@@ CheckoutRequest
amount: number
+ currency: string // now REQUIRED
items: LineItem[]Review-first: nothing changes until you decide.
Sound familiar?
The onboarding lie
A new engineer asks how the system works. The wiki answer was true two years ago — now it costs them a week of false starts.
The 2 a.m. runbook
Mid-incident, step 3 of the runbook points at a service you deleted in March. Now you're debugging the docs and the outage.
The diagram nobody updated
The architecture diagram was perfect the day it was drawn. Forty merges later it's fiction — because updating it was everyone's job, so it was no one's.
Documentation doesn't rot because people are lazy. It rots because nothing tells them the moment it stops being true. DiagramOps is that trigger.
Connect it once. It watches forever.
DiagramOps turns your diagrams, docs, and runbooks into evidence-linked knowledge — then checks that knowledge against your system on every merge.
- 1
Connect your sources
GitHub repos plus read-only Notion, Confluence, and Google Docs. DiagramOps draws the architecture from the code and indexes your docs as tracked knowledge.
- 2
It watches every change
Every pull request, every merge, and a weekly audit — checked against the actual routes, schemas, jobs, and docs. 250 checks a month included.
- 3
You get the catch
An email, a PR comment, and a review finding with the evidence, the diff, and a one-click fix — or a pull request that corrects the doc where it lives.
Replace manual sync with automatic drift detection
Knowledge drift review
This merge changed your architecture. DiagramOps opened a review finding with the proposed diagram update — nothing changes until you approve it:
GitHub integration — architecture
- Added
Merge to mainDrift detection- Removed
Manual sync- New connections
Merge to main → Drift detectionDrift detection → Linked diagram- Removed connections
GitHub webhook → Manual syncManual sync → Linked diagram
Review the finding — apply the patch in one click; the previous version stays in history.
Diagrams by MermaidCreator — keep your architecture diagrams alive in your repo.
What DiagramOps does all day
Every PR gets the picture
Pull requests that change your architecture get a comment with the impact, the risk, and a diagram of exactly what the change touches — before anyone reads the diff.
Review-first drift findings
On merge and in a weekly audit, DiagramOps compares your diagrams and docs against the code. Drift becomes a finding with the evidence and a proposed fix — nothing changes until you approve.
Watches your docs, not just your repo
Connect Notion, Confluence, and Google Docs read-only. Runbooks and specs become tracked knowledge — edit one, and the linked diagrams get flagged for review.
The catch comes to you
Owners get an email the moment a finding opens, and a Monday digest of what was checked, caught, and fixed. No dashboard-checking habit required.
Fixes land as pull requests
Accept a doc fix and DiagramOps opens the PR for you — the correction ships through your normal review process, not a copy-paste chore.
Diagrams that stay stable
Drift checks edit the existing diagram minimally instead of redrawing it — a one-route merge shows up as a one-node change, so every diff is one you can trust.
We run DiagramOps on this website.
mermaidcreator.com is a DiagramOps workspace: 56 drift checks ran on our own repo and docs this month — the last one 442h ago.
It starts with the best AI Mermaid editor
Drag it, type it, or describe it — MermaidCreator drafts the diagram and keeps the code in sync. Built on Mermaid.js, so your diagrams stay portable, versionable, and text-first.
Drag boxes, get clean code
Build on an infinite canvas. Every node you drag, drop, or connect writes clean, diffable Mermaid underneath — no syntax to memorise.
Type Mermaid, see it instantly
Paste existing Mermaid or write it from scratch in a focused editor with a live side-by-side preview. Code and canvas always stay in sync.
Lands crisp in GitHub, docs & slides
Share a live link, embed in READMEs and wikis, or export PNG, SVG, and PDF with fonts embedded — no clipped labels.
Free forever for the editor — no signup, no card. Sign up for cloud saves and 5 free AI generations a month; Pro makes them unlimited for $9.
Built for teams, not just browser tabs
Bring everyone's diagrams into one workspace. Ask your question where the diagram is, and see who else is in the room.
One shared workspace
Roles, shared diagrams, and a single bill. Owners and admins decide who can edit — viewers come along for free.
Comment in context
Leave a note pinned to the diagram instead of a Slack thread nobody can find later. Resolve it once it's handled.
Knowledge, not files
On DiagramOps, diagrams and docs become tracked knowledge with evidence links — so the answer to "is this still true?" is always one click away.
Start free. Upgrade when it matters.
Free
$0The full editor, live preview, share links, and monthly AI generations. No card, no signup to start.
Open the editorPro
$9/moUnlimited AI generations and saved diagrams, full version history, PDF export. For the person who diagrams every week.
See pricingDiagramOps
$149/moEverything in Pro for your whole team, plus living architecture diagrams, PR impact comments, and review-first drift detection across repos and docs. Includes 3 team workspaces and 250 drift checks a month.
Start 7-day free trialOne stale runbook found mid-incident costs more than a year of DiagramOps. Compare plans in detail.
How MermaidCreator compares
The portability of text-based Mermaid, the ease of a visual canvas, and AI on top — without the trade-offs of either extreme.
| Capability | MermaidCreator | Hand-written Mermaid | Drag-only diagram tools |
|---|---|---|---|
| Visual drag-and-drop editing | Yes — full canvas | No — code only | Yes |
| Text/code source of truth | Yes — clean Mermaid | Yes | No — opaque binary files |
| AI generation from a prompt | Yes — Claude | No | Limited / add-on |
| Version-control friendly | Yes — diffable text | Yes | No |
| Renders natively in GitHub & docs | Yes | Yes | No — image export only |
| Works without knowing Mermaid syntax | Yes — drag, drop, or prompt | No — syntax required | Yes |
| Fix broken Mermaid automatically | Yes — one-click AI repair | No — debug by hand | No — can't import Mermaid |
| Generate an architecture diagram from a repo | Yes — from any GitHub repo | No — draw it by hand | No |
| Renders & updates inside pull requests | Yes — PR comments + drift detection on merge | No — manual | No |
| Real-time team collaboration | Yes — shared workspaces, comments, presence | No | Varies |
Frequently asked questions
- Is MermaidCreator free to use?
- Yes. The free plan lets you use the visual and code editors, render live Mermaid previews, keep up to 10 saved diagrams, run 5 AI generations per month, create public share links and embeds, see your recent version history, and export to PNG and SVG. You can start drawing without an account; signing up adds cloud saves. The Pro plan unlocks unlimited AI generations, unlimited saved diagrams, full version history, and PDF export.
- Can I generate diagrams from a text prompt with AI?
- Yes. MermaidCreator's AI is powered by Claude. You can generate a complete diagram from a single sentence, restructure an existing diagram with a follow-up prompt, or auto-repair broken Mermaid syntax. The free plan includes a set number of AI generations; the Pro plan makes them unlimited.
- How do I export and share my diagrams?
- You can export diagrams as PNG and SVG on the free plan, with PDF added on Pro. Diagrams can also be published as a live public share link or embedded directly in documents, wikis, and README files, so the rendered diagram stays up to date wherever it appears.
- What is DiagramOps?
- DiagramOps is MermaidCreator's plan for engineering teams whose diagrams and runbooks must stay true. Connect your GitHub repos, Notion, Confluence, and Google Docs; DiagramOps indexes them into evidence-linked knowledge, then checks that knowledge against reality on every pull-request merge and in a weekly audit. When a diagram or doc stops matching the system, it opens a review finding with the evidence and a proposed fix, emails the workspace owners, and posts the architecture impact on the pull request itself.
- Does DiagramOps change my diagrams automatically?
- No — DiagramOps is review-first. When it detects drift it opens a finding with the proposed update; your diagram and docs stay untouched until a human approves. Applying a diagram patch keeps the previous version in history, and for repo-backed docs DiagramOps can open a GitHub pull request with the fix so it lands through your normal review process.
- How much does DiagramOps cost?
- DiagramOps costs $149 per month and includes 3 team workspaces, 250 drift checks per month, 5 connected knowledge sources per workspace, unlimited AI generation, and team collaboration. New subscriptions start with a 7-day free trial (card required, cancel anytime). That is usually less than one hour of engineering time — and cheaper than one incident caused by a runbook that pointed at a service you deleted months ago.
More questions? Read the full FAQ.
Stop trusting diagrams on faith
Connect a repo and DiagramOps draws your architecture, then keeps it honest — every merge, every doc, every week.