A
ToolJet
91.2
41,239 stars · AGPL-3.0
Workflow Automation
trigger.dev leads by 1.8 · narrow
A
91.2
41,239 stars · AGPL-3.0
B · leads
93.0
16,776 stars · Apache-2.0
ToolJet 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. ToolJet is written mainly in HTML; trigger.dev is written mainly in TypeScript. The composite score is 91.2 for ToolJet and 93.0 for trigger.dev.
ToolJet has 41,239 GitHub stars to trigger.dev's 16,776, a gap of 24,463 (2.46×). Forks are 5,511 for ToolJet and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 85.
Push history: ToolJet 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 952 for ToolJet (0.023 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
ToolJet 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. 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 52 for ToolJet and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both ToolJet (41,239 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: ToolJet is open source, trigger.dev is open source.
The lead is split. ToolJet is furthest ahead on fork community (100 to 85), while trigger.dev is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 93.0 against ToolJet at 91.2, a 1.8 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 | ToolJet | trigger.dev |
|---|---|---|
| GitHub stars | 41,239 | 16,776 |
| Forks | 5,511 | 1,534 |
| Open issues | 952 | 268 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 70 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 93.0 |
Open-source foundation of ToolJet AI - the enterprise app generation platform for internal tools, dashboards, business applications, workflows and AI agents. Build visually, from a prompt, or from Claude Code, Codex and Cursor over MCP 🚀
Trigger.dev – build and deploy durable AI agents and workflows
ToolJet has more GitHub stars: 41,239 versus 16,776 for trigger.dev. The gap is 24,463 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ToolJet and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
ToolJet 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. 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 93.0 and ToolJet scores 91.2. This page calls that a narrow lead for trigger.dev.