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.
dsp publish ./architecture.html --name "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.
Claude Code, Cursor, and Windsurf generate architecture diagrams as self-contained HTML files. D3 force graphs, animated Mermaid flow charts, interactive system topology maps — all living in a single .html file.
Then they get shared as screenshots.
The interactive elements — click to expand, hover for details, zoom and pan, node filtering — are gone. The diagram that took 10 minutes to generate becomes a flat image that someone has to zoom into on their phone.
The other options aren't better:
AI coding tools generate architecture proposals as rich HTML artifacts by default:
dsp publish ./architecture-proposal.html --name "q2-auth-migration"The architecture proposal stays in its natural format: interactive, zoomable, with annotations and decision trees intact. Your entire review committee — engineers, PMs, and leadership — clicks one link and sees what Claude built.
From Claude Code / Cursor / Windsurf:
dsp publish ./output.html --name "migration-plan-v2"Mermaid diagrams:
mmdc -i architecture.mmd -o architecture.html
dsp publish ./architecture.html --name "system-architecture"D3 multi-file diagram:
npm run build
dsp publish ./dist/ --name "network-topology"Draw.io HTML export: Draw.io (diagrams.net) exports diagrams as interactive HTML. File → Export → HTML.
dsp publish ./diagram.html --name "data-flow-diagram"A VP Engineering, security lead, and three PMs receive the URL in a Slack thread or Linear comment.
They click it. They authenticate with their company Google or Microsoft account — once. They see the full interactive architecture diagram:
Every interactive element the diagram was built with. No Lucidchart account. No Miro license. No Confluence markup rendering issues.
Free — one-time password auth, 50MB, unlimited viewers
Teams ($49/month) — Google + Microsoft SSO, 25GB, custom domain, unlimited viewers
Publish your first architecture diagram free →
Yes. mmdc -o diagram.html produces a self-contained HTML file. dsp publish ./diagram.html serves it with all interactivity.
Yes. draw.io's HTML export produces a self-contained file that renders the interactive diagram in a browser. Display serves it as-is.
Yes. Publish each version with a unique name: --name arch-v1, --name arch-v2. Or use the same name to overwrite (same URL, updated content). Both are valid depending on whether you want to preserve the history.
If your HTML diagram uses anchor links internally (e.g., #section-3), the Display URL supports them: yourco.display.dev/architecture-proposal#section-3. Viewers jump directly to the referenced section.
Simple Mermaid diagrams: 100KB–1MB. Complex D3 force graphs: 1–10MB. AI-generated interactive diagrams with embedded data: 2–20MB. All within Display's free tier (50MB artifact limit).
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).