Registry › Compare › Dify vs Flowise

Dify vs Flowise

Dify leads on trust: 75.5/100 (Grade B) against 61.4/100 (Grade C), a 14.1-point gap. Dify leads on maintenance and rests on broader evidence; Flowise leads on supply-chain integrity and transparency.

B Dify 75.5

Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.

langgenius/dify · #269 overall · #5 Workflow Platforms · coverage A (4/5)

Choose Dify if maintenance matters most.

  • +14.7Maintenance: last push today, against 101d ago
  • A vs BEvidence coverage: 4 of 5 independent signal types, against 3
C Flowise 61.4

Build AI Agents, Visually

FlowiseAI/Flowise · #668 overall · #15 Workflow Platforms · coverage B (3/5)

Choose Flowise if supply-chain integrity and transparency matter most.

  • +1.3Safety / Integrity: OSSF Scorecard 6.0 against 5.0
  • +0.8Transparency: OSSF Scorecard 6.0 against 5.0

Where they differ

11.2
Safety / IntegrityFlowise +1.3
12.5
12.8
TransparencyFlowise +0.8
13.6
20.0
MaintenanceDify +14.7
5.3
+0.7
Runtime calibrationDify +1.5
-0.8

2 dimensions identical: Identity 10.8 · Adoption 20.0 · Full evidence table

An independent, evidence-based trust comparison of Dify and Flowise, two Workflow Platforms projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Full evidence

Signal Difylanggenius/dify FlowiseFlowiseAI/Flowise
HVTrust score 75.5 61.4
Evidence grade B C
Coverage grade A B
Overall rank #269 #668
Rank in Workflow Platforms #5 #15
GitHub stars 161.7k 55.6k
Last updated today 101d ago
Build provenance No No
OSSF Scorecard 5.0 / 10 6.0 / 10
License NOASSERTION NOASSERTION
Downloads 26.4M/wk 7.4M/wk
Trust dimensions (points earned)
Safety / integrity / 25 11.2 12.5
Identity & provenance / 18 10.8 10.8
Transparency / 17 12.8 13.6
Maintenance / 20 20.0 5.3
Adoption / 20 20.0 20.0
Runtime capability surface (full matrix)
MCP server Declared Implemented
External providers — 6 — Anthropic, Google Gemini, OpenAI, …
Requires API keys Yes No
Plugin surface plugins —
Provenance drift Partial Unknown
Open in the live compare tool → Dify profile Flowise profile More Workflow Platforms →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →