Skip to content
DevUtils Online

AI Agents

Dify vs vibe-kanban

Dify leads by 7.8 · clear

A · leads

Dify

97.9

161,357 stars · Apache-2.0

Dify versus vibe-kanban is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Dify is written mainly in Python; vibe-kanban is written mainly in Rust. The composite score is 97.9 for Dify and 90.1 for vibe-kanban.

Dify has 161,357 GitHub stars to vibe-kanban's 28,719, a gap of 132,638 (5.62×). Forks are 25,515 for Dify and 3,064 for vibe-kanban. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 79.

Push history: Dify was last pushed on 17 November 2026 (0 days ago), and vibe-kanban was last pushed on 15 November 2026 (2 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 534 for vibe-kanban (0.019 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both Dify and vibe-kanban are listed as Apache-2.0. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In AI Agents, both Dify (161,357 stars) and vibe-kanban (28,719 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Dify is open source, vibe-kanban is open source.

Dify is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 21 points (100 vs 79), and the tightest is self-hosting at 0 points (100 vs 100).

Dify finishes ahead at 97.9 against vibe-kanban at 90.1, a 7.8 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Dify versus vibe-kanban metrics
Signal Dify vibe-kanban
GitHub stars 161,357 28,719
Forks 25,515 3,064
Open issues 1,422 534
Adoption 100 86
Activity 100 100
Community 100 79
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 97.9 90.1

Dify

Dify is a platform for building LLM apps: prompts, RAG pipelines, agents, and observability. It is aimed at teams that want that stack on their own machines.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Dify or vibe-kanban?

Dify has more GitHub stars: 161,357 versus 28,719 for vibe-kanban. The gap is 132,638 stars.

Which was updated more recently, Dify or vibe-kanban?

Dify was pushed more recently: 17 November 2026 versus 15 November 2026 for vibe-kanban. That is 2 days apart.

Can I self-host both Dify and vibe-kanban?

Yes. This catalog marks both Dify and vibe-kanban as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Dify or vibe-kanban?

Dify is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. vibe-kanban is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the Dify vs vibe-kanban score?

Dify scores 97.9 and vibe-kanban scores 90.1. This page calls that a clear lead for Dify.

Related comparisons