A · leads
fastlane
97.9
42,399 stars · MIT
Workflow Automation
fastlane leads by 5.1 · narrow
A · leads
97.9
42,399 stars · MIT
B
92.8
16,776 stars · Apache-2.0
fastlane 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. fastlane is written mainly in Ruby; trigger.dev is written mainly in TypeScript. The composite score is 97.9 for fastlane and 92.8 for trigger.dev.
fastlane has 42,399 GitHub stars to trigger.dev's 16,776, a gap of 25,623 (2.53×). Forks are 6,057 for fastlane and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 84.
Push history: fastlane 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 660 for fastlane (0.016 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
fastlane 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 fastlane and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both fastlane (42,399 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: fastlane is open source, trigger.dev is open source.
fastlane 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 16 points (100 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
fastlane finishes ahead at 97.9 against trigger.dev at 92.8, a 5.1 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 | fastlane | trigger.dev |
|---|---|---|
| GitHub stars | 42,399 | 16,776 |
| Forks | 6,057 | 1,534 |
| Open issues | 660 | 268 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 92.8 |
🚀 The easiest way to automate building and releasing your iOS and Android apps
Trigger.dev – build and deploy durable AI agents and workflows
fastlane has more GitHub stars: 42,399 versus 16,776 for trigger.dev. The gap is 25,623 stars.
trigger.dev was pushed more recently: 17 November 2026 versus 16 November 2026 for fastlane. That is 1 days apart.
Yes. This catalog marks both fastlane and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
fastlane 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.
fastlane scores 97.9 and trigger.dev scores 92.8. This page calls that a narrow lead for fastlane.