WillItSurvive

diagrams.net (JGraph)

Free diagramming tool (draw.io) that also sells paid apps inside Atlassian's Confluence and Jira.

Losing its protection
Assessed 23 July 2026 · Evidence as of 23 July 2026
The structural protection is eroding.
On the recordSince 23 July 2026 · Checkable from 2026 · Every call on the record Checkpoint: Atlassian's native Confluence/Jira whiteboard and diagramming roadmap update
The call

draw.io stays alive by being the free, embedded default inside Atlassian's tools, but that same dependence means Atlassian, or an AI agent that skips the UI entirely, could quietly take its place.

Diagrams.net (draw.io) lets people drag shapes around to create flowcharts, wireframes, and other diagrams. It makes almost all its money selling add-ons on Atlassian's Jira and Confluence platforms, which means it relies on Atlassian's goodwill and could be replaced if Atlassian builds its own diagramming tool. The real threat is that AI systems like Claude can now generate diagrams in draw.io's file format without users ever opening the app itself, turning the core task of drawing shapes into something you just ask an AI to do. The one thing that could change everything is whether Atlassian decides to build native diagramming straight into Jira and Confluence, which would cut off most of draw.io's revenue overnight.

Why
01
AI pressure: Claude, ChatGPT and MCP agent tools generating .drawio XML directly. AI chat tools now write draw.io's own file format from a prompt, so users get diagrams without ever opening draw.io's editor. Could AI do the core job? Only partly.
02
Bigger players: Atlassian. Atlassian owns the Confluence and Jira Marketplace where over 90% of draw.io's revenue sits, and could ship native diagramming any time. Could a giant copy it? Yes, easily.
03
What protects it. Two decades of free-tool goodwill and deep embedding as the default diagram app inside Confluence and Jira.
What would change this call
Atlassian announces native diagramming/whiteboard features built into Confluence or Jira. Would directly threaten draw.io's Marketplace revenue, its main income source.
Atlassian changes Marketplace fee structure or Forge app policies affecting third-party vendors. Would show the platform dependency risk materializing.
Growth or shutdown of third-party AI tools (ChatUML, next-ai-draw-io) generating .drawio files. Would show whether AI routes around draw.io's UI or reinforces its file format as standard.
Key numbers
  • ~$770K to $4M estimated annual revenue (2025-07-22)
  • $0 in disclosed outside funding, fully bootstrapped (2025-07-22)
  • 10-50 employees after 26 years in business (2026)
Named risks
  • Over 90% of revenue depends on Atlassian Marketplace goodwill and pricing policy. Severity: high
  • AI tools can already generate .drawio XML files without users opening draw.io's UI. Severity: high
  • 2024 precedent shows company willing to alter open-source license terms, risking community backlash or forks. Severity: medium
  • Small 10-50 person team with concentrated founder control creates key-person dependency. Severity: medium
  • Conflicting third-party revenue/entity data (Wiesbaden vs UK/CH) creates reporting confusion for investors and partners. Severity: low
Rivals, as read in July 2026
RivalDirectionEvidence
AtlassiancontestingHosts 90%+ of draw.io revenue via Marketplace; shipped native Confluence Whiteboards 2024-03-22
Lucidchartlosing toRanked above draw.io for real-time co-editing and Visio import in 2026 buyer's guides
MirocontestingPositioned as collaborative whiteboarding leader versus draw.io's technical diagramming focus, 2026
Microsoft Visiolosing toEnterprise incumbent via Microsoft 365 integration; draw.io framed as its free alternative
AI-native diagram tools (next-ai-draw-io, ChatUML, drawio-ninja)gaining onGenerate .drawio XML bypassing draw.io's UI entirely, active as of 2026-05
Questions people ask
Is diagrams.net (draw.io) profitable?
No audited figures are public, but draw.io Ltd has raised $0 in funding and has been self-funded since 2000, per Latka (2025-07-22). Its lean 10-50 person team and paid Atlassian Marketplace apps suggest a bootstrapped, likely profitable niche business rather than a loss-making venture.
Who owns diagrams.net?
diagrams.net is jointly owned by draw.io Ltd (England, company number 04051179) and draw.io AG (Switzerland, CHE-210.604.548, Zurich), per the company's own about page (2026). It renamed from JGraph Ltd to draw.io Ltd in September 2025; no external investors are disclosed.
Could AI replace diagrams.net?
Partially already happening: third-party tools like next-ai-draw-io and GitHub's official Copilot instructions (2026-03-26) generate valid .drawio XML files without users ever opening draw.io's UI. draw.io itself ships Claude-powered AI diagram generation and an MCP server (2026-06-29), racing to stay the rendering layer rather than be bypassed.
What is diagrams.net's biggest competitive threat?
Atlassian, which hosts over 90% of draw.io's paid revenue via its Confluence/Jira Marketplace and already shipped native Confluence Whiteboards on 2024-03-22. If Atlassian builds first-class native diagramming, draw.io's core monetization channel could be squeezed with little warning.
Did diagrams.net change its name or ownership recently?
Yes. The legal entity JGraph Ltd renamed to draw.io Ltd in September 2025, and the company now describes itself as jointly owned by draw.io Ltd (England) and draw.io AG (Switzerland), per the company's own about page and Wikipedia (accessed 2026-06-03).
What happened with draw.io's 2024 licensing controversy?
In August 2024 (version 24.7.8) draw.io added a clause to its Apache 2.0 license prohibiting use inside Confluence or Jira, aiming to protect its paid Atlassian revenue. After community pushback, it reverted the clause by December 2024 in version 25.0.2, per Wikipedia's Diagrams.net entry.
Timeline
  • 2026-06-29draw.io releases MCP server letting Claude, Copilot, Cursor generate diagrams programmatically
  • 2026-03-26GitHub ships official awesome-copilot instructions for generating valid .drawio XML
  • 2025-09JGraph Ltd legally renamed to draw.io Ltd, joint ownership with draw.io AG formalized
  • 2025-08-11draw.io publishes guide to disable default-on AI diagram generation feature
  • 2024-12draw.io reverts Apache license clause restricting Confluence/Jira use (v25.0.2)
  • 2024-08draw.io adds license clause (v24.7.8) barring open-source use inside Confluence/Jira
  • 2024-03-22Atlassian ships native Confluence Whiteboards feature
  • 2020-02Hosted web app moves from draw.io domain to app.diagrams.net citing .io TLD concerns
  • 2012Product rebranded from Diagramly to draw.io
  • 2004-08Company renamed from Pimuzar Limited to JGraph Ltd
Revision history
23 July 2026
First assessed. Losing its protection. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources