A · leads
bruno
95.7
48,427 stars · MIT
Workflow Automation
bruno leads by 2.5 · narrow
A · leads
95.7
48,427 stars · MIT
B
93.2
24,995 stars · GPL-3.0
bruno versus Tasmota is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; Tasmota is written mainly in C. The composite score is 95.7 for bruno and 93.2 for Tasmota.
bruno has 48,427 GitHub stars to Tasmota's 24,995, a gap of 23,432 (1.94×). Forks are 3,115 for bruno and 5,216 for Tasmota. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 94 versus 100.
Push history: bruno 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 2,002 for bruno (0.041 per star) and 12 for Tasmota (0.000 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
bruno 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 bruno and 64 for Tasmota. This is a procurement signal, not legal advice.
In Workflow Automation, both bruno (48,427 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: bruno is open source, Tasmota is open source.
The lead is split. bruno 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.
bruno finishes ahead at 95.7 against Tasmota at 93.2, a 2.5 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 | bruno | Tasmota |
|---|---|---|
| GitHub stars | 48,427 | 24,995 |
| Forks | 3,115 | 5,216 |
| Open issues | 2,002 | 12 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 95.7 | 93.2 |
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
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
bruno has more GitHub stars: 48,427 versus 24,995 for Tasmota. The gap is 23,432 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both bruno and Tasmota as self-hostable. Confirm each project's deploy docs before you plan a migration.
bruno 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.
bruno scores 95.7 and Tasmota scores 93.2. This page calls that a narrow lead for bruno.