A URL for everything your vLLM stack makes
Where humans and your vLLM stack
work on dashboards together.
vLLM serves the model on your GPUs. display.dev is where its output lands – one command, a URL that never changes, gated by your company's Google or Microsoft login.
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
Where vLLM job output goes after the run
You stood up vLLM for the throughput, the OpenAI-compatible endpoint, and models running on GPUs you control. That stack ends at the completion. A batch job writes a report, a dashboard or a research brief, and vLLM's work is done.
display.dev is the publish layer that vLLM doesn't include, and isn't trying to.
- ✗A file on a workernobody outside the cluster can reach it.
- ✗No account to sign intothere is no vendor in the loop, so the colleague who needs it has no login anywhere.
- ✗Infrastructure accessthe alternative is handing out credentials to read one report.
Three ways to publish vLLM output
index.html at the root URL and resolves every relative asset path.Who can open it
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 infrastructure access needed. Viewers sign in with the Google or Microsoft account they already use. No cluster credentials, no model account, no display.dev account.
Change the model, keep every published URL
You'll swap the model behind your vLLM endpoint as the open-weight field moves. display.dev sits above the serving layer – change the served model, the engine, even the whole stack, and everything you published keeps its URL, versions, and comment threads.
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 MCP tool call. 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.
Whatever vLLM is serving – plus Cursor, Codex, Claude Code, or your own scripts.
Try it free
- Publish a job's output in under a minute, no card
- Keep the URL when you upgrade
- Unlimited viewers on every plan
Common questions.
Does this expose my vLLM endpoint?
No. display.dev hosts only the file you explicitly publish. Your vLLM server, GPUs, and weights stay entirely on your own infrastructure. You're publishing the output, not the endpoint.
Do viewers need access to my infrastructure or an AI account?
No. Viewers sign in with their company Google or Microsoft email. No infrastructure access, no model account, no display.dev account on their side.
Can a batch job publish automatically?
Yes. Add dsp publish at the end of the job, or call display.dev's MCP/REST API from the job so it publishes its own output and returns the URL.
Can I publish a multi-file output directory?
Yes. dsp publish ./output/ serves index.html at the root URL and resolves all relative asset paths.
What happens when I change the served model?
Nothing moves. display.dev is independent of what produced the output, so every URL, version, and comment thread stays put.
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).