A · leads
Dify
97.9
161,357 stars · Apache-2.0
AI Agents
Dify leads by 12.0 · clear
A · leads
97.9
161,357 stars · Apache-2.0
B
85.9
25,471 stars · Apache-2.0
Dify versus letta 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; letta is written mainly in an unspecified language. The composite score is 97.9 for Dify and 85.9 for letta.
Dify has 161,357 GitHub stars to letta's 25,471, a gap of 135,886 (6.33×). Forks are 25,515 for Dify and 2,677 for letta. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 78.
Push history: Dify was last pushed on 17 November 2026 (0 days ago), and letta was last pushed on 18 October 2026 (29 days ago). Open issues stand at 1,422 for Dify (0.009 per star) and 0 for letta (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 78.
Both Dify and letta 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 letta (25,471 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, letta is open source.
The lead is split. Dify is furthest ahead on fork community (100 to 78), while letta is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Dify finishes ahead at 97.9 against letta at 85.9, a 12.0 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Dify | letta |
|---|---|---|
| GitHub stars | 161,357 | 25,471 |
| Forks | 25,515 | 2,677 |
| Open issues | 1,422 | 0 |
| Adoption | 100 | 85 |
| Activity | 100 | 78 |
| Community | 100 | 78 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 85.9 |
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.
Platform for stateful agents: AI with advanced memory that can learn and self-improve over time.
Dify has more GitHub stars: 161,357 versus 25,471 for letta. The gap is 135,886 stars.
Dify was pushed more recently: 17 November 2026 versus 18 October 2026 for letta. That is 29 days apart.
Yes. This catalog marks both Dify and letta as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. letta 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.
Dify scores 97.9 and letta scores 85.9. This page calls that a clear lead for Dify.