Skip to content
DevUtils Online

Workflow Automation

edict vs trigger.dev

trigger.dev leads by 7.7 · clear

A

edict

89.9

17,077 stars · MIT

B · leads

trigger.dev

97.6

16,776 stars · Apache-2.0

edict 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. edict is written mainly in Python; trigger.dev is written mainly in TypeScript. The composite score is 89.9 for edict and 97.6 for trigger.dev.

edict has 17,077 GitHub stars to trigger.dev's 16,776, a gap of 301 (1.02×). Forks are 1,771 for edict and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 98.

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

edict 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 edict and 96 for trigger.dev. This is a procurement signal, not legal advice.

In Workflow Automation, both edict (17,077 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: edict is open source, trigger.dev is open source.

The lead is split. edict 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.6 against edict at 89.9, a 7.7 point clear 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.

edict versus trigger.dev metrics
Signal edict trigger.dev
GitHub stars 17,077 16,776
Forks 1,771 1,534
Open issues 15 268
Adoption 100 100
Activity 58 100
Community 100 98
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 89.9 97.6

edict

🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System — 9 specialized AI agents with real-time dashboard, model config, and full audit trails

Project site · GitHub · Full profile

Questions this page answers

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

edict has more GitHub stars: 17,077 versus 16,776 for trigger.dev. The gap is 301 stars.

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

trigger.dev was pushed more recently: 17 November 2026 versus 28 September 2026 for edict. That is 50 days apart.

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

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

edict 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 edict vs trigger.dev score?

trigger.dev scores 97.6 and edict scores 89.9. This page calls that a clear lead for trigger.dev.

Related comparisons