A URL for everything v0 makes
Where humans and v0
work on prototypes together.
v0 generates the UI. display.dev is where your stakeholders review it – behind company SSO, with no Vercel account for viewers and no per-seat fees.
The demo shows an agent publishing a doc to display.dev – from a chat or a terminal – then the team opening its URL, commenting, the agent publishing v2 at the same URL, 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.
Indigo Engineering
Getting v0 output in front of non-technical stakeholders
v0 by Vercel generates polished React component previews and HTML exports. The output is visually excellent and technically complete. Getting stakeholders to review it is a different problem.
display.dev publishes the v0 export behind your company's Google or Microsoft SSO. Any stakeholder with a company email reviews it in the browser, interactively.
- ✗Share the v0 linkneeds a v0 or Vercel login. Your PM, design lead, and CEO have no Vercel account.
- ✗Export and deploy to Vercelneeds a Vercel project, and SSO sits behind the enterprise tier. The free tier is public-only.
- ✗Screenshotthe interactivity that makes v0 output valuable is gone.
- ✗Loom walkthroughasync, with no hands-on exploration for the reviewer.
Three ways to publish a v0 export
Who can open the prototype
A public URL, no sign-in. Free covers unlimited public links.
Named email addresses only. Useful for a client or a contractor you don't want to hand company sign-in to.
Anyone signing in with a verified company domain gets in – Google Workspace, Microsoft Entra ID, or a one-time password by email. Viewers are unlimited on every plan.
No Vercel account anywhere. Stakeholders sign in with the Google or Microsoft account they already use, then interact with the UI. No React setup on their side.
The Vercel account gap
- Every reviewer needs a Vercel account
- v0 is a Vercel product, and sharing a preview natively means a Vercel login. Most product, business, and executive stakeholders don't have one.
- Vercel SSO is enterprise-tier
- One project, gated behind the enterprise plan. It doesn't scale to a team sharing several v0 prototypes.
- Public preview URLs skip auth entirely
- No company gate, so internal designs sit on the open web.
- display.dev is the publish step instead
- Company-restricted, interactive, at a URL that never changes – and no Vercel account for anyone reviewing.
v0 artifact sharing compared
| Option | Non-Vercel viewers | Company auth | Interactivity | Cost |
|---|---|---|---|---|
| v0 native share | ❌ (Vercel login) | ❌ | ✅ | $0 |
| Deploy to Vercel + SSO | ❌ | ✅ | ✅ | Enterprise tier |
| Screenshot | ✅ (degraded) | – | ❌ | $0 |
| display.dev | ✅ | ✅ | ✅ | €49/mo flat |
Pricing
Try it. No credit card.
- Included: 10 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 that need company auth.
- 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.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets its own 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 other agent that creates HTML or Markdown output.
Try it free
- Publish a v0 prototype in under a minute, no card
- Keep the URL when you upgrade
- Unlimited viewers on every plan
Common questions.
Does display.dev require a Vercel account?
No. display.dev is independent of Vercel. Viewers authenticate with their company Google or Microsoft email.
What format do I export from v0?
v0's HTML export produces a self-contained HTML file. dsp publish ./export.html publishes it. For multi-file exports, dsp publish ./export-dir/ publishes the directory.
Can I keep v0 for iteration and use display.dev just for stakeholder sharing?
Yes. Iterate in v0, export when you want stakeholder review, publish with dsp publish. display.dev is the last step in the workflow, not a replacement for v0.
What if my v0 export has React/Next.js dependencies?
v0's HTML export is designed to be self-contained. For complex React builds that aren't self-contained, you'd need to build to static HTML first (next export or equivalent) before publishing with display.dev.
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).