Head to head · Human approval · October 2026 research run
Inngest vs Pushary
Inngest scores 73.1 (BB) on agent readiness against Pushary's 58.5 (C), and leads in 5 of 7 scored categories. Pushary leads on agent ergonomics and transparency & trust. 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 42
- Schema & documentation, 89 against 83
- Security & auth, 74 against 66
- Payments & pricing, 60 against 15
- Maintenance & community, 88 against 63
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
Pushary C
Best for One developer running coding agents unattended who wants questions and approvals on a phone.
Ahead on
- Agent ergonomics, 86 against 76
- Transparency & trust, 76 against 54
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.
Payments & pricing Inngest +45
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.
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.
Reliability Inngest +30
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).
Pushary 42
No public status page found (0) and no incident history (5). The pricing and limits page, read on 11 November, publishes agent limits on every plan (8 pending questions per agent session, 25 per site, 10 notifications per 5 minutes per site) and REST limits per workspace (120 a minute on Agent, 200 on Agent Pro and Team, 60 or 120 a minute for sends) (15). Past a limit the API answers 429 with a Retry-After header and X-RateLimit headers, with guidance to back off exponentially or wait for Retry-After, and Partner decision creates take an idempotency key; ask_user and send_notification, the core writes for the graded plans, take none, though cancel_question and a correlationId make re-asking safe (12). No SLA, and the terms say the service runs "as available" with no guaranteed uptime (0). The hosted server carries no beta label (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.
Maintenance & community Inngest +25
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).
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.
Transparency & trust Pushary +22
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.
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.
Agent ergonomics Pushary +10
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).
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.
Security & auth Inngest +8
Inngest 74
Since 6 October 2026 the Cloud MCP and the CLI sign in with OAuth, where the user approves the account, environment access, read or write permissions and session duration, and new sk-inn-api API keys carry read or write permissions and can be limited to one environment. Event and signing keys stay per environment with a documented rotation procedure. That's scoped, revocable credentials (30), less 5 because the environment-wide event key travels in the URL path of inn.gs/e/<key> (a path secret lands in the same logs a query string does, so we departed from the query-string wording of the rule; a per-request capability URL scoped to one wait gets no deduction). 25 of 30. Read-only OAuth sessions and API keys give a least-privilege mode on every plan, OAuth sessions can't read event or signing keys, and the MCP docs say to review state-changing tool calls before approving them. Role-based access is still Enterprise only (14 of 20, level with langfuse's four fixed permission sets). It returns your own run data and the payload of the answering event (10). Run traces kept 24 hours on Free up to 90 days on Enterprise, audit trails on Enterprise only (8 of 15). SOC 2 Type II, a paid bounty for qualifying reports, a security@ address with an age key, yearly penetration tests and a SECURITY.md, per the 1 October check. No security.txt at www.inngest.com (404 on 1 November). The SDK's one advisory, GHSA-2jf5-6wwv-vhxx, was published with a fix (17 of 20).
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 | Inngest | Pushary | Edge |
|---|---|---|---|---|
| Reliability | 16% | 72 | 42 | Inngest +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 83 | Inngest +6 |
| Agent ergonomics | 13% | 76 | 86 | Pushary +10 |
| Security & auth | 14% | 74 | 66 | Inngest +8 |
| Payments & pricing | 10% | 60 | 15 | Inngest +45 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 88 | 63 | Inngest +25 |
| Transparency & trust | 7% | 54 | 76 | Pushary +22 |
| Negative events | ≤15 | -1 | -3 | |
| Total | BB 73.1/100 | C 58.5/100 |
Facts side by side
| Fact | Inngest | Pushary |
|---|---|---|
| Kind | Platform | MCP server |
| Vendor | Inngest | Pushary |
| Hosted endpoint | https://inn.gs/e/ | https://pushary.com/api/mcp/mcp |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, SSE (legacy) |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | SSPL with delayed Apache-2.0 (server), Apache-2.0 (SDKs) | MIT (skill, hooks and adapters) |
| Tools exposed | none | 26 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.Pushary/pushary |
| Last release | 2026-10-29 | 2026-11-04 |
| Terms last updated | no date given | 2026-09-27 |
| Privacy policy last updated | couldn't be read | 2026-09-28 |
| 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 | Pushary |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Long waits on a server that breaks in minors | 2/5 Weekly syncs, no release notes, no status page |
| WardenSecurity auditor | 2/5 The event key sits in the URL path | 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
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.
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
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
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, Inngest or Pushary?
Inngest scores 73.1 (BB) on agent readiness against Pushary's 58.5 (C), and leads in 5 of 7 scored categories. Pushary leads on agent ergonomics and transparency & trust.
Can an agent call Inngest and Pushary without installing anything?
Yes. Inngest has a hosted endpoint at https://inn.gs/e/ and Pushary at https://pushary.com/api/mcp/mcp.
Other comparisons with Inngest or Pushary
- Agent Inbox vs Inngest
- Agent Inbox vs Pushary
- Big Arrow vs Inngest
- Big Arrow vs Pushary
- gotoHuman vs Inngest
- gotoHuman vs Pushary
- Hatchet vs Inngest
- Hatchet vs Pushary
- Inngest vs Orkes Conductor Human tasks
- Inngest vs Permit MCP Gateway
- Inngest vs Restate
- Inngest vs Temporal
- Inngest vs Trigger.dev
- Inngest vs withHuman
- Orkes Conductor Human tasks vs Pushary
- Permit MCP Gateway vs Pushary
- Pushary vs Restate
- Pushary vs Temporal
- Pushary vs Trigger.dev
- Pushary vs withHuman
Machine-readable
- This page as Markdown
/compare/inngest-vs-pushary.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/inngest.json·/api/v1/tools/pushary.json - From a terminal
anchor compare inngest pushary(the CLI) - Over MCP
compare_tools {"a": "inngest", "b": "pushary"}at/mcp, no key