Skip to content
DevUtils Online

Workflow Automation

conductor vs trigger.dev

conductor leads by 1.5 · narrow

A · leads

conductor

97.2

32,478 stars · Apache-2.0

conductor versus trigger.dev 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; trigger.dev is written mainly in TypeScript. The composite score is 97.2 for conductor and 95.7 for trigger.dev.

conductor has 32,478 GitHub stars to trigger.dev's 16,776, a gap of 15,702 (1.94×). Forks are 1,074 for conductor and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 95 versus 100.

Push history: conductor was last pushed on 17 November 2026 (0 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 300 for conductor (0.009 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both conductor and trigger.dev 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 trigger.dev (16,776 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, trigger.dev is open source.

The lead is split. conductor is furthest ahead on adoption (100 to 94), while trigger.dev is furthest ahead on fork community (100 to 95). Choose the dimension a rollout cannot compromise on.

conductor finishes ahead at 97.2 against trigger.dev at 95.7, a 1.5 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

conductor versus trigger.dev metrics
Signal conductor trigger.dev
GitHub stars 32,478 16,776
Forks 1,074 1,534
Open issues 300 268
Adoption 100 94
Activity 100 100
Community 95 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 97.2 95.7

conductor

Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, conductor or trigger.dev?

conductor has more GitHub stars: 32,478 versus 16,776 for trigger.dev. The gap is 15,702 stars.

Which was updated more recently, conductor or trigger.dev?

Both were last pushed on 17 November 2026.

Can I self-host both conductor and trigger.dev?

Yes. This catalog marks both conductor and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, conductor or trigger.dev?

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. trigger.dev 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.

Who wins the conductor vs trigger.dev score?

conductor scores 97.2 and trigger.dev scores 95.7. This page calls that a narrow lead for conductor.

Related comparisons