A · leads
Archon
97.1
23,938 stars · MIT
Workflow Automation
Archon leads by 2.3 · narrow
A · leads
97.1
23,938 stars · MIT
B
94.8
27,230 stars · MIT
Archon versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Archon is written mainly in TypeScript; vagrant is written mainly in Ruby. The composite score is 97.1 for Archon and 94.8 for vagrant.
vagrant has 27,230 GitHub stars to Archon's 23,938, a gap of 3,292 (1.14×). Forks are 3,536 for Archon and 4,491 for vagrant. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 97 versus 100.
Push history: Archon 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 214 for Archon (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.
Both Archon 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 Archon (23,938 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: Archon is open source, vagrant is open source.
The lead is split. Archon is furthest ahead on issue health (84 to 70), while vagrant is furthest ahead on fork community (100 to 97). Choose the dimension a rollout cannot compromise on.
Archon finishes ahead at 97.1 against vagrant at 94.8, a 2.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 | Archon | vagrant |
|---|---|---|
| GitHub stars | 23,938 | 27,230 |
| Forks | 3,536 | 4,491 |
| Open issues | 214 | 760 |
| Adoption | 99 | 100 |
| Activity | 100 | 92 |
| Community | 97 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.1 | 94.8 |
The first open-source harness builder for AI coding. Make AI coding deterministic and repeatable.
Vagrant is a tool for building and distributing development environments.
vagrant has more GitHub stars: 27,230 versus 23,938 for Archon. The gap is 3,292 stars.
Archon was pushed more recently: 17 November 2026 versus 12 November 2026 for vagrant. That is 5 days apart.
Yes. This catalog marks both Archon and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
Archon 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.
Archon scores 97.1 and vagrant scores 94.8. This page calls that a narrow lead for Archon.