A
leon
94.5
17,690 stars · MIT
Workflow Automation
sim leads by 3.4 · narrow
A
94.5
17,690 stars · MIT
B · leads
97.9
30,151 stars · Apache-2.0
leon versus sim is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 94.5 for leon and 97.9 for sim.
sim has 30,151 GitHub stars to leon's 17,690, a gap of 12,461 (1.70×). Forks are 1,484 for leon and 3,915 for sim. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 88 versus 100.
Push history: leon was last pushed on 17 November 2026 (0 days ago), and sim was last pushed on 17 November 2026 (0 days ago). Open issues stand at 118 for leon (0.007 per star) and 330 for sim (0.011 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
leon 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. sim 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 96 for leon and 96 for sim. This is a procurement signal, not legal advice.
In Workflow Automation, both leon (17,690 stars) and sim (30,151 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: leon is open source, sim is open source.
sim 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 12 points (88 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
sim finishes ahead at 97.9 against leon at 94.5, a 3.4 point narrow 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 | leon | sim |
|---|---|---|
| GitHub stars | 17,690 | 30,151 |
| Forks | 1,484 | 3,915 |
| Open issues | 118 | 330 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.5 | 97.9 |
🧠 Leon is your open-source personal assistant.
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
sim has more GitHub stars: 30,151 versus 17,690 for leon. The gap is 12,461 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both leon and sim as self-hostable. Confirm each project's deploy docs before you plan a migration.
leon 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. sim 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.
sim scores 97.9 and leon scores 94.5. This page calls that a narrow lead for sim.