Skip to content
DevUtils Online

AI Agents

Dify vs text-to-cad

Dify leads by 7.1 · clear

A · leads

Dify

97.9

161,357 stars · Apache-2.0

Dify versus text-to-cad is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.9 for Dify and 90.8 for text-to-cad.

Dify has 161,357 GitHub stars to text-to-cad's 26,630, a gap of 134,727 (6.06×). Forks are 25,515 for Dify and 2,537 for text-to-cad. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 77.

Push history: Dify was last pushed on 17 November 2026 (0 days ago), and text-to-cad was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 46 for text-to-cad (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

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. text-to-cad is listed as MIT, 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. License scores in this pair are 96 for Dify and 96 for text-to-cad. This is a procurement signal, not legal advice.

In AI Agents, both Dify (161,357 stars) and text-to-cad (26,630 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, text-to-cad is open source.

The lead is split. Dify is furthest ahead on fork community (100 to 77), while text-to-cad is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.

Dify finishes ahead at 97.9 against text-to-cad at 90.8, a 7.1 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 text-to-cad metrics
Signal Dify text-to-cad
GitHub stars 161,357 26,630
Forks 25,515 2,537
Open issues 1,422 46
Adoption 100 85
Activity 100 100
Community 100 77
Issue health 84 96
License 96 96
Self-hosting 100 100
Composite 97.9 90.8

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 text-to-cad?

Dify has more GitHub stars: 161,357 versus 26,630 for text-to-cad. The gap is 134,727 stars.

Which was updated more recently, Dify or text-to-cad?

Both were last pushed on 17 November 2026.

Can I self-host both Dify and text-to-cad?

Yes. This catalog marks both Dify and text-to-cad 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 text-to-cad?

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. text-to-cad is listed as MIT, 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 text-to-cad score?

Dify scores 97.9 and text-to-cad scores 90.8. This page calls that a clear lead for Dify.

Related comparisons