Head to head · Human approval · October 2026 research run
Orkes Conductor Human tasks vs Restate
Restate scores 74 (BB) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 6 of 7 scored categories. Orkes Conductor Human tasks leads on security & auth. 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.
Ahead on
- Security & auth, 77 against 61
Also in its favour
- A hosted endpoint, with nothing to install
- 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
Restate BB
Best for A team that already writes agent steps as durable handlers and wants a long, cheap wait for a human answer in TypeScript, Python, Java, Go or Rust, with the option to self-host.
Ahead on
- Reliability, 96 against 32
- Schema & documentation, 85 against 65
- Agent ergonomics, 81 against 69
- Payments & pricing, 60 against 30
- Maintenance & community, 92 against 81
- Transparency & trust, 53 against 46
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
No reviewer inbox, Slack app or email. The approval request and the reply endpoint are the builder's code
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 Restate +64
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.
Restate 96
Graded as Restate Cloud, the hosted service, with the hosted lines. Status page at status.restate.dev (incident.io) with two components and a 90-day window (20). The incidents feed, re-read on 1 November, still lists nothing after the 36-minute Cloud UI outage of 16 July 2026, which is outside the 90-day window that starts on 3 August, so the record is clean (30). Throughput is published per plan, from 10 actions a second with bursts to 100 on Free up to 500 with bursts to 2,000 on Premium, per the 8 October check (15). The ingress docs, re-read on 1 November, say which calls are safe to retry, name 408, 425, 429 and 5xx as retryable, and take an Idempotency-Key header with a 24-hour retention. No Retry-After guidance was found (13 of 15). The pricing table, re-read on 1 November, lists 99.9 per cent on Starter, Business and Premium and 99.99 per cent on Enterprise and multi-AZ Premium, but no SLA document was found and the terms say availability can't be guaranteed (8 of 10). Restate Cloud, awakeables and the server at 1.8 (1.8.1 since 21 October) are generally available (10).
Payments & pricing Restate +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.
Restate 60
No machine payment protocol (0). Per-unit prices are public on restate.dev/pricing, re-read on 1 November, $25 per million extra actions on Starter and Business and $15 on Premium, though the table is drawn by script and read from the page's script bundle (20). Free plan of 100,000 actions a month, and the pricing FAQ says no credit card is required (20). A person signs up in the browser for Restate Cloud (0). The server also runs locally with no 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.
Schema & documentation Restate +20
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.
Restate 85
OpenAPI 3.1 for the Admin API, 25 paths in the 1.8.0 document read on 1 November (the 17 October note's 28 was wrong), at docs.restate.dev/schemas/openapi-admin.json, and the server generates an OpenAPI 3.1 definition for each registered service. Server 1.8.0 of 14 October extends that per-service document to the call, send, attach, output and status routes and makes the Admin document work with client generators, but the release notes don't name the routes that resolve and reject awakeables, which stay documented in prose with curl examples (20 of 25). llms.txt, llms-full.txt, a .md copy of every page and a docs MCP server at docs.restate.dev/mcp (10). The external-events page compares signals, awakeables and workflow promises in one table with what each is for, and the approval guide lists the five steps of the pattern, per the 8 October check (16 of 20). Typed SDKs in five language families, with the awakeable payload typed by the caller and sent as JSON (12 of 15). The approval guide has working code for seven agent SDKs plus timeouts, and there is an error-code reference and the x-restate-error-source header (12 of 15). Semantic versioning with dated changelogs for the server and each SDK, and the 1.8.0 and 1.8.1 entries list their breaking changes with migration guidance (15).
Security & auth Orkes Conductor Human tasks +16
Orkes Conductor Human tasks 77
Application access keys with roles and per-resource read and execute permissions, swapped for a JWT at /api/token. The JWT expiry is configurable, and a negative value means it never expires (25 of 30). RBAC, application roles, assignment to named users or groups, and a TERMINATE strategy that fails the workflow when nobody answers (18 of 20). It returns form answers from assigned reviewers (10). Human task states and history are kept per task, and the Audit Logs page (in the docs repository since 12 August 2026, v5.5.0 and later) records who created, updated or deleted 21 resource types, HUMAN_TASK and ACCESS_KEY among them. It's off by default, switched on through Orkes support, visible to administrators only and doesn't cover task runs (12 of 15). Conductor OSS's SECURITY.md routes reports through GitHub's private advisory form, with no acknowledgement time (7), and the pricing page names SOC 2 Type II for Enterprise per the 1 October check. No bounty found and security.txt unread (12 of 20). 25 + 18 + 10 + 12 + 12 = 77.
Restate 61
Graded as Restate Cloud. API keys (key_...) are created per environment with a role and sent as a Bearer token. The docs show Full and Admin roles and we couldn't read the full list or the revocation controls in the Cloud UI (22 of 30). No documented way to put the key in a query string. Roles on keys, private services that the ingress won't expose, request signing with an ED25519 key so services accept calls only from their environment, and teams with RBAC, with SAML SSO and SCIM on Premium and Enterprise. Nothing asks for confirmation before an Admin key kills or purges an invocation (12 of 20). It returns the caller's own data and the approver's payload (10). Each invocation's journal is visible in the UI and by SQL for 1 day on Free up to 30 days on Premium, and OTEL export starts at Business. No log of who resolved an awakeable was found (8 of 15). The trust centre at trust.restate.dev, re-read on 1 November, says Restate has completed a SOC 2 Type 1 audit and is in the observation period for Type 2, as the BYOC docs say, and a HIPAA BAA is sold as an add-on. restate.dev/.well-known/security.txt still returns 404 on 1 November, the server repository has no SECURITY.md, and no bounty or published advisory was found (9 of 20). The self-hosted server is weaker by design, since the docs say its ingress and admin ports carry no authentication and expect a proxy in front. Server 1.8.0 drops client-supplied x-restate-* headers at the ingress so ingress metadata can't be spoofed, and 1.8.1 updates rustls and rustls-webpki for six RUSTSEC advisories in those libraries.
Agent ergonomics Restate +12
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.
Restate 81
No MCP server for operating Restate was found, so the surface is the HTTP ingress and Admin API. Resolving an awakeable sends one JSON value and returns almost nothing, and run state is read with SQL through the introspection API, where the caller chooses columns and limits (18 of 25). SQL filters over invocations and state, with no cursor pagination found on the Admin list routes (15 of 20). x-restate-error-source separates handler errors from ingress errors, the docs name the retryable status codes, and a rejection can carry an error code (16 of 20). Idempotency-Key on calls and sends with 24-hour retention by default, attach and output routes that are safe to retry, and an awakeable that resolves or rejects once. MCP annotations don't apply (17 of 20). ctx.awakeable() takes no arguments, and official SDKs cover TypeScript, Python, Java and Kotlin, Go and Rust (15).
Maintenance & community Restate +11
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.
Restate 92
Server v1.8.1 tagged on 21 October 2026 and v1.7.14 on 22 October, after v1.8.0 on 14 October, and the TypeScript SDK reached 1.18.1 on 31 October (30). The server has 20 tags in the 90 days from 3 August (v1.7.3-rc.1 to v1.7.14), the TypeScript SDK four since 9 October (1.17.3, 1.17.4, 1.18.0, 1.18.1) and the Python SDK two (1.1.0 on 21 October, 1.2.0 on 28 October) (20). The server repository had 352 open issues and 105 open pull requests on 8 October, and of eight issues opened from 2 to 8 October, three were closed within three days and two more had replies. GitHub's pages and API answered 403 on 17 October and 1 November, so this stands per the 8 October check (18 of 25). Current official SDKs for TypeScript (1.18.1), Python (1.2.0, 28 October), Java and Kotlin, Go and Rust (15). CI, end-to-end and SDK integration checks passed on the latest main commit read on 8 October, with one cancelled run, not re-read since. Both SDKs added a GitHub Actions lockfile on 28 October (9 of 10).
Score by category
| Category | Weight | Orkes Conductor Human tasks | Restate | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 96 | Restate +64 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 65 | 85 | Restate +20 |
| Agent ergonomics | 13% | 69 | 81 | Restate +12 |
| Security & auth | 14% | 77 | 61 | Orkes Conductor Human tasks +16 |
| Payments & pricing | 10% | 30 | 60 | Restate +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 92 | Restate +11 |
| Transparency & trust | 7% | 46 | 53 | Restate +7 |
| Negative events | ≤15 | -1 | -3 | |
| Total | C 55.5/100 | BB 74/100 |
Facts side by side
| Fact | Orkes Conductor Human tasks | Restate |
|---|---|---|
| Kind | Platform | Platform |
| Vendor | Orkes | Restate GmbH |
| Hosted endpoint | https://developer.orkescloud.com/api | no (local only) |
| Transports | HTTP, stdio | HTTP |
| Auth | API key | API key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor) | BSL 1.1 converting to Apache-2.0 four years after release (server), MIT (SDKs) |
| Tools exposed | 19 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.conductor-oss/conductor-mcp | not listed |
| Last release | 2026-10-23 | 2026-10-31 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2022-02-23 | no document linked |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 4.5k stars, 329k npm/wk, 76k PyPI/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (4) |
The panel on both
The one reviewer who reviewed both, Keel, rates Restate higher.
| Reviewer | Orkes Conductor Human tasks | Restate |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 The engine ships, the MCP server stopped in January | 3/5 One minor version at a time, with ingress paths moved in 1.7 |
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.
Restate
An awakeable pauses a handler at no compute cost and resumes it from one HTTP request, with a durable timeout, on a free plan of 100,000 actions a month. Restate sends nothing to the approver, so the Slack message, email or inbox is the builder's code, and the published terms and privacy statement predate the paid plans.
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
Restate
- Create the awakeable, send its ID inside
ctx.run, then await the promise, so a retry doesn't send a second approval request - Resolve with
POST /restate/awakeables/<id>/resolveand a JSON body, or/rejectwith a text reason, which throws a terminal error in the handler - On Restate Cloud send
Authorization: Bearer key_...tohttps://<env_id>.env.<region>.restate.cloud:8080. On a self-hosted server put an authenticating proxy in front of port 8080 - Wrap the wait in
orTimeoutand decide what a timeout means. Without it the handler waits with no limit - Retry ingress errors only on 408, 425, 429 or 5xx, and only when
x-restate-error-sourceisn'tinvocation. Pin the CLI version in scripts that parse its--jsonoutput
Questions
Which is better for AI agents, Orkes Conductor Human tasks or Restate?
Restate scores 74 (BB) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 6 of 7 scored categories. Orkes Conductor Human tasks leads on security & auth.
Are Orkes Conductor Human tasks and Restate open source?
Orkes Conductor Human tasks is open source (Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor)). No open-source release is listed for Restate.
Other comparisons with Orkes Conductor Human tasks or Restate
- Agent Inbox vs Orkes Conductor Human tasks
- Agent Inbox vs Restate
- Big Arrow vs Restate
- gotoHuman vs Orkes Conductor Human tasks
- gotoHuman vs Restate
- Hatchet vs Orkes Conductor Human tasks
- Hatchet vs Restate
- Inngest vs Orkes Conductor Human tasks
- Inngest vs Restate
- Orkes Conductor Human tasks vs Permit MCP Gateway
- Orkes Conductor Human tasks vs Pushary
- Orkes Conductor Human tasks vs Temporal
- Orkes Conductor Human tasks vs Trigger.dev
- Orkes Conductor Human tasks vs withHuman
- Permit MCP Gateway vs Restate
- Pushary vs Restate
- Restate vs Temporal
- Restate vs Trigger.dev
- Restate vs withHuman
- Big Arrow vs Orkes Conductor Human tasks
Machine-readable
- This page as Markdown
/compare/orkes-conductor-vs-restate.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/orkes-conductor.json·/api/v1/tools/restate.json - From a terminal
anchor compare orkes-conductor restate(the CLI) - Over MCP
compare_tools {"a": "orkes-conductor", "b": "restate"}at/mcp, no key