Skip to content
DevUtils Online

Workflow Automation

automa vs Tasmota

Tasmota leads by 26.4 · decisive

A

automa

68.9

21,723 stars · license n/a

B · leads

Tasmota

95.3

24,995 stars · GPL-3.0

automa versus Tasmota is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. automa is written mainly in Vue; Tasmota is written mainly in C. The composite score is 68.9 for automa and 95.3 for Tasmota.

Tasmota has 24,995 GitHub stars to automa's 21,723, a gap of 3,272 (1.15×). Forks are 2,341 for automa and 5,216 for Tasmota. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 91 versus 100.

Push history: automa was last pushed on 02 March 2026 (260 days ago), and Tasmota was last pushed on 17 November 2026 (0 days ago). Open issues stand at 379 for automa (0.017 per star) and 12 for Tasmota (0.000 per star). Issue-health scores are 84 and 96; activity scores are 36 and 100.

automa is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for automa and 64 for Tasmota. This is a procurement signal, not legal advice.

Only Tasmota is marked self-hostable here (24,995 stars, deploy score 100). automa is not (21,723 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: automa is unpriced in this catalog, Tasmota is open source.

Tasmota is ahead on every scored dimension that is not level. The widest gap is self-hosting at 65 points (35 vs 100), and the tightest is adoption at 1 points (99 vs 100).

Tasmota finishes ahead at 95.3 against automa at 68.9, a 26.4 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

automa versus Tasmota metrics
Signal automa Tasmota
GitHub stars 21,723 24,995
Forks 2,341 5,216
Open issues 379 12
Adoption 99 100
Activity 36 100
Community 91 100
Issue health 84 96
License 30 64
Self-hosting 35 100
Composite 68.9 95.3

Tasmota

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

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, automa or Tasmota?

Tasmota has more GitHub stars: 24,995 versus 21,723 for automa. The gap is 3,272 stars.

Which was updated more recently, automa or Tasmota?

Tasmota was pushed more recently: 17 November 2026 versus 02 March 2026 for automa. That is 260 days apart.

Can I self-host both automa and Tasmota?

Only Tasmota is marked self-hostable. automa is not.

Which license is easier to embed in a commercial product, automa or Tasmota?

automa is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.

Who wins the automa vs Tasmota score?

Tasmota scores 95.3 and automa scores 68.9. This page calls that a decisive lead for Tasmota.

Related comparisons