A
flowgram.ai
94.3
8,589 stars · MIT
Workflow Automation
trigger.dev leads by 3.6 · narrow
A
94.3
8,589 stars · MIT
B · leads
97.9
16,776 stars · Apache-2.0
flowgram.ai 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. Both projects are written mainly in TypeScript. The composite score is 94.3 for flowgram.ai and 97.9 for trigger.dev.
trigger.dev has 16,776 GitHub stars to flowgram.ai's 8,589, a gap of 8,187 (1.95×). Forks are 788 for flowgram.ai and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 91 versus 100.
Push history: flowgram.ai was last pushed on 16 November 2026 (1 day ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 117 for flowgram.ai (0.014 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
flowgram.ai 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 flowgram.ai and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both flowgram.ai (8,589 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: flowgram.ai is open source, trigger.dev is open source.
trigger.dev is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 9 points (91 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
trigger.dev finishes ahead at 97.9 against flowgram.ai at 94.3, a 3.6 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 | flowgram.ai | trigger.dev |
|---|---|---|
| GitHub stars | 8,589 | 16,776 |
| Forks | 788 | 1,534 |
| Open issues | 117 | 268 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.3 | 97.9 |
FlowGram is an extensible workflow development framework with built-in canvas, form, variable, and materials that helps developers build AI workflow platforms faster and simpler.
Trigger.dev – build and deploy durable AI agents and workflows
trigger.dev has more GitHub stars: 16,776 versus 8,589 for flowgram.ai. The gap is 8,187 stars.
trigger.dev was pushed more recently: 17 November 2026 versus 16 November 2026 for flowgram.ai. That is 1 days apart.
Yes. This catalog marks both flowgram.ai and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
flowgram.ai 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.
trigger.dev scores 97.9 and flowgram.ai scores 94.3. This page calls that a narrow lead for trigger.dev.