Launching today
display.dev
Publish agent-generated HTML behind company auth
140 followers
Publish agent-generated HTML behind company auth
140 followers
display.dev is the easiest way to publish agent-generated artifacts behind company authentication. One command gives your HTML and Markdown files a permanent URL. Your colleagues sign in securely via OTP or Google/Microsoft SSO, and drive iteration with in-line comments.
Hey everyone!
I'm Ott, co-founder of display.dev.
A month ago @carlrannaberg came to me with a problem. In his constant use of Claude Code, his agents were building him beautiful HTML artifacts – spec sheets, interactive plans, reviews, etc. Sharing them with colleagues, however, was a mess – screenshots or PDFs to Slack, having others open HTMLs and run them on localhost – nothing good really.
The problem clicked immediately. Anyone building with agents long enough hits this wall.
So we built display.dev – one command publishes any HTML or Markdown artifact behind your company's auth. Your team signs in with Google, Microsoft or a one-time password. They see the artifact exactly as the agent built it. No static and inconvenient screenshots, no GitHub accounts, no $320/month Vercel add-ons.
Here’s what makes it actually useful day to day:
> One command, one click or your agent does it for you – CLI, web app or MCP. Publishing happens wherever you already are – your terminal, your browser or inside Claude Code/Cursor/etc. You get back a permanent URL.
> Gated by default, public when you want – Google + Microsoft SSO or OTP. Everyone at your company gets in, nobody outside does. And if you want to share something with the public, simply change the visibility setting.
> Comments your agent can read – Teammates drop inline comments. You and your agent can read them, update the artifact and resolve the thread. The thing stays alive instead of dying as a one-shot output.
> Your published artifacts are natively agent-readable – agents can pull the content as markdown from any published link, so there's no manual back-and-forth copy-pasting or importing-exporting.
> Stats and audit logs – View counts per artifact, plus audit logs of exactly who accessed what. Useful when you actually need to know if your exec opened the doc.
> Publish without an account – agents can publish unauthenticated using “curl”. The response is a public preview URL anyone can open and a single-use claim URL. Later, you can claim the URL for the organization, if you sign up or in.
> Unlimited viewers, flat price – No per-seat cliff when you share with your PM, exec and legal team on the same day. (Also, a free and a solo tier exist!).
We've been using display.dev daily ourselves – privately sharing analysis docs and ideas that Claude has built, collaborating on things fast. It's made a real difference to how we work.
Happy to answer questions – on the product, the problem and alternative solutions!
I like how this is both secure AND lightweight, a rare combination! Cool stuff!
@double_u_d thanks, Kirill!
This is a perfect utility for the current 'coding agent' era. Being able to instantly host agent-generated artifacts behind SSO is much cleaner than passing around raw HTML files. Does display.dev support custom domains for these permanent URLs, and is there an option to expire links automatically for temporary artifacts?
@rivra_dev Thanks, Rivra!
I agree that it's a much cleaner flow – so much easier to share a simple URL and collaborate within the artifact.
On your questions:
> Custom domains – we're introducing them shortly, they're planned to come out in the next few weeks. Keep an eye out on our channels or page.
> Automatic expiry – not at the moment, but currently it's as simple as telling your agent to delete it and it's done.
Once the user is logged on, can their identity be passed so that when we fetch the data, we can customize it?
PS: Please add a "Contact us" page :)
@jay_janarthanan1 Can you explain in a little more detail what you mean about passing on the identity for customization?
We'll make sure to add a contact us page - a very good point!
@ottilves When a user is authenticated, I assume the app will receive a JWT token. Let's say I have a REST fetch command in my HTML. If the token can be dynamically passed to the REST body, I can return the correct data. Basically, I want to know who is authenticated.
@ottilves @jay_janarthanan1 Can you explain what would be the use case of knowing who is authenticated? Because we have audit logs, which show all the actions the users took on the artifact, including views. Would these cover your needs?
Outfunnel
Awesome that someone finally built this!
@andruspurde Appreciate the support!