A URL for every diagram your agents draw
Where your reviewers
and agents work on diagrams.
Architecture proposals, system diagrams, migration plans – generated as HTML by Claude Code, Cursor, or your own Mermaid/D3 scripts. Published behind company SSO in 15 seconds.
The demo shows an agent publishing a doc to display.dev – from a chat or a terminal – then a teammate opening its URL, selecting Edit, changing a number on the page and saving v2, a colleague commenting on v2, the agent publishing v3 at the same URL and resolving the comment, and the doc being shared with someone outside the company.
Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.
Used by top teams at
The command
"Publish ./architecture.html to Display for everyone at my company."
Your agent publishes the proposal and returns the link, for example https://acme.dsp.so/0kzNYG7O-auth-migration-proposal.
Your VP Engineering, security lead, and the four PMs who need to review it click the link, authenticate once with their company email, and see the full interactive diagram.
Starting from a blank page? The architecture diagram template publishes in one click – no account.
Architecture proposals deserve more than a screenshot.
Claude Code, Cursor and Codex generate architecture diagrams as self-contained HTML: D3 force graphs, animated Mermaid flow charts, interactive topology maps, all in one .html file. Then they get shared as screenshots, and the diagram someone generated in 10 minutes becomes a flat image to pinch-zoom on a phone.
Click to expand, hover for detail, zoom and pan, node filtering – none of it survives any of those.
- ✗Confluencestrips the JavaScript, so the diagram arrives broken.
- ✗Notion embedpastes a flat image or a broken preview.
- ✗GitHub raw fileshows the HTML source instead of the diagram.
- ✗Google Slidesa screenshot, with every interaction gone.
Workflows by tool
- Claude Code, Cursor or Codex
- Ask the agent to publish the file to Display. The proposal keeps its native format: interactive, zoomable, annotations and decision trees intact.
- Mermaid
mmdc -i architecture.mmd -o architecture.htmlRender the Mermaid source to self-contained HTML, then publish the file.- D3, multi-file
- Ask your agent to bundle the build into one self-contained HTML file and publish it.
- Draw.io export
- Draw.io (diagrams.net) exports an interactive HTML file under File → Export → HTML.
What reviewers see
Pricing
Try it. No credit card.
- Included: 3 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Audit logs
For teams who need SSO & audit logs.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: 365 days audit logs
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays the current version at the same URL, not a one-shot screenshot.
Ask your agent to publish the file to Display, in your terminal or in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Cursor, Codex, and Claude Code all work, along with any agent that creates HTML or Markdown output. Your diagrams, versions and comments stay put when you switch agents.
Try it free
- Publish an interactive diagram in 15 seconds, no card
- Reviewers sign in with the Google or Microsoft account they already use
- Unlimited viewers on every plan
Common questions.
Does display.dev work with Mermaid diagrams exported as HTML?
Yes. mmdc -o diagram.html produces a self-contained HTML file. Your agent can publish it, and Display serves it with all interactivity.
What about draw.io / diagrams.net HTML exports?
Yes. draw.io's HTML export produces a self-contained file that renders the interactive diagram in a browser. display.dev serves it as-is.
Can I version architecture diagrams?
Yes. Publish each version with a unique name: --name arch-v1, --name arch-v2. Or keep one URL by republishing to the existing artifact with --id <shortId> --base-version <currentVersion>. Both are valid depending on whether you want separate artifacts or one version history.
Can I share specific sections with a link anchor?
If your HTML diagram uses anchor links internally (e.g., #section-3), the display.dev URL supports them: acme.dsp.so/0kzNYG7O-architecture-proposal#section-3. Viewers jump directly to the referenced section.
What file size can architecture diagrams reach?
Simple Mermaid diagrams: 100KB–1MB. Complex D3 force graphs: 1–10MB. AI-generated interactive diagrams with embedded data: 2–20MB. Smaller diagrams fit display.dev's Free tier (10MB per artifact, 50MB total storage); larger ones need Solo or Pro, which permit the platform maximum of 50MB per artifact.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).