A · leads
conductor
97.9
32,478 stars · Apache-2.0
Workflow Automation
conductor leads by 20.8 · decisive
A · leads
97.9
32,478 stars · Apache-2.0
B
77.1
2,919 stars · license n/a
conductor versus LoopForge 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; LoopForge is written mainly in Go. The composite score is 97.9 for conductor and 77.1 for LoopForge.
conductor has 32,478 GitHub stars to LoopForge's 2,919, a gap of 29,559 (11.13×). Forks are 1,074 for conductor and 423 for LoopForge. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 87.
Push history: conductor was last pushed on 17 November 2026 (0 days ago), and LoopForge was last pushed on 17 November 2026 (0 days ago). Open issues stand at 300 for conductor (0.009 per star) and 176 for LoopForge (0.060 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
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. LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for conductor and 30 for LoopForge. This is a procurement signal, not legal advice.
In Workflow Automation, both conductor (32,478 stars) and LoopForge (2,919 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, LoopForge is unpriced in this catalog.
conductor is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
conductor finishes ahead at 97.9 against LoopForge at 77.1, a 20.8 point decisive 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 | LoopForge |
|---|---|---|
| GitHub stars | 32,478 | 2,919 |
| Forks | 1,074 | 423 |
| Open issues | 300 | 176 |
| Adoption | 100 | 77 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 84 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 77.1 |
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
conductor has more GitHub stars: 32,478 versus 2,919 for LoopForge. The gap is 29,559 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both conductor and LoopForge 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. LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
conductor scores 97.9 and LoopForge scores 77.1. This page calls that a decisive lead for conductor.