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.
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!
What got me was the MCP part, it means the agent handles the publish step itself from inside the chat, so there's no jumping between tools or touching a hosting config. The fact that users just sign in with their existing Google or Microsoft account without creating anything new is a genuinely so impressive. I also loved the fact that the url is not like public url which is what happens when you publish through claude code, so that security and authentication is maintained through and through. Curious how the comment-to-agent feedback loop works in practice, does the agent pick up all comments automatically or do you have to trigger it manually?
I'm curious about how display.dev handles authentication for different enterprise setups. Is it using OAuth, SAML, or something else? Auth integration is often trickier than it first appears, especially with legacy systems in the mix.
The screenshot-or-PDF-to-Slack pain point is the right thing to fix — agent-generated artifacts only feel like artifacts when they have a stable URL someone can come back to. The SSO/OTP gate is doing two jobs at once: keep strangers out, and (more subtly) tell the agent which audience it's writing for, which I think is underrated.
I hit a related shape building PolyMind, a small alert tool that watches Polymarket and pings me when a position shifts in a market I care about. The artifact problem there is the same: an alert is only useful if it lives somewhere it can be revisited and annotated by the trader after the fact — a one-shot Slack ping is essentially fire-and-forget. Curious whether display.dev's comment layer is intended to drive iteration on the artifact itself, or whether it's more of an asynchronous review channel for humans to triangulate around what the agent produced.
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 :)
I like how this is both secure AND lightweight, a rare combination! Cool stuff!
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?
About display.dev on Product Hunt
“Publish agent-generated HTML behind company auth”
display.dev launched on Product Hunt on May 12th, 2026 and earned 167 upvotes and 17 comments, placing #5 on the daily leaderboard. 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.
display.dev was featured in SaaS (41.9k followers), Developer Tools (512.2k followers) and Artificial Intelligence (468.1k followers) on Product Hunt. Together, these topics include over 203.2k products, making this a competitive space to launch in.
Who hunted display.dev?
display.dev was hunted by Ott Ilves. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how display.dev stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Ott Ilves
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!