A · leads
sim
97.4
30,151 stars · Apache-2.0
Workflow Automation
sim leads by 2.7 · narrow
A · leads
97.4
30,151 stars · Apache-2.0
B
94.7
24,995 stars · GPL-3.0
sim versus Tasmota is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. sim is written mainly in TypeScript; Tasmota is written mainly in C. The composite score is 97.4 for sim and 94.7 for Tasmota.
sim has 30,151 GitHub stars to Tasmota's 24,995, a gap of 5,156 (1.21×). Forks are 3,915 for sim and 5,216 for Tasmota. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 97 versus 100.
Push history: sim 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 330 for sim (0.011 per star) and 12 for Tasmota (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
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. 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 sim and 64 for Tasmota. This is a procurement signal, not legal advice.
In Workflow Automation, both sim (30,151 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: sim is open source, Tasmota is open source.
The lead is split. sim is furthest ahead on license flexibility (96 to 64), while Tasmota is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
sim finishes ahead at 97.4 against Tasmota at 94.7, a 2.7 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 | sim | Tasmota |
|---|---|---|
| GitHub stars | 30,151 | 24,995 |
| Forks | 3,915 | 5,216 |
| Open issues | 330 | 12 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 97 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 94.7 |
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
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
sim has more GitHub stars: 30,151 versus 24,995 for Tasmota. The gap is 5,156 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both sim and Tasmota as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
sim scores 97.4 and Tasmota scores 94.7. This page calls that a narrow lead for sim.