A · level
leon
94.7
17,690 stars · MIT
Workflow Automation
Too close to call · 94.7 to 95.3
A · level
94.7
17,690 stars · MIT
B · level
95.3
24,995 stars · GPL-3.0
leon versus Tasmota is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. leon is written mainly in TypeScript; Tasmota is written mainly in C. The composite score is 94.7 for leon and 95.3 for Tasmota.
Tasmota has 24,995 GitHub stars to leon's 17,690, a gap of 7,305 (1.41×). Forks are 1,484 for leon and 5,216 for Tasmota. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 85 versus 100.
Push history: leon was last pushed on 17 November 2026 (0 days ago), and Tasmota was last pushed on 17 November 2026 (0 days ago). Open issues stand at 118 for leon (0.007 per star) and 12 for Tasmota (0.000 per star). Issue-health scores are 84 and 96; 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. Tasmota is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for leon and 64 for Tasmota. This is a procurement signal, not legal advice.
In Workflow Automation, both leon (17,690 stars) and Tasmota (24,995 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, Tasmota is open source.
The lead is split. leon is furthest ahead on license flexibility (96 to 64), while Tasmota is furthest ahead on fork community (100 to 85). Choose the dimension a rollout cannot compromise on.
Composite score: leon 94.7, Tasmota 95.3. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | Tasmota |
|---|---|---|
| GitHub stars | 17,690 | 24,995 |
| Forks | 1,484 | 5,216 |
| Open issues | 118 | 12 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 95.3 |
🧠 Leon is your open-source personal assistant.
Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
Tasmota has more GitHub stars: 24,995 versus 17,690 for leon. The gap is 7,305 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both leon and Tasmota 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. Tasmota is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. leon scores 94.7 and Tasmota scores 95.3.