Disclosure up front: I'm affiliated with diagram.now — I'm connected to the product. I'm posting this to get developer feedback on diagram import/export interoperability, not to pitch an install.

Most teams I've worked with don't have one source of truth for their diagrams. They have:

• a few Mermaid blocks living in READMEs and Markdown docs,
• an old Visio (.vsdx) or Lucidchart file someone made two reorgs ago,
• a SQL schema that is secretly the "real" ERD,
• and a pile of screenshots pasted into docs and tickets.

The diagram is rarely the hard part. The hard part is that the same diagram lives in five formats and none of them stay in sync with the docs they're supposed to explain.

I've been working on diagram.now, a browser-based editor for technical diagrams — flowcharts, UML, ERD, BPMN, cloud/network architecture, mind maps, wireframes. It's a free browser editor with no signup to start. There's an optional Confluence app for teams that want diagrams editable inside Confluence pages, but that's intentionally not what I want to talk about here. I want feedback on the editor itself, and specifically on the interoperability story.

What it does today

• Import/insert from Mermaid and SQL — paste a Mermaid graph or a CREATE TABLE block to start an editable diagram instead of a static render.
• Import Lucidchart and Visio .vsdx files — this is migration-oriented, and honestly the part I most want real-world files to stress-test.
• Export to PNG, SVG, PDF, or a URL.
• Templates/shapes for the diagram categories above.

I'm deliberately keeping the Confluence side secondary. The thing I actually want to learn is whether the browser editor plus import/export is useful on its own.

Where I'd love feedback

1. Imports: Which format matters most to you — Mermaid, SQL→ERD, .vsdx, Lucidchart, or something else (PlantUML, draw.io XML, Graphviz)? If you've ever tried to migrate diagrams between tools, where did it break?
2. URL export: Is a shareable diagram URL genuinely useful in your workflow (issues, chat, runbooks), or do you basically always want a PNG/SVG/PDF you can drop into a doc? I want to get the privacy and editability semantics right before leaning on it, so I'm honestly unsure how much people actually want it.
3. Templates: What starter templates would make this worth keeping a tab open for? I'm considering an incident-runbook decision tree, an ADR/architecture diagram, a SaaS ERD, an AWS three-tier diagram, and an API sequence diagram — but I'd rather build what people ask for.

What I'm not going to claim

draw.io and Lucid are mature and excellent and I'm not pretending otherwise. I'm also not going to tell you it imports every .vsdx or Lucid file perfectly — diagram files vary wildly and I'd rather collect real failures than overpromise. And I'm not making any privacy or security claims about your data in this post; if you do try it, please use non-sensitive diagrams until the data-handling story is properly documented.

If you want to poke at it: https://diagram.now/

Blunt feedback very welcome — especially "this import choked on my file" or "URL export is pointless because X." That's exactly what I'm hoping to learn.