OpenDiagramEditable from the first draft
A generated diagram should begin a design conversation, not end it. Every output opens on a canvas where the structure can be reviewed and changed.
Why OpenDiagram exists
Architecture should stay open to change.
Software systems evolve after the whiteboard meeting. OpenDiagram keeps the diagram, the reasoning, and the editing surface together so architecture can evolve with the code.
The problem
System knowledge is scattered.
Screenshots, repositories, documents, and chat history each hold a different fragment. OpenDiagram brings those materials into one architecture workspace.
Screenshots
Repositories
Documents
Chat history
Connecting fragments…
Mascot unifies the pieces
One canvas · one story
What we believe
Thinking becomes useful when the team can see and change it.
Engineer judgment stays in the loop
OpenDiagram creates working drafts. Engineers still validate constraints, tradeoffs, failure modes, and the architecture that reaches production.
Open source first
The code is available under Apache 2.0. Teams can inspect it, contribute to it, and run the workspace on infrastructure they control.
- Status
- Early
- License
- Apache 2.0
- Source
- GitHub