Skip to content
DevUtils Online

Workflow Automation

shepherd vs trigger.dev

trigger.dev leads by 18.1 · decisive

B · leads

trigger.dev

97.9

16,776 stars · Apache-2.0

shepherd 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. shepherd is written mainly in Python; trigger.dev is written mainly in TypeScript. The composite score is 79.8 for shepherd and 97.9 for trigger.dev.

trigger.dev has 16,776 GitHub stars to shepherd's 2,639, a gap of 14,137 (6.36×). Forks are 227 for shepherd and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 74 versus 100.

Push history: shepherd was last pushed on 09 September 2026 (69 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 13 for shepherd (0.005 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 96 and 84; activity scores are 58 and 100.

shepherd is listed as MIT, 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. License scores in this pair are 96 for shepherd and 96 for trigger.dev. This is a procurement signal, not legal advice.

In Workflow Automation, both shepherd (2,639 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: shepherd is open source, trigger.dev is open source.

The lead is split. shepherd is furthest ahead on issue health (96 to 84), while trigger.dev is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.

trigger.dev finishes ahead at 97.9 against shepherd at 79.8, a 18.1 point decisive 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.

shepherd versus trigger.dev metrics
Signal shepherd trigger.dev
GitHub stars 2,639 16,776
Forks 227 1,534
Open issues 13 268
Adoption 81 100
Activity 58 100
Community 74 100
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 79.8 97.9

shepherd

A runtime substrate that turns an agent's execution into a reversible, Git-like trace, so meta-agents can observe, fork, replay, and revert any run. Couples agent and environments in a copy-on-write fork ~5x faster than docker commit, with ~95% KV-cache reuse on replay. Framework built for meta-agents to supervise, optimize, and train other agents

Project site · GitHub · Full profile

Questions this page answers

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

trigger.dev has more GitHub stars: 16,776 versus 2,639 for shepherd. The gap is 14,137 stars.

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

trigger.dev was pushed more recently: 17 November 2026 versus 09 September 2026 for shepherd. That is 69 days apart.

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

Yes. This catalog marks both shepherd 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, shepherd or trigger.dev?

shepherd is listed as MIT, 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 shepherd vs trigger.dev score?

trigger.dev scores 97.9 and shepherd scores 79.8. This page calls that a decisive lead for trigger.dev.

Related comparisons