A · level
Tasmota
95.0
24,995 stars · GPL-3.0
Workflow Automation
Too close to call · 95.0 to 94.5
A · level
95.0
24,995 stars · GPL-3.0
B · level
94.5
27,230 stars · MIT
Tasmota versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Tasmota is written mainly in C; vagrant is written mainly in Ruby. The composite score is 95.0 for Tasmota and 94.5 for vagrant.
vagrant has 27,230 GitHub stars to Tasmota's 24,995, a gap of 2,235 (1.09×). Forks are 5,216 for Tasmota and 4,491 for vagrant. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 98.
Push history: Tasmota was last pushed on 17 November 2026 (0 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 12 for Tasmota (0.000 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 96 and 70; activity scores are 100 and 92.
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. vagrant 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. License scores in this pair are 64 for Tasmota and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both Tasmota (24,995 stars) and vagrant (27,230 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: Tasmota is open source, vagrant is open source.
The lead is split. Tasmota is furthest ahead on issue health (96 to 70), while vagrant is furthest ahead on license flexibility (96 to 64). Choose the dimension a rollout cannot compromise on.
Composite score: Tasmota 95.0, vagrant 94.5. 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 | Tasmota | vagrant |
|---|---|---|
| GitHub stars | 24,995 | 27,230 |
| Forks | 5,216 | 4,491 |
| Open issues | 12 | 760 |
| Adoption | 99 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 98 |
| Issue health | 96 | 70 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.0 | 94.5 |
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
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 24,995 for Tasmota. The gap is 2,235 stars.
Tasmota was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both Tasmota and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. vagrant 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. Tasmota scores 95.0 and vagrant scores 94.5.