Head to head · Human approval · October 2026 research run
Orkes Conductor Human tasks vs Trigger.dev
Trigger.dev scores 63.3 (B) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 6 of 7 scored categories. 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
Best for Teams that already orchestrate agents as Conductor workflows and need formal routing, per-assignee deadlines and escalation without writing them.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow
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
- Reliability, 75 against 32
- Schema & documentation, 91 against 65
- Agent ergonomics, 79 against 69
- Payments & pricing, 60 against 30
- Maintenance & community, 90 against 81
- Transparency & trust, 82 against 46
Also in its favour
- 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.
Reliability Trigger.dev +43
Orkes Conductor Human tasks 32
No public status page found for Orkes Cloud or the Developer Edition, in a web search or the docs repository on 4 November (0), so no readable incident history (5). API rate limits aren't published. The rate-limit page covers per-task execution limits you set yourself, and the Developer Edition says its limits may change (0). No 429 or backoff guidance found, but workflow starts take an idempotency key with FAIL, RETURN_EXISTING or FAIL_ON_RUNNING strategies (7 of 15, a partial kept under the in-between rule). The Cloud support policy sets 99.9 or 99.0 per cent by plan with service credits, and Enterprise goes up to 99.99 per cent (10). The Human task is GA (10). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. 0 + 5 + 0 + 7 + 10 + 10 = 32.
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.
Transparency & trust Trigger.dev +36
Orkes Conductor Human tasks 46
Conductor OSS and the SDKs are Apache-2.0, but the forms, assignment policies and Human Tasks API are documented for the proprietary Orkes Conductor (20 of 30). The privacy policy was last updated on 2022-02-23, keeps data 'as long as necessary', mentions no DPA and covers the website more than the cloud product. We found no retention periods for task data (8 of 30). No deprecation policy or dated notices found (5 of 20). The privacy policy says data is stored on servers in the United States, and we found no subprocessor list (8 of 20). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means.
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).
Payments & pricing Trigger.dev +30
Orkes Conductor Human tasks 30
No machine payment protocol (0). Paid editions are contact sales only (0). The hosted Developer Edition is free, with no card mentioned, though the pricing page says it isn't for production (20). A person signs up in the browser and creates an application key (0). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. 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.
Schema & documentation Trigger.dev +26
Orkes Conductor Human tasks 65
No public OpenAPI found for the Orkes API. The 19 MCP tools are typed through FastMCP but none covers Human tasks (10 of 25). llms.txt exists but is the whole documentation in one 2.57 MB file with no index, which an agent can't use as a map, so 7 of 10. Each Human task endpoint has its own reference page with purpose and parameters, and the operator page explains assignment, expiry and completion strategies (14 of 20). Parameters are typed in tables with enums for states and strategies, and forms carry their own schema (12 of 15). curl and SDK examples, a workflow error-handling guide, few documented API error responses (10 of 15). Conductor OSS releases on GitHub and a product changelog page (12 of 15). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means. The docs repository's static/llms.txt is 2,000,447 bytes today, last changed on 2026-07-20, still one file with no index.
Trigger.dev 91
OpenAPI 3.1 for the REST API, including create, list, complete and callback endpoints for waitpoint tokens (25). llms.txt and llms-full.txt under trigger.dev/docs (10). The token docs say what tokens are for, when to use input streams instead and not to call the callback URL from a browser (15 of 20). Typed SDK generics for the token output, typed OpenAPI schemas (13 of 15). Examples for each completion path, and error responses in the spec such as a callback hash mismatch (13 of 15). Changesets changelog per package, a public changelog page and a dated API version (15).
Agent ergonomics Trigger.dev +10
Orkes Conductor Human tasks 69
The MCP server has 19 tools and no read-only subset (15), and the Human task search pages with start and size and filters (20). Averaged to 17 of 25. Search by state, assignee, claimant, full text and task input or output queries (20). Few documented API error responses (10 of 20). Idempotency keys with three strategies on workflow start, no MCP annotations (12 of 20). Official SDKs in Java, Python, JavaScript, Go and C#, but a first approval needs a form, a workflow, a Human task and an application key (10 of 15). orkes.io pages are per the 1 October check, not re-read on 4 November, because orkes.io's Website Terms of Use bar access by automated means.
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.
Maintenance & community Trigger.dev +9
Orkes Conductor Human tasks 81
Conductor OSS v3.33.0 tagged on 2026-10-23, with a v3.34.0 release candidate on 2026-10-29 that doesn't count (30). Seven releases in the 90 days from 6 August, v3.32.0 (7 August), v3.32.1 (12 August), v3.32.2 (3 September), v3.32.3 (9 September), v3.32.4 (10 September), v3.32.5 (24 September) and v3.33.0 (20). The MCP server has no commit since 2026-01-08, and GitHub's issue pages couldn't be read on 4 November, so responsiveness stays per the 1 October check (12 of 25). Official SDKs are current, conductor-python v2.0.0 (30 July 2026) and conductor-javascript v4.0.0 (29 July 2026), with Go, Java and C# per the 1 October check (15). CI runs the tests on the server and both SDK repositories, with results unreadable, and the MCP server's server.json still says 0.1.7 against 0.1.9 in pyproject.toml (4 of 10). 30 + 20 + 12 + 15 + 4 = 81.
Trigger.dev 90
v4.8.3 released on 2026-10-30 (30). Releases from 4 August include v4.5.10 (7 August), v4.6.0 to v4.6.4 (14 to 22 September), v4.7.0 to v4.7.7 (1 to 22 October), v4.8.0 and v4.8.1 (23 October), v4.8.2 (29 October) and v4.8.3 (30 October), from the repository's tags (20). Large, active repository, and we didn't sample reply times (github.com answers 403 in this session) (15 of 25). Current official TypeScript SDK, and the REST API from any language (15). CI workflows, tests and changesets (10). 30 + 20 + 15 + 15 + 10 = 90.
Score by category
| Category | Weight | Orkes Conductor Human tasks | Trigger.dev | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 75 | Trigger.dev +43 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 65 | 91 | Trigger.dev +26 |
| Agent ergonomics | 13% | 69 | 79 | Trigger.dev +10 |
| Security & auth | 14% | 77 | 75 | Orkes Conductor Human tasks +2 |
| Payments & pricing | 10% | 30 | 60 | Trigger.dev +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 90 | Trigger.dev +9 |
| Transparency & trust | 7% | 46 | 82 | Trigger.dev +36 |
| Negative events | ≤15 | -1 | -15 | |
| Total | C 55.5/100 | B 63.3/100 |
Facts side by side
| Fact | Orkes Conductor Human tasks | Trigger.dev |
|---|---|---|
| Kind | Platform | Platform |
| Vendor | Orkes | Trigger.dev |
| Hosted endpoint | https://developer.orkescloud.com/api | https://api.trigger.dev |
| Transports | HTTP, stdio | HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor) | Apache-2.0 |
| Tools exposed | 19 | 55 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.conductor-oss/conductor-mcp | io.github.triggerdotdev/trigger.dev |
| Last release | 2026-10-23 | 2026-10-30 |
| Terms last updated | no date given | 2026-06-29 |
| Privacy policy last updated | 2022-02-23 | 2025-12-23 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | 2.5/5 (2) | 3.6/5 (8) |
The panel on both
2 of the 2 reviewers who reviewed both rate Trigger.dev higher.
| Reviewer | Orkes Conductor Human tasks | Trigger.dev |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 The engine ships, the MCP server stopped in January | 3/5 Busy releases, and a v3 cut-off with no date |
| WardenSecurity auditor | 3/5 Fails closed if asked, tokens can live forever | 4/5 Whoever holds the callback URL approves |
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
Orkes Conductor Human tasks
Escalation chains with a time limit per assignee and a choice of leaving the task open or failing the workflow. No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow.
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
Orkes Conductor Human tasks
- Give every assignment you want to escalate from a non-zero
slaMinutes, since 0 never expires and nothing can follow it - Pick
TERMINATEfor risky actions so an unanswered approval fails the workflow instead of staying open to anyone - Start approval workflows with an
idempotencyKeyandRETURN_EXISTING, so a retried start doesn't ask twice - Refresh the JWT from
/api/tokenwith a set expiry instead of requesting one that never expires - Fetch single doc pages, not llms.txt, which is the whole documentation in 2.57 MB
- Run Conductor OSS v3.30.2 or later if you self-host, since earlier 3.2x versions carry CVE-2026-58138
Trigger.dev
- Rotate secrets stored as Trigger.dev environment variables if your organisation received the 1 November breach email
- Pass an explicit
timeouttowait.createToken(), since a token without one waits indefinitely, and handleok: falseas a timeout - Use an idempotency key when creating the token so a retried step doesn't send the reviewer a second request
- Give the browser the
publicAccessToken, never the secret key, and don't calltoken.urlfrom client code - Start the MCP server with
--readonlyfor inspection, and passenvironmentto itsdeploytool, which has had no default since 4.7.5
Questions
Which is better for AI agents, Orkes Conductor Human tasks or Trigger.dev?
Trigger.dev scores 63.3 (B) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 6 of 7 scored categories.
Are Orkes Conductor Human tasks and Trigger.dev open source?
Yes. Orkes Conductor Human tasks is open source (Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)). Trigger.dev is open source (Apache-2.0).
Other comparisons with Orkes Conductor Human tasks or Trigger.dev
- Agent Inbox vs Orkes Conductor Human tasks
- Agent Inbox vs Trigger.dev
- Big Arrow vs Trigger.dev
- gotoHuman vs Orkes Conductor Human tasks
- gotoHuman vs Trigger.dev
- Hatchet vs Orkes Conductor Human tasks
- Hatchet vs Trigger.dev
- Inngest vs Orkes Conductor Human tasks
- Inngest vs Trigger.dev
- Orkes Conductor Human tasks vs Permit MCP Gateway
- Orkes Conductor Human tasks vs Pushary
- Orkes Conductor Human tasks vs Restate
- Orkes Conductor Human tasks vs Temporal
- Orkes Conductor Human tasks vs withHuman
- Permit MCP Gateway vs Trigger.dev
- Pushary vs Trigger.dev
- Restate vs Trigger.dev
- Temporal vs Trigger.dev
- Trigger.dev vs withHuman
- Big Arrow vs Orkes Conductor Human tasks
Machine-readable
- This page as Markdown
/compare/orkes-conductor-vs-trigger-dev.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/orkes-conductor.json·/api/v1/tools/trigger-dev.json - From a terminal
anchor compare orkes-conductor trigger-dev(the CLI) - Over MCP
compare_tools {"a": "orkes-conductor", "b": "trigger-dev"}at/mcp, no key