A · level
cli
97.4
32,362 stars · Apache-2.0
Workflow Automation
Too close to call · 97.4 to 96.8
A · level
97.4
32,362 stars · Apache-2.0
B · level
96.8
32,478 stars · Apache-2.0
cli versus conductor is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cli is written mainly in Rust; conductor is written mainly in Java. The composite score is 97.4 for cli and 96.8 for conductor.
conductor has 32,478 GitHub stars to cli's 32,362, a gap of 116 (1.00×). Forks are 1,997 for cli and 1,074 for conductor. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 92.
Push history: cli was last pushed on 03 November 2026 (14 days ago), and conductor was last pushed on 17 November 2026 (0 days ago). Open issues stand at 137 for cli (0.004 per star) and 300 for conductor (0.009 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
Both cli and conductor 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 cli (32,362 stars) and conductor (32,478 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: cli is open source, conductor is open source.
The lead is split. cli is furthest ahead on issue health (96 to 84), while conductor is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Composite score: cli 97.4, conductor 96.8. 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 | cli | conductor |
|---|---|---|
| GitHub stars | 32,362 | 32,478 |
| Forks | 1,997 | 1,074 |
| Open issues | 137 | 300 |
| Adoption | 100 | 100 |
| Activity | 92 | 100 |
| Community | 100 | 92 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 96.8 |
Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent skills.
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
conductor has more GitHub stars: 32,478 versus 32,362 for cli. The gap is 116 stars.
conductor was pushed more recently: 17 November 2026 versus 03 November 2026 for cli. That is 14 days apart.
Yes. This catalog marks both cli and conductor as self-hostable. Confirm each project's deploy docs before you plan a migration.
cli 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. cli scores 97.4 and conductor scores 96.8.