A · leads
conductor
97.9
32,478 stars · Apache-2.0
Workflow Automation
conductor leads by 14.1 · clear
A · leads
97.9
32,478 stars · Apache-2.0
B
83.8
1,635 stars · Apache-2.0
conductor versus rulego 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; rulego is written mainly in Go. The composite score is 97.9 for conductor and 83.8 for rulego.
conductor has 32,478 GitHub stars to rulego's 1,635, a gap of 30,843 (19.86×). Forks are 1,074 for conductor and 164 for rulego. On the log scale used inside this pair, adoption is 100 versus 71, and the fork community is 100 versus 73.
Push history: conductor was last pushed on 17 November 2026 (0 days ago), and rulego was last pushed on 13 November 2026 (4 days ago). Open issues stand at 300 for conductor (0.009 per star) and 4 for rulego (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
Both conductor and rulego are listed as Apache-2.0. 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 conductor (32,478 stars) and rulego (1,635 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, rulego is open source.
The lead is split. conductor is furthest ahead on adoption (100 to 71), while rulego is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
conductor finishes ahead at 97.9 against rulego at 83.8, a 14.1 point clear 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 | rulego |
|---|---|---|
| GitHub stars | 32,478 | 1,635 |
| Forks | 1,074 | 164 |
| Open issues | 300 | 4 |
| Adoption | 100 | 71 |
| Activity | 100 | 92 |
| Community | 100 | 73 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 83.8 |
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
⛓️RuleGo is a lightweight, high-performance, embedded, next-generation component orchestration rule engine framework for Go.
conductor has more GitHub stars: 32,478 versus 1,635 for rulego. The gap is 30,843 stars.
conductor was pushed more recently: 17 November 2026 versus 13 November 2026 for rulego. That is 4 days apart.
Yes. This catalog marks both conductor and rulego 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. rulego 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
conductor scores 97.9 and rulego scores 83.8. This page calls that a clear lead for conductor.