Skip to content
DevUtils Online

Workflow Automation

skyvern vs Tasmota

Tasmota leads by 4.2 · narrow

A

skyvern

91.1

23,434 stars · AGPL-3.0

B · leads

Tasmota

95.3

24,995 stars · GPL-3.0

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

Tasmota has 24,995 GitHub stars to skyvern's 23,434, a gap of 1,561 (1.07×). Forks are 2,246 for skyvern and 5,216 for Tasmota. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 90 versus 100.

Push history: skyvern 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 301 for skyvern (0.013 per star) and 12 for Tasmota (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for skyvern and 64 for Tasmota. This is a procurement signal, not legal advice.

In Workflow Automation, both skyvern (23,434 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: skyvern is open source, Tasmota is open source.

Tasmota is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is issue health at 12 points (84 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

Tasmota finishes ahead at 95.3 against skyvern at 91.1, a 4.2 point narrow 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.

skyvern versus Tasmota metrics
Signal skyvern Tasmota
GitHub stars 23,434 24,995
Forks 2,246 5,216
Open issues 301 12
Adoption 99 100
Activity 100 100
Community 90 100
Issue health 84 96
License 52 64
Self-hosting 100 100
Composite 91.1 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, skyvern or Tasmota?

Tasmota has more GitHub stars: 24,995 versus 23,434 for skyvern. The gap is 1,561 stars.

Which was updated more recently, skyvern or Tasmota?

Both were last pushed on 17 November 2026.

Can I self-host both skyvern and Tasmota?

Yes. This catalog marks both skyvern and Tasmota as self-hostable. Confirm each project's deploy docs before you plan a migration.

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

skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 skyvern vs Tasmota score?

Tasmota scores 95.3 and skyvern scores 91.1. This page calls that a narrow lead for Tasmota.

Related comparisons