Head to head · Human approval · October 2026 research run
Orkes Conductor Human tasks vs Pushary
Pushary scores 58.5 (C) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 4 of 7 scored categories. Orkes Conductor Human tasks leads on security & auth, payments & pricing and maintenance & community. 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 66
- Payments & pricing, 30 against 15
- Maintenance & community, 81 against 63
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
Pushary C
Best for One developer running coding agents unattended who wants questions and approvals on a phone.
Ahead on
- Reliability, 42 against 32
- Schema & documentation, 83 against 65
- Agent ergonomics, 86 against 69
- Transparency & trust, 76 against 46
Watch for
No free agent plan, and the 3-day trial needs a card
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 Pushary +30
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.
Pushary 76
Closed hosted service under Estonian law with terms updated 1 November 2026, and MIT-licensed skill and adapters (18 of 30). The privacy policy, updated 29 October 2026, says a pending question is cached in Redis for ten minutes or until its deadline, at most 24 hours, that session history is on by default with transcripts redacted and encrypted on the user's machine and recoverable by Pushary compliance admins for legal obligations, that code isn't written to the audit trail, and that the plan's retention window (30 days on Agent to 365 on Team) sets what the dashboard shows while older records aren't deleted automatically. A data processing relationship is described for subscriber data; no DPA document was found (25 of 30). The changelog's deprecation policy says breaking changes are announced at least 90 days in advance, with migration guides (20). Sub-processors are named with what each processes (Clerk, Neon, Vercel, Railway, Redis, Stripe, Resend, PostHog and others) (20). 18 + 25 + 20 + 20 = 83.
Schema & documentation Pushary +18
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.
Pushary 83
The hosted server's tool list wasn't read, since nothing is sent to MCP endpoints in this re-check. The tool reference documents each tool's arguments with types and required flags, and the REST API has an OpenAPI 3.1 file linked from llms.txt (15 of 25, the earlier partial kept). llms.txt, Markdown copies of the docs and the skill files are written for agents (10). Per the 1 October reading of the skill, it states when to ask, when to notify and when not to (20). Arguments carry types, ranges such as 1 to 100 for limit, enums such as the flow status, and required flags; question type is an enum of confirm, select and input, and select takes 2 to 6 options (10 of 15). Examples for each tool, and the outcome states (pending, cancelled, expired, missing, unavailable) documented with what to do next (13 of 15). A dated service changelog, versions per component (CLI, Mac app, phone app, SDKs, Hermes plugin) and URL versioning at /api/v1/ with 12 months of security updates for the previous version (15). 15 + 10 + 20 + 10 + 13 + 15 = 83.
Maintenance & community Orkes Conductor Human tasks +18
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.
Pushary 63
The service changelog's newest entries are dated 4 November 2026, covering CLI 1.9.61 to 1.9.100, Pushary for Mac 0.1.104 to 0.1.127, Server SDK 2.5.1, Python SDK 2.4.1 and Hermes plugin 0.9.2 (30). Since 13 August the changelog has entries for 1 to 5 October, 15 October and two for 4 November, and the CLI changelog has its own notes per release (20). Public issues welcome, and we didn't sample replies (8 of 25). The repository's server.json names io.github.Pushary/pushary, but no registry page was read, and a vendor's own server.json is a claim, not presence (0). The skill mirror holds docs and config only, and the adapters carry tests (5 of 10, the earlier partial kept). 30 + 20 + 8 + 0 + 5 = 63.
Agent ergonomics Pushary +17
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.
Pushary 86
The tool reference lists 26 tools, but each key gets a subset. A Claude or ChatGPT connector gets 6, the key setup creates gets 7, and full-access keys add the subscriber, campaign, template and flow tools, with four Partner decision tools on Partner and Enterprise plans. 15 for 11 to 30 tools plus 10 back for per-key toolsets (25). List tools take limit and cursor, flows filter by status, and wait: false and timeoutMs shorten a question (20). Every result carries answered, status and handoffAction, and over-limit errors name the limit (18 of 20). cancel_question, a correlationId and Partner idempotency keys make retries safe, and annotations weren't read (8 of 20). Few required parameters, and official SDKs in TypeScript and Python (15). 25 + 20 + 18 + 8 + 15 = 86.
Payments & pricing Orkes Conductor Human tasks +15
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.
Pushary 15
No machine payment protocol (0). Public plan prices, Agent at $9.99 a month with 5,000 notifications, Agent Pro $19.99, Team $59 for 5 people and Partner Launch, Growth and Scale at $99, $299 and $799 a month, but no per-call price (10). The pricing page says there is no free agent plan, and the 3-day trial needs a card added to start (0). Setup needs a person to pair a phone and start a paid account (0). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Security & auth Orkes Conductor Human tasks +11
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.
Pushary 66
Bearer API keys in the form pk_xxx.sk_xxx, which setup writes after pairing a phone by QR code and fingerprint. The docs describe key kinds with different reach (connector, agent setup and full-access keys, and keys bound to one end user that can only create, read and cancel that user's decisions), but no rotation procedure was found (20 of 30). Enforced gates through Claude Code and Hermes hooks, and propose_scope with allowed and off-limits paths on supported hosts; an agent key can't switch phone approvals off. Plain MCP clients get cooperative questions only (15 of 20). Per the 1 October check, the skill says a text answer containing yes isn't approval for a separate action (12 of 15). The audit trail records each question, the tool, who decided, when and on which surface (12 of 15). SECURITY.md in the skill repository is a disclosure policy with a 48-hour acknowledgement for that repository, and the changelog names an address for vulnerability reports on the service with no stated time. No security.txt (404 on 11 November), bounty or certification of Pushary's own; OSV lists no advisory for pushary (7 of 20). 20 + 15 + 12 + 12 + 7 = 66.
Score by category
| Category | Weight | Orkes Conductor Human tasks | Pushary | Edge |
|---|---|---|---|---|
| Reliability | 16% | 32 | 42 | Pushary +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 65 | 83 | Pushary +18 |
| Agent ergonomics | 13% | 69 | 86 | Pushary +17 |
| Security & auth | 14% | 77 | 66 | Orkes Conductor Human tasks +11 |
| Payments & pricing | 10% | 30 | 15 | Orkes Conductor Human tasks +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 63 | Orkes Conductor Human tasks +18 |
| Transparency & trust | 7% | 46 | 76 | Pushary +30 |
| Negative events | ≤15 | -1 | -3 | |
| Total | C 55.5/100 | C 58.5/100 |
Facts side by side
| Fact | Orkes Conductor Human tasks | Pushary |
|---|---|---|
| Kind | Platform | MCP server |
| Vendor | Orkes | Pushary |
| Hosted endpoint | https://developer.orkescloud.com/api | https://pushary.com/api/mcp/mcp |
| Transports | HTTP, stdio | Streamable HTTP, SSE (legacy) |
| Auth | API key | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Apache-2.0 (Conductor OSS and SDKs), proprietary (Orkes Conductor) | MIT (skill, hooks and adapters) |
| Tools exposed | 19 | 26 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.conductor-oss/conductor-mcp | io.github.Pushary/pushary |
| Last release | 2026-10-23 | 2026-11-04 |
| Terms last updated | no date given | 2026-09-27 |
| Privacy policy last updated | 2022-02-23 | 2026-09-28 |
| 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 | not found in the text |
| 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) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Orkes Conductor Human tasks | Pushary |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 The engine ships, the MCP server stopped in January | 2/5 Weekly syncs, no release notes, no status page |
| WardenSecurity auditor | 3/5 Fails closed if asked, tokens can live forever | 3/5 Enforced only where the hooks run |
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.
Pushary
Pushary's hosted MCP server lets an agent ask a person on their phone and wait for the answer, with 26 documented tools in per-key subsets, published rate limits with Retry-After, and a dated changelog. There's no free agent plan and the trial needs a card, plain MCP clients get cooperative questions only, and there's no status page or SLA.
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
Pushary
- Read
answered,statusandhandoffActionon every result, and never treat a timeout as approval - Expect
ask_userto return at once withanswered: falsewhen the user's mode is notify-only or terminal-only - Poll
wait_for_answeronce, then follow the handoff instead of looping - Cancel a live question with
cancel_questionbefore asking the same thing in chat - Expect 403
subscription_requiredfromsend_notification,ask_userandpropose_scopewhen the workspace has no active plan
Questions
Which is better for AI agents, Orkes Conductor Human tasks or Pushary?
Pushary scores 58.5 (C) on agent readiness against Orkes Conductor Human tasks's 55.5 (C), and leads in 4 of 7 scored categories. Orkes Conductor Human tasks leads on security & auth, payments & pricing and maintenance & community.
Can an agent call Orkes Conductor Human tasks and Pushary without installing anything?
Yes. Orkes Conductor Human tasks has a hosted endpoint at https://developer.orkescloud.com/api and Pushary at https://pushary.com/api/mcp/mcp.
Are Orkes Conductor Human tasks and Pushary 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 Pushary.
Other comparisons with Orkes Conductor Human tasks or Pushary
- Agent Inbox vs Orkes Conductor Human tasks
- Agent Inbox vs Pushary
- Big Arrow vs Pushary
- gotoHuman vs Orkes Conductor Human tasks
- gotoHuman vs Pushary
- Hatchet vs Orkes Conductor Human tasks
- Hatchet vs Pushary
- Inngest vs Orkes Conductor Human tasks
- Inngest vs Pushary
- Orkes Conductor Human tasks vs Permit MCP Gateway
- 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
- Permit MCP Gateway vs Pushary
- Pushary vs Restate
- Pushary vs Temporal
- Pushary vs Trigger.dev
- Pushary vs withHuman
- Big Arrow vs Orkes Conductor Human tasks
Machine-readable
- This page as Markdown
/compare/orkes-conductor-vs-pushary.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/orkes-conductor.json·/api/v1/tools/pushary.json - From a terminal
anchor compare orkes-conductor pushary(the CLI) - Over MCP
compare_tools {"a": "orkes-conductor", "b": "pushary"}at/mcp, no key