dify

langgenius/dify

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.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
12 Nov 2026
today
Ship score
96/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 157,434 → 160,789 (29 Sep – 10 Nov 2026)
+2,497 stars in the 28 days to 10 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
161K
Forks
25.5K
Open issues
1.2K
Watchers
836
Primary language
Python
License
Other
Created
12 Apr 2023
Owner
langgenius · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 112 startups in the directory ship primarily in Python.

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 100%, self-hostable 91%, hosted offering 82%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 12 Nov 2026This is the badge for langgenius/dify, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/langgenius/dify.svg)](https://ossean.com/langgenius/dify)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.