Skip to content
DevUtils Online

Workflow Automation

superplane vs trigger.dev

trigger.dev leads by 12.5 · clear

B · leads

trigger.dev

97.9

16,776 stars · Apache-2.0

superplane 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. superplane is written mainly in Go; trigger.dev is written mainly in TypeScript. The composite score is 85.4 for superplane and 97.9 for trigger.dev.

trigger.dev has 16,776 GitHub stars to superplane's 10,094, a gap of 6,682 (1.66×). Forks are 710 for superplane and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 90 versus 100.

Push history: superplane 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 266 for superplane (0.026 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.

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

In Workflow Automation, both superplane (10,094 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: superplane 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 superplane at 85.4, a 12.5 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.

superplane versus trigger.dev metrics
Signal superplane trigger.dev
GitHub stars 10,094 16,776
Forks 710 1,534
Open issues 266 268
Adoption 95 100
Activity 100 100
Community 90 100
Issue health 70 84
License 30 96
Self-hosting 100 100
Composite 85.4 97.9

Questions this page answers

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

trigger.dev has more GitHub stars: 16,776 versus 10,094 for superplane. The gap is 6,682 stars.

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

Both were last pushed on 17 November 2026.

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

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

superplane 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.

Who wins the superplane vs trigger.dev score?

trigger.dev scores 97.9 and superplane scores 85.4. This page calls that a clear lead for trigger.dev.

Related comparisons