Evaluation map
A defined inputBranching workflowReviewable output

Make the workflow inspectable

HomeDify in Japan: moving from experiments to enterprise workflows

Case studies

Dify in Japan: moving from experiments to enterprise workflows

A public customer story connects workflow building with company-wide adoption and governance.

Vendor-published customer case

Japan · Dify / Kakaku.com

What the source documents

Dify’s published Kakaku.com story describes adopting Dify Enterprise to organize AI application development. Its GitHub repository provides workflow, retrieval and self-hosting documentation. The story is a vendor account, not an independent audit.

What this means for your project

The useful buying question is how a workflow becomes usable by a team: who owns it, who can access data, and how errors are escalated. CNPS suggests starting with one document or support workflow and an agreed evaluation set.

What to confirm

This is not a CNPS delivery. Reported adoption does not establish the result of a new customer project. Dify licensing includes additional conditions for multi-tenant use and frontend branding.

What to evaluate

  • Use authorized documents and a fixed question set.
  • Measure citation correctness and human correction time.
  • Test permissions and refusal on missing evidence.

Evidence & sources

Let’s start with your real-world challenge.

Tell us what you need to improve, where you work and when you want to begin.

Start a conversation