A · leads
conductor
95.5
32,478 stars · Apache-2.0
Workflow Automation
conductor leads by 1.3 · narrow
A · leads
95.5
32,478 stars · Apache-2.0
B
94.2
27,230 stars · MIT
conductor versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. conductor is written mainly in Java; vagrant is written mainly in Ruby. The composite score is 95.5 for conductor and 94.2 for vagrant.
conductor has 32,478 GitHub stars to vagrant's 27,230, a gap of 5,248 (1.19×). Forks are 1,074 for conductor and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 83 versus 100.
Push history: conductor 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 300 for conductor (0.009 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 84 and 70; activity scores are 100 and 92.
conductor is listed as Apache-2.0, 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. License scores in this pair are 96 for conductor and 96 for vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both conductor (32,478 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: conductor is open source, vagrant is open source.
The lead is split. conductor is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 83). Choose the dimension a rollout cannot compromise on.
conductor finishes ahead at 95.5 against vagrant at 94.2, a 1.3 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 | conductor | vagrant |
|---|---|---|
| GitHub stars | 32,478 | 27,230 |
| Forks | 1,074 | 4,491 |
| Open issues | 300 | 760 |
| Adoption | 100 | 98 |
| Activity | 100 | 92 |
| Community | 83 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.5 | 94.2 |
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
Vagrant is a tool for building and distributing development environments.
conductor has more GitHub stars: 32,478 versus 27,230 for vagrant. The gap is 5,248 stars.
conductor was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both conductor and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
conductor is listed as Apache-2.0, 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.
conductor scores 95.5 and vagrant scores 94.2. This page calls that a narrow lead for conductor.