Skip to content
DevUtils Online

Workflow Automation

bruno vs skyvern

bruno leads by 6.7 · narrow

A · leads

bruno

96.5

48,427 stars · MIT

B

skyvern

89.8

23,434 stars · AGPL-3.0

bruno versus skyvern 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; skyvern is written mainly in Python. The composite score is 96.5 for bruno and 89.8 for skyvern.

bruno has 48,427 GitHub stars to skyvern's 23,434, a gap of 24,993 (2.07×). Forks are 3,115 for bruno and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 96.

Push history: bruno was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,002 for bruno (0.041 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 70 and 84; 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. 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. License scores in this pair are 96 for bruno and 52 for skyvern. This is a procurement signal, not legal advice.

In Workflow Automation, both bruno (48,427 stars) and skyvern (23,434 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, skyvern is open source.

The lead is split. bruno is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.

bruno finishes ahead at 96.5 against skyvern at 89.8, a 6.7 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.

bruno versus skyvern metrics
Signal bruno skyvern
GitHub stars 48,427 23,434
Forks 3,115 2,246
Open issues 2,002 301
Adoption 100 93
Activity 100 100
Community 100 96
Issue health 70 84
License 96 52
Self-hosting 100 100
Composite 96.5 89.8

Questions this page answers

Which has more GitHub stars, bruno or skyvern?

bruno has more GitHub stars: 48,427 versus 23,434 for skyvern. The gap is 24,993 stars.

Which was updated more recently, bruno or skyvern?

Both were last pushed on 17 November 2026.

Can I self-host both bruno and skyvern?

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

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

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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the bruno vs skyvern score?

bruno scores 96.5 and skyvern scores 89.8. This page calls that a narrow lead for bruno.

Related comparisons