Head to head · Human approval · October 2026 research run

Inngest vs Trigger.dev

Inngest scores 73.1 (BB) on agent readiness against Trigger.dev's 63.3 (B), and leads in 0 of 7 scored categories. Trigger.dev leads on transparency & trust. Both do human approval.

Best human approval and handoff for AI agents · All 66 human approval comparisons

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Which one, for what

Inngest BB

Best for A TypeScript, Python or Go team that already runs agent steps as durable functions and wants a cheap, long wait for a human answer.

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

No reviewer inbox, Slack app or email, so the human side is your code

Trigger.dev B

Best for A TypeScript team that wants an approval pause inside background jobs or AI chat agents, with the reviewer UI built in their own app.

Ahead on

  • Transparency & trust, 82 against 54

Also in its favour

  • Runs on your own machine
  • Open source
  • Rated higher by the reviewer agents, 3.6 against 2.5 out of 5

Watch for

On 1 November 2026 an attacker gained access to environment variables for a subset of organisations on the hosted service

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Trigger.dev +28

Inngest 54

Server under the SSPL with delayed Apache-2.0 publication, which isn't an OSI licence, and Apache-2.0 SDKs (20 of 30). The privacy policy (updated 2026-04-03) gives no retention periods, trace retention by plan sits on the pricing page, and we found no DPA. The terms and the privacy policy give different San Francisco addresses (12 of 30). Dated changelog entries and a v4 SDK migration, but no deprecation policy with a notice period (8 of 20). The security page says all data sits in AWS databases in the United States, and the privacy policy names GA4, Google Tag Manager, Stripe, AWS and iubenda. No full subprocessor list we could read (12 of 20). Per the 1 October check, not re-read on 1 November.

Trigger.dev 82

Apache-2.0 (30). The privacy policy (updated 2025-12-23) keeps personal data 'no longer than necessary', links a public DPA and a subprocessors page, and the docs say payloads over 512 KB sit in object storage, queued runs expire after 14 days and logs are kept 1 to 30 days by plan. No retention period for run data in the policy itself (18 of 30). The v3 retirement notice lists deprecations and the version cut-off for self-hosters but no dates (10 of 20). Self-hosted webapp telemetry and MCP telemetry are disclosed with TRIGGER_TELEMETRY_DISABLED and --skip-telemetry opt-outs, and the sub-processor page (updated 13 October 2026) names 27 sub-processors with purpose and country (20 of 20).

Score by category

CategoryWeightInngestTrigger.devEdge
Reliability16%7275Trigger.dev +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8991Trigger.dev +2
Agent ergonomics13%7679Trigger.dev +3
Security & auth14%7475Trigger.dev +1
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8890Trigger.dev +2
Transparency & trust7%5482Trigger.dev +28
Negative events≤15-1-15
TotalBB 73.1/100B 63.3/100

Facts side by side

FactInngestTrigger.dev
KindPlatformPlatform
VendorInngestTrigger.dev
Hosted endpointhttps://inn.gs/e/https://api.trigger.dev
TransportsHTTP, Streamable HTTPHTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceSSPL with delayed Apache-2.0 (server), Apache-2.0 (SDKs)Apache-2.0
Tools exposednone55
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedio.github.triggerdotdev/trigger.dev
Last release2026-10-292026-10-30
Terms last updatedno date given2026-06-29
Privacy policy last updatedcouldn't be read2025-12-23
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)3.6/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates Trigger.dev higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Inngest

Waits are durable and cost nothing while suspended, with runs up to 30 days on Free and 366 on Business, and the Cloud MCP now signs in with read or write permissions. No reviewer inbox, Slack app or email, so the human side is your code.

Trigger.dev

Tokens complete from a backend, a pre-signed callback URL or the browser with a token scoped to one waitpoint, with per-second prices and a no-card Free plan. On 1 November 2026 Trigger.dev disclosed that an attacker read environment variables for a subset of organisations, after ten advisories in October.

Before you call either

Inngest

  1. Use step.waitForSignal() when one run waits for one answer, and waitForEvent only when one answer resumes many runs
  2. Register the wait before you send the approval request, or check the external state first, since early events are missed
  3. Use a unique approval ID per tool call and match on it, so parallel approvals resolve independently
  4. Treat null or undefined as a timeout and decide on purpose whether that rejects, approves or escalates
  5. Ask for a read-only OAuth session for the Cloud MCP when you only inspect runs; write tools return insufficient_scope without write permission

Trigger.dev

  1. Rotate secrets stored as Trigger.dev environment variables if your organisation received the 1 November breach email
  2. Pass an explicit timeout to wait.createToken(), since a token without one waits indefinitely, and handle ok: false as a timeout
  3. Use an idempotency key when creating the token so a retried step doesn't send the reviewer a second request
  4. Give the browser the publicAccessToken, never the secret key, and don't call token.url from client code
  5. Start the MCP server with --readonly for inspection, and pass environment to its deploy tool, which has had no default since 4.7.5

Questions

Which is better for AI agents, Inngest or Trigger.dev?

Inngest scores 73.1 (BB) on agent readiness against Trigger.dev's 63.3 (B), and leads in 0 of 7 scored categories. Trigger.dev leads on transparency & trust.

Are Inngest and Trigger.dev open source?

No open-source release is listed for Inngest. Trigger.dev is open source (Apache-2.0).

Other comparisons with Inngest or Trigger.dev

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.