A · leads
conductor
96.6
32,478 stars · Apache-2.0
Workflow Automation
conductor leads by 5.0 · narrow
A · leads
96.6
32,478 stars · Apache-2.0
B
91.6
23,434 stars · AGPL-3.0
conductor versus skyvern 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; skyvern is written mainly in Python. The composite score is 96.6 for conductor and 91.6 for skyvern.
conductor has 32,478 GitHub stars to skyvern's 23,434, a gap of 9,044 (1.39×). Forks are 1,074 for conductor and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 90 versus 100.
Push history: conductor was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 300 for conductor (0.009 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for conductor and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both conductor (32,478 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. conductor is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on fork community (100 to 90). Choose the dimension a rollout cannot compromise on.
conductor finishes ahead at 96.6 against skyvern at 91.6, a 5.0 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 | conductor | skyvern |
|---|---|---|
| GitHub stars | 32,478 | 23,434 |
| Forks | 1,074 | 2,246 |
| Open issues | 300 | 301 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.6 | 91.6 |
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
Automate browser based workflows with AI
conductor has more GitHub stars: 32,478 versus 23,434 for skyvern. The gap is 9,044 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both conductor and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
conductor scores 96.6 and skyvern scores 91.6. This page calls that a narrow lead for conductor.