A URL for everything your Dify workflows make
Where humans and your Dify workflows
work on reports together.
Dify runs the workflow. display.dev is where its output lands – at a URL that never changes, behind Google or Microsoft login on any plan. One HTTP node at the end of the run, and the specific report or generated page is gated for the people who need it.
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
Gating a single Dify output behind company login
Dify is a strong builder for LLM workflows and agents on whichever model you choose, and its web app lets you publish a usable interface. But access control via SSO for viewers outside your workspace lives in the Enterprise commercial edition, and Dify runs across whatever model you configured, so the teammate who needs the output has no vendor account to authenticate against either.
display.dev fills the gap on any plan: take the HTML or Markdown a workflow produces and publish it to a URL only your company can open.
- ✗Dify's web app on open source or standardPublishes an app, but no company gate for outside viewers.
- ✗A public linkHands an internal report to the open web.
- ✗An email attachmentA fresh copy every run and no URL to bookmark.
- ✗A screenshotLoses whatever the workflow rendered.
Two ways to publish from Dify
Who can open it
A public URL when the workflow'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, on any plan.
No vendor account, ever. The stakeholder reading the output 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 workflow, keep every published URL
You'll rework Dify apps and swap the model behind them as the field moves. display.dev sits above all of it. Change the workflow 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
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 HTTP Request node, or dsp publish ./file.html from a terminal. 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.
Dify, plus Cursor, Codex, Claude Code, or your own scripts.
Get started free
- Add the publish node to a workflow in minutes, no card
- Keep the URL when you rebuild the workflow
- Unlimited viewers on every plan
Common questions.
How do I publish from Dify?
Add an HTTP Request node that POSTs your workflow output to display.dev's REST API and returns a URL. It works on any Dify plan, including self-hosted.
Doesn't Dify already let me publish a web app?
It does, but company SSO for viewers outside your workspace is an Enterprise feature. display.dev gates published output by company login on any plan, and is scoped to a specific artifact rather than a whole app.
Do viewers need a Dify or model-vendor account?
No. Viewers sign in with their company Google or Microsoft email. No display.dev account, no Dify login, no model-vendor account.
Can I update the same report each run?
Yes. Pass the artifact's short_id and current base_version in the POST body. The URL stays the same; the report updates in place.
What if I rebuild the workflow later?
Nothing moves. display.dev is independent of the workflow, 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).