A · leads
Activepieces
96.3
25,581 stars · MIT
Workflow Automation
Activepieces leads by 1.1 · narrow
A · leads
96.3
25,581 stars · MIT
B
95.2
24,995 stars · GPL-3.0
Activepieces versus Tasmota is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Activepieces is written mainly in TypeScript; Tasmota is written mainly in C. The composite score is 96.3 for Activepieces and 95.2 for Tasmota.
Activepieces has 25,581 GitHub stars to Tasmota's 24,995, a gap of 586 (1.02×). Forks are 4,476 for Activepieces and 5,216 for Tasmota. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 98 versus 100.
Push history: Activepieces 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 961 for Activepieces (0.038 per star) and 12 for Tasmota (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
Activepieces 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 Activepieces and 64 for Tasmota. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 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: Activepieces is open source, Tasmota is open source.
The lead is split. Activepieces is furthest ahead on license flexibility (96 to 64), while Tasmota is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Activepieces finishes ahead at 96.3 against Tasmota at 95.2, a 1.1 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 | Activepieces | Tasmota |
|---|---|---|
| GitHub stars | 25,581 | 24,995 |
| Forks | 4,476 | 5,216 |
| Open issues | 961 | 12 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 96.3 | 95.2 |
Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.
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
Activepieces has more GitHub stars: 25,581 versus 24,995 for Tasmota. The gap is 586 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and Tasmota as self-hostable. Confirm each project's deploy docs before you plan a migration.
Activepieces 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.
Activepieces scores 96.3 and Tasmota scores 95.2. This page calls that a narrow lead for Activepieces.