A URL for everything Llama makes
Where humans and Llama
work on dashboards together.
You run Llama. 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
Publishing Llama's output for your team to read
You chose Llama to keep data on your infrastructure, skip the per-token vendor bill, and avoid lock-in to one API. It runs on Ollama, vLLM or llama.cpp and it writes real work: analyses, dashboards, reports, internal docs. Then someone has to read it.
display.dev gives Llama's output the home that an open-weight model doesn't come with.
- ✗No share buttonopen-weight means no vendor, so there is no "share with my org" anywhere in the stack.
- ✗No account to sign intoyour teammate has no login for a model you host yourself.
- ✗Email attachmenta fresh copy every run, and no single place to look.
- ✗Slack pastethe interactivity is gone the moment it becomes text.
Three ways to publish Llama's output
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 AI account anywhere. Viewers sign in with the Google or Microsoft account they already use. Nothing to install, no model account, no display.dev account.
Change the model, keep every published URL
Today it's Llama. Next quarter you might add a Qwen fine-tune or swap a 70B for something newer. display.dev sits above the model – rotate freely, 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.
Llama and any other open-weight model – plus Cursor, Codex, Claude Code, or your own scripts.
Try it free
- Publish a file Llama wrote in under a minute, no card
- Keep the URL when you upgrade
- Unlimited viewers on every plan
Common questions.
Which Llama versions does this work with?
All of them, and any runtime. display.dev publishes any HTML or Markdown file on disk – it never sees the model. Llama 3, Llama 4, a fine-tune, served via Ollama, vLLM, or llama.cpp: if it writes a file, dsp publish works.
Do viewers need anything installed or any AI account?
No. Viewers sign in with their company Google or Microsoft email. No display.dev account, no model account, nothing to install on their side.
Does my Llama deployment leave my infrastructure?
No. Only the artifact you explicitly publish leaves. Your weights, serving stack, and data stay on your own hardware.
Can my pipeline publish automatically after inference?
Yes. Add dsp publish to the end of the script, or wire display.dev's MCP/REST API into your agent so it publishes its own output and returns the URL.
What if I switch from Llama to another 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).