A · leads
firecrawl
93.8
202,516 stars · AGPL-3.0
AI Agents
firecrawl leads by 7.4 · clear
A · leads
93.8
202,516 stars · AGPL-3.0
B
86.4
25,471 stars · Apache-2.0
firecrawl versus letta is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. firecrawl is written mainly in TypeScript; letta is written mainly in an unspecified language. The composite score is 93.8 for firecrawl and 86.4 for letta.
firecrawl has 202,516 GitHub stars to letta's 25,471, a gap of 177,045 (7.95×). Forks are 10,604 for firecrawl and 2,677 for letta. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 85.
Push history: firecrawl 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 810 for firecrawl (0.004 per star) and 0 for letta (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 78.
firecrawl is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. License scores in this pair are 52 for firecrawl and 96 for letta. This is a procurement signal, not legal advice.
In AI Agents, both firecrawl (202,516 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: firecrawl is open source, letta is open source.
The lead is split. firecrawl is furthest ahead on recent activity (100 to 78), while letta is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
firecrawl finishes ahead at 93.8 against letta at 86.4, a 7.4 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 | firecrawl | letta |
|---|---|---|
| GitHub stars | 202,516 | 25,471 |
| Forks | 10,604 | 2,677 |
| Open issues | 810 | 0 |
| Adoption | 100 | 83 |
| Activity | 100 | 78 |
| Community | 100 | 85 |
| Issue health | 96 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.8 | 86.4 |
Supercharge your AI agents with data from the web and beyond. Building the library for superintelligence. 🔥
Platform for stateful agents: AI with advanced memory that can learn and self-improve over time.
firecrawl has more GitHub stars: 202,516 versus 25,471 for letta. The gap is 177,045 stars.
firecrawl was pushed more recently: 17 November 2026 versus 18 October 2026 for letta. That is 29 days apart.
Yes. This catalog marks both firecrawl and letta as self-hostable. Confirm each project's deploy docs before you plan a migration.
firecrawl is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.
firecrawl scores 93.8 and letta scores 86.4. This page calls that a clear lead for firecrawl.