Head to head · Human approval · October 2026 research run
Inngest vs Orkes Conductor Human tasks
Inngest scores 73.1 (BB) 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
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.
Ahead on
- Reliability, 72 against 32
- Schema & documentation, 89 against 65
- Agent ergonomics, 76 against 69
- Payments & pricing, 60 against 30
- Maintenance & community, 88 against 81
- Transparency & trust, 54 against 46
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
Best for Teams that already orchestrate agents as Conductor workflows and need formal routing, per-assignee deadlines and escalation without writing them.
Also in its favour
- Runs on your own machine
- Open source
Watch for
No built-in Slack or email prompt, so alerts need a trigger policy and a second workflow
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 Inngest +40
Inngest 72
Status page at status.inngest.com (incident.io) with component history (20). Its feed lists 14 incidents from 10 August to 20 October, and each one hit part of the service. Degraded or delayed function execution on 10, 19 and 20 August, 4 and 18 September (the latter labelled partial outage, 16:31 to 18:33 UTC), 26 September and 9, 10 and 12 October (the 9 October one a 44-minute Rackspace network outage), Connect routing delays for "a subset of customers using Inngest Connect" on 24 and 26 August, delayed observability on 20 August and 26 September, and intermittent Event API errors on 20 October (updates from 13:07 to 13:20 UTC, components marked affected until 15:33 UTC, labelled degraded performance). The 7 and 16 July incidents behind the earlier 5 have left the 90-day window. Minor incidents only (20 of 30). Plan limits are published with numbers (concurrency, queue depth, event size, 5,000 events per send), but no request rate for the event or REST API (10 of 15, per the 1 October check). The OpenAPI spec documents 429 on /events and invoke, event IDs deduplicate for 24 hours and functions take idempotency keys, with no Retry-After guidance found (12 of 15, per the 1 October check). No SLA on the pricing page, which mentions only support response SLAs (0). step.waitForEvent(), step.waitForSignal() and the Cloud MCP are GA (10).
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.
Payments & pricing Inngest +30
Inngest 60
No machine payment protocol (0). Per-execution prices published, $50 per million over the Pro allowance, tiering down to $15 per million (20). Free plan of 50,000 executions a month with no card (20). A person signs up in the browser for Cloud (0). The local Dev Server runs without an account, but the rubric scores the hosted option. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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.
Schema & documentation Inngest +24
Inngest 89
OpenAPI 3.0.3 for REST API v2, 35 paths, at api-docs.inngest.com/api-specs/v2.json (25). llms.txt on the main site and the API docs, plus llms-full.txt and a .md copy of each API page (10). The wait docs say when to use waitForSignal instead of waitForEvent and spell out the race where an early answer is missed (15 of 20). Typed SDKs in TypeScript, Python and Go. The if match is a CEL string (12 of 15). Many code examples and 429 and error responses in the spec (12 of 15). Dated changelog, release notes that flag breaking changes, and versioned v1 and v2 APIs (15).
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.
Transparency & trust Inngest +8
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.
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.
Agent ergonomics Inngest +7
Inngest 76
The Cloud MCP has 34 tools (14 shared with the Dev Server, 20 Cloud-only) (5), while REST v2 responses can be sized with cursor pagination and optional output (20). We average the two surfaces to 12 of 25. Runs list with app, function, status and time filters (20). SDK error classes for non-retriable and retry-after cases and error responses in the spec (14 of 20). Event-ID deduplication, function idempotency keys and step memoisation, and the MCP docs mark which tools change state, though we didn't confirm annotations in the tool definitions (15 of 20). A wait needs an event name, a timeout and a match, and official SDKs cover TypeScript, Python and Go (15).
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.
Maintenance & community Inngest +7
Inngest 88
TypeScript SDK 4.26.2 on 29 October 2026 (30). Since 3 August, 15 TypeScript SDK releases (4.15.0 to 4.26.2), server releases v1.42.0 to v1.49.0 and changelog entries on 7 August, 12 August and 6 October (20). Responsiveness per the 1 October check, not re-read on 1 November (GitHub's pages and API refuse us), with 55 open issues and 182 open pull requests on the server repository, reply times not sampled (15 of 25). Current official SDKs in TypeScript, Python (0.5.19 stable, 0.5.20a1 on 30 October) and Go (15). CI badge on main and a Node 20 floor (8 of 10).
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.
Score by category
| Category | Weight | Inngest | Orkes Conductor Human tasks | Edge |
|---|---|---|---|---|
| Reliability | 16% | 72 | 32 | Inngest +40 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 65 | Inngest +24 |
| Agent ergonomics | 13% | 76 | 69 | Inngest +7 |
| Security & auth | 14% | 74 | 77 | Orkes Conductor Human tasks +3 |
| Payments & pricing | 10% | 60 | 30 | Inngest +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 81 | Inngest +7 |
| Transparency & trust | 7% | 54 | 46 | Inngest +8 |
| Negative events | ≤15 | -1 | -1 | |
| Total | BB 73.1/100 | C 55.5/100 |
Facts side by side
| Fact | Inngest | Orkes Conductor Human tasks |
|---|---|---|
| Kind | Platform | Platform |
| Vendor | Inngest | Orkes |
| Hosted endpoint | https://inn.gs/e/ | https://developer.orkescloud.com/api |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | SSPL with delayed Apache-2.0 (server), Apache-2.0 (SDKs) | Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor) |
| Tools exposed | none | 19 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.conductor-oss/conductor-mcp |
| Last release | 2026-10-29 | 2026-10-23 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | couldn't be read | 2022-02-23 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | 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) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Inngest | Orkes Conductor Human tasks |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Long waits on a server that breaks in minors | 2/5 The engine ships, the MCP server stopped in January |
| WardenSecurity auditor | 2/5 The event key sits in the URL path | 3/5 Fails closed if asked, tokens can live forever |
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.
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.
Before you call either
Inngest
- Use
step.waitForSignal()when one run waits for one answer, andwaitForEventonly when one answer resumes many runs - Register the wait before you send the approval request, or check the external state first, since early events are missed
- Use a unique approval ID per tool call and
matchon it, so parallel approvals resolve independently - Treat
nullorundefinedas a timeout and decide on purpose whether that rejects, approves or escalates - Ask for a read-only OAuth session for the Cloud MCP when you only inspect runs; write tools return
insufficient_scopewithout write permission
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
Questions
Which is better for AI agents, Inngest or Orkes Conductor Human tasks?
Inngest scores 73.1 (BB) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 6 of 7 scored categories.
Are Inngest and Orkes Conductor Human tasks open source?
No open-source release is listed for Inngest. Orkes Conductor Human tasks is open source (Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)).
Other comparisons with Inngest or Orkes Conductor Human tasks
- Agent Inbox vs Inngest
- Agent Inbox vs Orkes Conductor Human tasks
- Big Arrow vs Inngest
- gotoHuman vs Inngest
- gotoHuman vs Orkes Conductor Human tasks
- Hatchet vs Inngest
- Hatchet vs Orkes Conductor Human tasks
- Inngest vs Permit MCP Gateway
- Inngest vs Pushary
- Inngest vs Restate
- Inngest vs Temporal
- Inngest vs Trigger.dev
- Inngest vs withHuman
- 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 Trigger.dev
- Orkes Conductor Human tasks vs withHuman
- Big Arrow vs Orkes Conductor Human tasks
Machine-readable
- This page as Markdown
/compare/inngest-vs-orkes-conductor.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/inngest.json·/api/v1/tools/orkes-conductor.json - From a terminal
anchor compare inngest orkes-conductor(the CLI) - Over MCP
compare_tools {"a": "inngest", "b": "orkes-conductor"}at/mcp, no key