A
LoopForge
78.2
2,919 stars · license n/a
Workflow Automation
trigger.dev leads by 19.7 · decisive
A
78.2
2,919 stars · license n/a
B · leads
97.9
16,776 stars · Apache-2.0
LoopForge 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. LoopForge is written mainly in Go; trigger.dev is written mainly in TypeScript. The composite score is 78.2 for LoopForge and 97.9 for trigger.dev.
trigger.dev has 16,776 GitHub stars to LoopForge's 2,919, a gap of 13,857 (5.75×). Forks are 423 for LoopForge and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 82 versus 100.
Push history: LoopForge 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 176 for LoopForge (0.060 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for LoopForge and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both LoopForge (2,919 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: LoopForge is unpriced in this catalog, trigger.dev is open source.
trigger.dev is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
trigger.dev finishes ahead at 97.9 against LoopForge at 78.2, a 19.7 point decisive 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 | LoopForge | trigger.dev |
|---|---|---|
| GitHub stars | 2,919 | 16,776 |
| Forks | 423 | 1,534 |
| Open issues | 176 | 268 |
| Adoption | 82 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 52 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 78.2 | 97.9 |
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
Trigger.dev – build and deploy durable AI agents and workflows
trigger.dev has more GitHub stars: 16,776 versus 2,919 for LoopForge. The gap is 13,857 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both LoopForge and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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.
trigger.dev scores 97.9 and LoopForge scores 78.2. This page calls that a decisive lead for trigger.dev.