Skip to content
DevUtils Online

Workflow Automation

Activepieces vs bruno

bruno leads by 1.4 · narrow

B · leads

bruno

95.9

48,427 stars · MIT

Activepieces versus bruno is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Activepieces is written mainly in TypeScript; bruno is written mainly in JavaScript. The composite score is 94.5 for Activepieces and 95.9 for bruno.

bruno has 48,427 GitHub stars to Activepieces's 25,581, a gap of 22,846 (1.89×). Forks are 4,476 for Activepieces and 3,115 for bruno. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 100 versus 96.

Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and bruno was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 2,002 for bruno (0.041 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.

Both Activepieces and bruno are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Workflow Automation, both Activepieces (25,581 stars) and bruno (48,427 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: Activepieces is open source, bruno is open source.

The lead is split. Activepieces is furthest ahead on fork community (100 to 96), while bruno is furthest ahead on adoption (100 to 94). Choose the dimension a rollout cannot compromise on.

bruno finishes ahead at 95.9 against Activepieces at 94.5, a 1.4 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.

Activepieces versus bruno metrics
Signal Activepieces bruno
GitHub stars 25,581 48,427
Forks 4,476 3,115
Open issues 961 2,002
Adoption 94 100
Activity 100 100
Community 100 96
Issue health 70 70
License 96 96
Self-hosting 100 100
Composite 94.5 95.9

Activepieces

Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Activepieces or bruno?

bruno has more GitHub stars: 48,427 versus 25,581 for Activepieces. The gap is 22,846 stars.

Which was updated more recently, Activepieces or bruno?

Both were last pushed on 17 November 2026.

Can I self-host both Activepieces and bruno?

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

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

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

Who wins the Activepieces vs bruno score?

bruno scores 95.9 and Activepieces scores 94.5. This page calls that a narrow lead for bruno.

Related comparisons