display.dev for Dify
Dify runs the workflow. display.dev is where its output lands – at a permanent URL, behind your company login when you want it. Dify's web app can publish an app for people to use, but company SSO on those web apps is an Enterprise-only feature. For the specific HTML and Markdown a workflow produces, gated so the right people can open it without an account, display.dev is the publish step: one HTTP node, a permanent URL, gated by Google or Microsoft login on any plan.
Dify can share an app. Gating a piece of output is harder.
Dify is a strong builder for LLM workflows and agents on whichever model you choose. Its web app lets you ship a usable interface – but access control via SSO for viewers outside your workspace lives in the Enterprise commercial edition. On the open-source and standard paths, there's no company-gated way to hand a specific report or generated page to a colleague.
And because Dify runs across whatever model you configured, the teammate who needs the output has no vendor account to authenticate against either.
display.dev fills that gap on any plan: take the HTML or Markdown a workflow produces and publish it to a URL only your company can open.
From a Dify workflow to a company URL
HTTP Request node at the end of your workflow:
Method: POST
URL: https://api.display.dev/v1/publish
Header: Authorization: Bearer {DISPLAY_TOKEN}
Body (JSON):
{
"content": "{{#llm.text#}}",
"name": "workflow-report",
"org": "yourco"
}
The response contains a permanent, company-gated URL:
https://acme.dsp.so/0kzNYG7O-workflow-report
Via CLI for output written to disk:
dsp publish ./report.html --name "report-$(date +%Y-%m-%d)"Anyone with a company email opens it; everyone else is blocked.
Viewers sign in with their work email. Nothing else.
Dify is model-agnostic, so there's no single vendor behind your workflow and no account your viewers already hold. The stakeholder reading the output isn't going to have a login for whatever model ran underneath.
display.dev is vendor-independent. Viewers sign in with the Google or Microsoft email they already use for work. No display.dev account, no Dify login, nothing to install. They click and read.
The best workflow changes. The home doesn't.
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: Private artifacts
- 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: Private artifacts
- 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: Private artifacts
- 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: Private artifacts
- 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 a living document, 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 Claude Code, Cursor, Codex, or your own scripts.
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).