Skip to content
DevUtils Online

Workflow Automation

Activepieces vs vagrant

Activepieces leads by 1.5 · narrow

B

vagrant

94.8

27,230 stars · MIT

Activepieces versus vagrant 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; vagrant is written mainly in Ruby. The composite score is 96.3 for Activepieces and 94.8 for vagrant.

vagrant has 27,230 GitHub stars to Activepieces's 25,581, a gap of 1,649 (1.06×). Forks are 4,476 for Activepieces 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 100.

Push history: Activepieces 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 961 for Activepieces (0.038 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 70 and 70; activity scores are 100 and 92.

Both Activepieces and vagrant 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 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: Activepieces is open source, vagrant is open source.

The lead is split. Activepieces is furthest ahead on recent activity (100 to 92), while vagrant is furthest ahead on adoption (100 to 99). Choose the dimension a rollout cannot compromise on.

Activepieces finishes ahead at 96.3 against vagrant at 94.8, a 1.5 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 vagrant metrics
Signal Activepieces vagrant
GitHub stars 25,581 27,230
Forks 4,476 4,491
Open issues 961 760
Adoption 99 100
Activity 100 92
Community 100 100
Issue health 70 70
License 96 96
Self-hosting 100 100
Composite 96.3 94.8

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 vagrant?

vagrant has more GitHub stars: 27,230 versus 25,581 for Activepieces. The gap is 1,649 stars.

Which was updated more recently, Activepieces or vagrant?

Activepieces was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.

Can I self-host both Activepieces and vagrant?

Yes. This catalog marks both Activepieces and vagrant 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 vagrant?

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. 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.

Who wins the Activepieces vs vagrant score?

Activepieces scores 96.3 and vagrant scores 94.8. This page calls that a narrow lead for Activepieces.

Related comparisons