A URL for everything your crew makes
Where humans and your crew
work on reports together.
Your crew does the work. display.dev is where its output lands – at a URL that never changes, behind your company login when you want it. CrewAI coordinates role-playing agents across whatever model you choose; display.dev is the hosted place to put the HTML and Markdown they produce.
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
A crew can produce the report but can't host it
CrewAI is built around autonomous crews: one agent researches, another writes, another fact-checks, another formats and "publishes" the result. The pattern works right up to the last word, because publishing usually means writing a file nobody outside the run can open. And the crew runs across whatever model you pointed it at, so the colleague who needs the report has no vendor account either.
display.dev makes "publish" a real last step the crew can take: a URL your team can click.
- ✗A Markdown fileLands on a worker, not in front of a reader.
- ✗An S3 bucketNobody reads it without credentials someone has to hand out.
- ✗An email attachmentA new copy every run, and no URL to bookmark.
- ✗A public linkThe only zero-friction option, and wrong for internal work.
Three ways to publish from a crew
Who can open it
A public URL when the crew's output isn't sensitive. Nothing to sign in to.
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 and free.
No vendor account, ever. The exec reading the crew's report has no login for the model that ran underneath, and doesn't need one. They sign in with the Google or Microsoft email they already use for work.
Change the crew, keep every published URL
You'll re-tune crews, swap models, and rewrite agents as the field moves. display.dev sits above all of it. Change the crew however you like; 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
No per-API-call charges. No per-publish charges. No per-viewer charges. Flat.
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.
One MCP tool call, one REST request, or dsp publish ./file.html. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a 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.
CrewAI and any agent that can make an HTTP request or call an MCP tool.
Get started free
- Add the publish tool to a crew in minutes, no card
- Keep the URL when you rebuild the crew
- Unlimited viewers on every plan
Common questions.
How do I add display.dev to a crew?
Wrap the publish call as a custom CrewAI tool with display.dev's REST API, or use MCP. The formatting/publishing agent calls it as its final step and returns the URL.
Do viewers need a CrewAI or model-vendor account?
No. Viewers sign in with their company Google or Microsoft email. No display.dev account, no CrewAI login, no model-vendor account.
Can the crew publish without a human in the loop?
Yes. Publishing is just a tool call. The crew runs it autonomously and the URL appears in its output.
Can a scheduled crew update the same URL each run?
Yes. Publish with the artifact's short_id and current base_version. The URL stays the same; bookmarked links show the latest version.
What if I rebuild the crew or switch models?
Nothing moves. display.dev is independent of the framework and model, so everything you published keeps its URL, versions, and comment threads.
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).