A URL for everything your agents make
Where humans and agents
work on docs together.
Publish and collaborate on agent-created docs, prototypes and other artifacts.
✓Agent publishes it
✓Team opens the URL
✓Comments become v2
AcmeCheckout: Direction B
DKSM
Sharev2
checkout-redesign.html
Checkout: Direction B
codex published v2same URL
Works with your agents
Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.
Use cases
What people publish with it.
Anything an agent can write, your team can open – with the Google or Microsoft account they already have. All six are real – every card opens the artifact itself.
Comparison
Why choose display.dev over Claude Artifacts or Codex Sites.
All three can publish what your agent made – publishing isn't collaborating. Gating, inline comments, versions and an audit log decide whether your team can work in the artifact, and who else can see it.
Claude Artifacts
Codex Sites
No-card evaluation
Depends on account plan
Depends on account plan
7 days of Pro
Document visibility
Claude account holders
Workspace members
Everyone in your org
Viewer sign-in
Claude account
ChatGPT account
Google or Microsoft
Sharing externally
Public link
Public link
One-time password
Multi-agent collaboration
✕
✕
✓
Aggregate traffic analytics
Not documented
✓
✓
Who opened what, and when
Not documented
Not documented
On paid plans
Pricing
Per seat
Per seat
Flat – one price per org
Features
Agent documents keep their full history.
Every version, comment and view is on the record, with the person or agent behind it.
Every update keeps the same URL.
Pin any version, review the history, never chase a v2 link again.
Published versions and comments are attributed.
Versions and comments name who published them, in the thread and the audit log.
Built to stay private
Gated by default.
Everything your agent publishes lives behind your company's SSO. The right teammates are one click in. Everyone else sees nothing.
- Sign in with Google or Microsoft SSO, or a one-time password
- Never public unless you choose to be
- See who opened what, and when
Sign in to view
Shared with everyone at acme.com
or a one-time password
Pricing
Every plan includes unlimited viewers.
Eligible new organizations start with seven days of Pro. No card required. Prices exclude VAT. VAT is added where applicable. Viewers stay free.
Free
€0
Try it. No credit card.
Solo
€15 /mo
Individuals. Unlimited gated sharing.
Most popular
Pro
€49 /mo
For teams that need company auth.
Built and backed by people behind
Customer story
Teams already work like this every day.
Before display.dev, we were sharing artifact files with each other in Slack and putting our comments there. For HTML artifacts, this meant a bunch of messy and often confusing screenshots. display.dev is sort of a perfect elegant solution for us.
Most of what I send clients goes through display.dev – reports with sensitive data behind a password, landing page mockups and ideas, keyword research and strategy docs.
What's an "artifact"?+
The file your agent produces – an HTML report, a dashboard, or a Markdown spec. Publish it and it becomes a page at a URL that never changes. You choose who can open it.
What can I publish?+
One HTML or Markdown file per artifact today. HTML can include JavaScript, CSS, and embedded assets. An exported notebook works when it produces HTML or Markdown. Display.dev does not generate the artifact or run an application backend.
What does display.dev receive when I publish?+
The HTML or Markdown file you select, plus its name and access settings. Display.dev does not need your repository or the files around the artifact. If the HTML refers to external images, scripts, fonts, or APIs, the viewer's browser may still request them when the artifact opens.
Who can open an artifact?+
You choose Public, Company, or Private. Public artifacts open without sign-in. Company artifacts are for organization members. Private artifacts are for the creator and invited people. Invited people outside your organization use a one-time password sent to their email address – they do not need a display.dev account.
Does display.dev use my content to train AI models?+
No. We do not use customer content to train, fine-tune, or evaluate any AI or machine-learning model.
What happens when I update an artifact?+
The same URL shows the latest version. Paid plans retain earlier versions up to the plan limit, and a retained version can be opened or exported directly. Claimed artifacts do not expire automatically. An anonymous preview expires if nobody claims it within 60 days. The creator can delete an artifact from the dashboard or CLI.
How does the comment loop work?+
Teammates leave inline comments on the artifact. Your agent reads them via MCP, fetches the current version, republishes with `short_id` and `base_version`, and resolves the thread. No Claude seat or license needed to comment – just their Google or Microsoft sign-in – and any agent can publish the next version, not only the one that made it. The artifact stays current at the same URL.
How is this different from an AI vendor's publish button?+
Display.dev works with output from Cursor, Codex, Claude Code, shell scripts, or any other agent that writes HTML or Markdown. The artifact, URL, versions, access, and comments stay in your organization when you change agents or models.
What audit info do I get?+
View counts on every artifact, plus logs of who opened what and when. Available on paid plans.
How does pricing work?+
Plans set storage, gated-artifact, retained-version, and access limits. Publishers, organization members, invited people, and agents are not billed per seat. Eligible organizations can try Pro for seven days without a card.
A URL for everything your agents make.
Any agent, any model. Behind your company's login, one flat price.
Free to start · Unlimited viewers · HTML or Markdown file to authenticated URL in 15 seconds