Best first template
Incident response decision tree for a runbook.
draw.io/diagrams.net is a well-known diagramming option. diagram.now should not pretend otherwise. The best reason to try diagram.now is simple: you can start drawing in the browser, then move successful diagrams into an Atlassian-native Confluence workflow when the team needs them in docs.
Incident response decision tree for a runbook.
Send search visitors to the browser editor first. Ask for Marketplace install only after they know the diagram is useful.
When the diagram belongs in a spec, runbook, ADR, or process page, install diagram.now so it stays editable beside the docs.
Use the free editor for quick sketches, design reviews, process maps, and planning visuals. Keep the first CTA focused on making a diagram, not installing a paid app.
If the diagram explains a decision, runbook, product spec, process, or architecture page, the Confluence app gives teams a way to keep that visual close to the text people already maintain.
Use this page to explain fit, not to attack draw.io. Link to the existing Confluence-specific comparison for readers who are evaluating Atlassian Marketplace options.
Use the browser editor for the first draft. If the diagram becomes team documentation, install diagram.now from Atlassian Marketplace and keep it editable inside Confluence.
Yes, for users who want a browser diagram editor and a Confluence-oriented path. draw.io/diagrams.net remains a widely used diagramming product, so the comparison should focus on workflow fit.
diagram.now supports common diagram categories such as flowcharts, UML, ERD, BPMN, cloud architecture, network diagrams, mind maps, and wireframes.
No. Use this as the broader free-editor page and cross-link to the existing draw.io alternative for Confluence page for Marketplace evaluators.