The tools don't match the way architects think.
"There is a missing tool: visual-first, semantically aware, built specifically for the way software architects think."
Architecture diagrams should be visual, semantic, versioned, close to Pages, and readable by agents.
Ideagram is not just a place to draw boxes and arrows. It is a software architecture workspace where diagrams, notes, exports, and automation share the same source of truth.
Infinite canvas. Semantic diagram model. Mermaid panel. Side by side.
Start a project. Watch it become an architecture.
Model the idea, get a diagram, record the decision, leave a note — the same loop, every time, whether you're clicking around Ideagram or typing into an agent. The MCP server isn't a read-only API bolted on after the fact: it's the same creation path the in-app editor uses, open to your CLI, your IDE, or any agent that speaks MCP.
Everything software architects need in one canvas.
Not a generic whiteboard. Ideagram is built around semantic architecture diagrams, Pages, Mermaid, collaboration, and MCP automation.
UML, C4, and flowcharts
Create software architecture diagrams with diagram-aware nodes, relationships, and visual conventions for UML, C4, sequence, and flowchart views.
Nested diagrams
Double-click any container to drill into it. Navigate system hierarchy with breadcrumbs while each level keeps its own components and connections.
Mermaid to Ideagram
Paste Mermaid and render it as a polished Ideagram view instead of a raw Mermaid diagram. Keep code as the editing surface when text is the right workflow.
Portable read-only viewer
Embed Ideagram-style diagrams in other apps without taking the full editor. The viewer focuses on rendering Mermaid and RenderGraph with a consistent visual language.
MCP server
Model, diagram, and document a project from a CLI, Cursor, Claude Code, or any MCP agent — the same create-and-document loop as the in-app editor, live at ideagram.dev/mcp.
Version history
Track diagram evolution over time. Browse previous snapshots, compare architectural changes, and restore earlier states when needed.
Real-time collaboration
See teammates' cursors live, collaborate without overwrites, and use locks when someone is actively editing a diagram.
Workspace hierarchy
Organize work by Organization, Workspace, Project, and Diagram so architecture maps to how teams actually manage systems.
DSL code editor
Use the Monaco-powered editor to work with diagrams as structured text, with syntax highlighting, autocomplete, and read-only visual preview.
Permissions and roles
Control access with owner, admin, editor, and viewer roles across organizations, workspaces, and projects.
Pages beside diagrams
Keep ADRs, runbooks, onboarding notes, and project context in Pages right beside the diagrams they explain.
Open source release, coming soon.
We are preparing the public release. Until then, the hosted alpha is the place to explore Ideagram and share feedback with the team.
Pages keep architecture context with the diagrams.
Pages gives every project a Confluence-style workspace for folders, markdown pages, and notes living right next to the diagrams they describe. Write the why where the what already lives.
Pages live next to the diagrams
Folders, pages, and notes are scoped to the same project as your architecture, instead of living in a separate wiki that drifts out of sync.
Markdown, not a proprietary format
Every page is plain markdown. Write ADRs, runbooks, onboarding notes, and design rationale the way your team already writes docs.
Embed and link back to diagrams
Reference a diagram directly from a page, and see which pages reference a diagram from the canvas side.
AI assistance grounded in architecture data.
Ask Ideagram to generate component scaffolding, explain layer relationships, or export your canvas to Mermaid syntax. AI workflows should operate through the same structured diagram data exposed by MCP, not through screenshots or disconnected prompts.
Your diagrams. Your infrastructure.
Ideagram runs on your own Supabase instance. Your data never passes through our servers; it lives in your Postgres, under your RLS policies, in your region.
If Ideagram shuts down tomorrow, your stack keeps running. Export to Mermaid, migrate to any tool that speaks plain text. No hostage-ware.
Contact
Let’s talk about Ideagram.
Questions, feedback, or an idea to share? Send us a note and we’ll get back to you.