A · level
Archon
95.7
23,938 stars · MIT
Workflow Automation
Too close to call · 95.7 to 96.3
A · level
95.7
23,938 stars · MIT
B · level
96.3
48,427 stars · MIT
Archon versus bruno 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; bruno is written mainly in JavaScript. The composite score is 95.7 for Archon and 96.3 for bruno.
bruno has 48,427 GitHub stars to Archon's 23,938, a gap of 24,489 (2.02×). Forks are 3,536 for Archon 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 98.
Push history: Archon 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 214 for Archon (0.009 per star) and 2,002 for bruno (0.041 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
Both Archon 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 Archon (23,938 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: Archon is open source, bruno is open source.
The lead is split. Archon is furthest ahead on issue health (84 to 70), while bruno is furthest ahead on adoption (100 to 94). Choose the dimension a rollout cannot compromise on.
Composite score: Archon 95.7, bruno 96.3. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | bruno |
|---|---|---|
| GitHub stars | 23,938 | 48,427 |
| Forks | 3,536 | 3,115 |
| Open issues | 214 | 2,002 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.7 | 96.3 |
The first open-source harness builder for AI coding. Make AI coding deterministic and repeatable.
Opensource IDE For Exploring and Testing API's (lightweight alternative to Postman/Insomnia)
bruno has more GitHub stars: 48,427 versus 23,938 for Archon. The gap is 24,489 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Archon and bruno 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. 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.
Neither tool clears a one-point margin. Archon scores 95.7 and bruno scores 96.3.