Head to head · Human approval · October 2026 research run

Temporal vs Trigger.dev

Temporal scores 76.6 (BB) on agent readiness against Trigger.dev's 63.3 (B), and leads in 4 of 7 scored categories. Trigger.dev leads on payments & pricing. 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

Temporal BB

Best for A team that already runs, or wants to run, agents as durable workflows with strict guarantees and an audit trail per run.

Ahead on

  • Reliability, 80 against 75
  • Agent ergonomics, 85 against 79
  • Security & auth, 88 against 75
  • Transparency & trust, 91 against 82

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No reviewer inbox, notifications or routing, so the human side is all 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

  • Payments & pricing, 60 against 30

Also in its favour

  • A hosted endpoint, with nothing to install
  • Runs on your own machine

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.

Payments & pricing Trigger.dev +30

Temporal 30

No machine payment protocol (0). Per-unit prices published, $50 per million Actions on Developer, tiering down to $25 per million with volume from Business up, plus storage per GB-hour (20). New accounts get $150 of credits for 90 days, but on 1 November the pricing page still says "A credit card is required to sign up for Temporal Cloud" (0). The MIT server is free to run yourself, but the rubric scores the hosted option. A person signs up for Cloud in the browser or through a cloud marketplace (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Trigger.dev 60

No machine payment protocol (0). Per-unit prices published without a login and re-read on 2 November, $0.0000338 a second for the default Small 1x machine (0.5 vCPU) up to $0.00068 for Large 2x, plus $0.25 per 10,000 runs (20). Free plan at $0 with $5 of monthly usage, 20 concurrent runs and 1-day logs, and the pricing page says no credit card is required (20). A person signs up in the browser. Since 4.7.0 the CLI can create the first organisation and activate the Free plan, but login still goes through browser authorisation (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Security & auth Temporal +13

Temporal 88

Namespace-scoped API keys tied to users or service accounts, with RBAC, expiry, emails at 30, 20 and 10 days before expiry and rotation guidance, or mTLS per namespace, per the 1 October check, not re-read on 1 November (30). Read-only account role and namespace-scoped service accounts (18 of 20). It returns your own workflow data and the signal payloads you send (10). Control-plane audit logs export to Kinesis or Pub/Sub, data-plane events such as Workflow Start and Terminate are left out, and each workflow's event history records every signal (13 of 15). temporal.io/.well-known/security.txt is valid (security@temporal.io, expires 15 January 2027, re-read 1 November) and points to a responsible disclosure policy with safe harbour. Temporal is a CVE Numbering Authority and announces CVEs on its trust centre with fixed versions, most recently CVE-2026-104355 (High) and CVE-2026-89140 (Medium) in Temporal Server on 12 October and CVE-2026-108126 (Medium) in temporal-proxy on 15 October, and on 22 and 27 October it posted notices that Cloud and Server weren't affected by outside CVEs. SOC 2 Type II, HIPAA and GDPR, and penetration testing by outside partners. No bug bounty found (17 of 20). 30 + 18 + 10 + 13 + 17 = 88.

Trigger.dev 75

Secret keys per environment, personal access tokens for the CLI and MCP, and a public access token scoped to one waitpoint for browser completion. Since 4.8.2 deployed tasks use short-lived run tokens for supported SDK operations. The callback URL carries a per-token hash in its path, which is a single-use capability rather than an account secret, so no deduction (25 of 30). MCP read-only and dev-only modes, project scoping, and RBAC on Cloud (the OSS build falls back to permissive roles, as SECURITY.md says) (15 of 20). It returns your own run data and the completion payload (10). Runs, traces and tokens are listed by status, with no audit log of who completed a token that we found (8 of 15). SECURITY.md with private GitHub advisories, a valid security.txt (expires 2027-09-01, re-read on 2 November), SOC 2 Type II with the report and a penetration test report on request for Enterprise per the 17 October check, and advisories published with CVE IDs on GitHub. No bug bounty found (17 of 20). The 1 November breach is counted under negative events. 25 + 15 + 10 + 8 + 17 = 75.

Transparency & trust Temporal +9

Temporal 91

Server and SDKs under MIT (30). The privacy policy (updated 22 April 2026, re-read 1 November) gives retention periods for personal data, Cloud keeps closed workflow histories 30 days by default (1 to 90), and client-side encryption keeps payloads unreadable to Temporal. The DPA at temporal.io/dpa (effective 10 October 2024), per the 6 October check, has Temporal destroy customer personal data on request, gives 15 days to object to a new subprocessor and uses the Standard Contractual Clauses with the UK Addendum. These agree (30). Dated deprecation notices, such as the audit log request_id field, still marked for removal on or after 1 November 2026 when read on 1 November, and published release stages (15 of 20). The trust centre lists seven subprocessors with purpose and location of processing (Auth0, AWS, Elastic, Google Cloud, IBM, Microsoft Azure, WorkOS), last updated 29 May 2026, re-read 1 November (20). 30 + 30 + 15 + 20 = 95.

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

Agent ergonomics Temporal +6

Temporal 85

No official MCP server, so context cost is judged on the API. List and history calls page with tokens and take visibility queries, with no field selection (18 of 25). Visibility filters and next_page_token paging (20). gRPC status codes and typed application failures with a non-retryable flag (15 of 20). Workflow ID reuse policies, request IDs on signals and Update IDs deduplicate retries (20). SDKs in eight languages, but an approval needs a running worker, a workflow definition and a signal sender before the first call (12 of 15). Per the 6 October check, not re-read on 1 November. 18 + 20 + 15 + 20 + 12 = 85.

Trigger.dev 79

The MCP server registers 55 tools in the released 4.8.3 (54 with telemetry off), up from 49 in 4.7.4 with webhook, alert and session tools (5), plus --readonly mode, which hides the 23 write tools, --dev-only mode and project scoping (8), so 13 for MCP. The REST API pages and filters (20). We average the two surfaces to 16 of 25. Tokens list by status and tags, runs list with filters and cursors (20). wait.forToken() returns ok: false with an error on timeout, .unwrap() throws, and the spec documents errors (15 of 20). Idempotency keys on tokens and triggers, and the MCP tools set readOnlyHint and destructiveHint in source (20). Every createToken option is optional, but the official SDK is TypeScript only (8 of 15). 16 + 20 + 15 + 20 + 8 = 79.

Reliability Temporal +5

Temporal 80

Status page at status.temporal.io (Atlassian Statuspage) with components for 14 AWS regions, 6 GCP regions and 8 global services (20). On 1 November its RSS history feed was read (its robots.txt disallows the /api/ feed used on 6 October). In the 90 days from 3 August one major sits on the core path. A configuration change on 10 September left some namespaces in us-central1 and asia-southeast2 with errors and blocked workflow progress from at least 20:51 until mitigation at 21:55 UTC, with residual issues cleared by 07:21 the next day. Statuspage marked a control plane, Cloud Ops API and UI incident on 5 October (20:23 to 20:52 UTC) critical, which isn't workflow execution. The 31 July to 1 August Usage API and UI outage has left the window. Since 17 October there are only minor entries. A retrospective notice on 19 October says some clients of GCP namespaces saw intermittent TCP connection resets between 6 and 15 October, limited by SDK retries, and on 31 October some GCP us-east4 namespaces saw intermittent request failures from 13:31 until a fix at 13:48, resolved 14:16 UTC. Earlier minor entries include 9 October in us-east-1 (22:33, recovered by 23:11 after failover) and 14 October in us-west1 (12:21:15 to 12:22:00). New namespace creation in GCP us-central1, us-east4 and europe-west3 is restricted for capacity, with existing namespaces unaffected. One major outage, so 10 of 30. Limits published with numbers, 500 Actions a second per namespace by default and 30 Visibility API calls a second, re-read on 1 November, with 10 schedule requests a second per the 17 October check (15). Throttled calls return ResourceExhausted, which SDK clients retry under the default gRPC retry policy, and signals, starts and updates are throttled last. Workflow IDs and request IDs make starts and signals safe to retry (15). Contractual SLA at temporal.io/sla of 99.9 per cent for a standard single-region namespace and 99.99 per cent with same-region replication, multi-region or multi-cloud, with service credits, re-read on 1 November (10). Signals, timers and Updates are GA (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.

Trigger.dev 75

Status page at status.trigger.dev (Better Stack) with components per region and incident history (20). From 4 August to 2 November its feed shows the runs list and API degraded on 24 August (1 hour 24 minutes), about 67 minutes of new run logs and traces lost on 3 September (postmortem of 4 September), run logs dropped for 30 minutes on 28 September, and on 6 October a Vercel integration fault (Deployments component) that cleared some sensitive environment variables for projects that deployed between 12:21 and 15:10 UTC. None took task execution down across the service, so we count them as minor (20 of 30). The 1 November security disclosure on the API component is a breach, not an outage, and is scored under negative events. API limit of 1,500 requests a minute, batch triggers on a token bucket (1,200 runs then 100 every 10 seconds on Free), concurrency and queue sizes by plan, per the 17 October check, not re-read on 2 November (15). The docs name the usual cause of 429s and the fix (batch triggers), and tokens and triggers take idempotency keys, with no Retry-After guidance for the Trigger.dev API itself (10 of 15). No SLA found on the pricing page, re-read on 2 November (0). Waitpoint tokens are GA in v4 (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Score by category

CategoryWeightTemporalTrigger.devEdge
Reliability16%8075Temporal +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9191even
Agent ergonomics13%8579Temporal +6
Security & auth14%8875Temporal +13
Payments & pricing10%3060Trigger.dev +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9090even
Transparency & trust7%9182Temporal +9
Negative events≤15-3-15
TotalBB 76.6/100B 63.3/100

Facts side by side

FactTemporalTrigger.dev
KindPlatformPlatform
VendorTemporal TechnologiesTrigger.dev
Hosted endpointno (local only)https://api.trigger.dev
TransportsHTTPHTTP, stdio
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceMITApache-2.0
Tools exposednone55
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedio.github.triggerdotdev/trigger.dev
Last release2026-10-282026-10-30
Terms last updated2024-10-012026-06-29
Privacy policy last updated2026-04-222025-12-23
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews3.6/5 (8)3.6/5 (8)

The panel on both

3 of the 8 reviewers who reviewed both rate Temporal higher.

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

Temporal

Waits of any length with a timeout survive worker restarts and deploys. No reviewer inbox, notifications or routing, so the human side is all 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

Temporal

  1. Put the decision in a typed Signal payload (approver, decision, comments, timestamp) instead of a bare boolean
  2. Always wait with a timeout and treat the timeout path as a rejection or an escalation on purpose
  3. Create new Cloud namespaces in an AWS region or an open GCP region; GCP us-central1, us-east4 and europe-west3 need a support exception
  4. Use an Update instead of a Signal when the approver's tool needs an acknowledgement back
  5. Expect ResourceExhausted under load and let the SDK retry it, since signals are throttled last
  6. Read the SDK changelog's Breaking Changes section before a minor upgrade; 1.35.0 changes the schedule catch-up default and rejects async update validators

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, Temporal or Trigger.dev?

Temporal scores 76.6 (BB) on agent readiness against Trigger.dev's 63.3 (B), and leads in 4 of 7 scored categories. Trigger.dev leads on payments & pricing.

Are Temporal and Trigger.dev open source?

Yes. Temporal is open source (MIT). Trigger.dev is open source (Apache-2.0).

Other comparisons with Temporal 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.