Introducing diagram.now: inline flowcharts, UML, BPMN, ERD, and mind maps in Confluence Cloud

[#1]

Hi Atlassian Community

How many architecture diagrams, process maps, and database models in your Confluence spaces are already out of date?

The page keeps getting updated, but the diagram often falls out of sync because it lives somewhere else: another tab, another tool, another file, or someone’s personal workspace.

That is the problem we built  diagram.now to solve: a Forge-native inline diagram editor for Confluence Cloud, now available on Atlassian Marketplace.

The idea is simple: if the documentation lives in Confluence, the diagram should be created and edited there too.



What you can diagram

diagram.now includes 1,000+ shapes across 20+ diagram types, including:

- Flowcharts and decision trees
- UML and BPMN process diagrams
- ERD / database models
- Mind maps and planning visuals
- AWS, Azure, and GCP cloud architecture diagrams
- Web and mobile wireframes
- Network, rack, and infrastructure diagrams

Already have diagrams elsewhere?

diagram.now supports importing from Gliffy, Lucidchart, Visio (.vsdx), and Mermaid, plus CSV and SQL. You can also export diagrams as PNG, SVG, JPEG, or PDF when you need to share them outside Confluence.

Why we built it

Confluence is already where many teams document systems, decisions, processes, onboarding guides, and product plans. But when the visual part of that documentation lives outside Confluence, the same problems tend to repeat:

- The written page gets updated, but the diagram does not.
- Teammates hesitate to edit diagrams because they do not know where the source file lives.
- Readers lose trust in the page when the picture no longer matches reality.

We wanted diagramming to stay closer to the pages where teams already collaborate, review, and maintain documentation.

What diagram.now helps with

- Inline editing: Create and edit diagrams directly inside Confluence pages.
- Broad diagram coverage: Use one app for flowcharts, UML, BPMN, ERD, mind maps, cloud diagrams, wireframes, and more.
- Confluence-native workflow: Keep visual documentation attached to the pages where teams already work.
- Forge-native foundation: Built on Atlassian Forge for Confluence Cloud teams that prefer Atlassian-native app workflows.
- Admin-friendly install: Install through Atlassian Marketplace and manage it as part of your Confluence Cloud app stack.

Five practical ways teams can use it

1. Architecture decision records — add a current-state or proposed-state diagram inside an ADR page, then update it as the decision evolves.
2. Incident and support runbooks — create flowcharts for escalation paths, triage decisions, rollback steps, or “what to check next” support workflows.
3. Product and engineering planning — use mind maps, wireframes, and process flows next to requirements and discovery notes.
4. Database and domain modeling — add ERDs or UML class diagrams alongside technical specs.
5. Cloud infrastructure documentation — document AWS, Azure, or GCP architectures on Confluence pages used for onboarding, security reviews, and migration planning.

Try it

If your team uses Confluence as the source of truth for technical or process documentation, you can try diagram.now on Atlassian Marketplace:

https://marketplace.atlassian.com/apps/523472243/diagram-now-flowchart-uml-bpmn-erd-mind-map

Feedback welcome

I would especially love feedback from Confluence admins, documentation owners, software architects, and power users:

- What kinds of diagrams do your teams struggle to keep current?
- What would make a Confluence diagramming app easier to evaluate?
- Which templates or starter diagrams would save your team time?

Happy to answer questions in the comments, and I would genuinely appreciate feedback from the community.


Thanks!

Artem