# Hatchet > Hatchet is an open-source (MIT) platform for durable tasks, queues and workflows, sold as Hatchet Cloud or self-hosted. A durable task can pause until an event arrives, which is its building block for human approval steps. - Canonical: https://www.anchorterminal.com/tools/hatchet - Markdown: https://www.anchorterminal.com/tools/hatchet.md (~7,750 tokens) - Slim: https://www.anchorterminal.com/tools/hatchet.min.md (~1,780 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/hatchet.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade B · 68.3/100 · rank #225 of 950 · #4 in Human approval & handoff · not agent-ready · confidence medium** ## Assessment A durable task waits for a keyed event without holding a worker slot, and resumes from its event log after a restart, in Python, TypeScript, Go or Ruby. Hatchet supplies only the pause and resume. It has no approver inbox, notification channel or record of who answered, and its MCP server cannot push the event. ## Facts | Field | Value | | --- | --- | | Vendor | Hatchet Technologies, Inc. (https://hatchet.run) | | Kind | Model platform | | Category | Human approval & handoff (https://www.anchorterminal.com/categories/human-in-the-loop) | | Transport | HTTP, stdio | | Endpoint | `https://cloud.hatchet.run` | | Auth | API key · Self-serve. A person signs up at cloud.hatchet.run and creates an API token in Settings, scoped to one tenant with a configurable expiry. SDK clients, workers and the REST API send it as a Bearer token. The MCP server reads tokens from CLI profiles the user granted. Embedded mode runs a local engine with no token. | | Pricing | Freemium ($0.03 / 1k calls) · Hatchet Cloud is pay as you go from $0, and the plan without a card includes 1 million runs and 1 million events a month, capped at 2,000 of each a day, so an agent's owner can start without a contract. Beyond that, $30 per million runs and $5 per million events. Enterprise is priced by sales. Self-hosting is free under MIT (https://hatchet.run/pricing). | | x402 | No · No x402, MPP or L402 in the docs index, the OpenAPI file or the pricing page (checked 2026-10-09). | | Licence | MIT | | Tools exposed | 7 | | Packages | pypi: `hatchet-sdk`; npm: `@hatchet-dev/typescript-sdk`; go: `github.com/hatchet-dev/hatchet` | | Source | https://github.com/hatchet-dev/hatchet | | Docs | https://docs.hatchet.run/v1/durable-event-waits | | llms.txt | https://docs.hatchet.run/llms.txt | | Last release | 2026-10-08 | | How the pause works | A durable task calls the event wait with an event key. Hatchet writes a checkpoint, can evict the task from its worker slot, and re-queues it when a matching event arrives | | How the answer arrives | An event with the matching key and a JSON payload, pushed from an SDK, `POST /api/v1/tenants/{tenant}/events` or an incoming webhook. The wait returns the payload | | Timeouts | None on the event wait itself. Combine a sleep condition and an event condition in one or group, and the first to be satisfied resumes the task | | Channels | None built in. The owner sends the request over Slack, email or a web page and pushes the event with the reply | | Free tier | $0 without a card, 1 million runs and 1 million events a month, 2,000 runs and 2,000 events a day, 3 users, 1-day retention, per the pricing page | | Usage prices | $30 per million runs and $5 per million events after the included amounts. A failed run is billed, retries are not | | Limits | Default maximum payload 4 MB. Plan quotas for daily runs, worker slots and queue backlog. No request rate for the REST API was found in the reviewed documentation | | MCP server | Local, stdio, inside the Hatchet CLI (`hatchet mcp serve`). Seven tools, deny-by-default profile grants in `~/.hatchet/mcp-grants.yaml`, no tool annotations | | Credentials | API tokens per tenant with a configurable expiry, created and revoked in the dashboard or the API. Dashboard sign-in with Google or GitHub, SSO on the enterprise plan | | Roles | OWNER, ADMIN, MEMBER and read-only VIEWER, plus a per-member flag that hides payloads. API tokens are not restricted by either | | Audit | Audit logs on Business plans and above, 30 days, with actor, action, resource, IP address and time, read through the management API | | SDKs | Python `hatchet-sdk` 1.41.1 (24 September 2026), TypeScript `@hatchet-dev/typescript-sdk` 1.36.0, Go in the main module, Ruby 0.9.0 (5 October 2026), all MIT | | Regions | Control plane in AWS Oregon. Data plane live in Oregon, N. Virginia and Ireland, Sydney in private beta | | Certifications | SOC 2 Type II, HIPAA and GDPR per the docs security page. The trust centre at trust.hatchet.run is script-drawn and was not read | | Status | status.hatchet.run on Better Stack, three components (API, Hatchet Cloud, website) | | Capabilities | hitl.approve, hitl.ask, agent.durable, automation.workflows, automation.code | | Tags | hosted, self-hosted, open-source, freemium, free-tier, mcp, openapi, llms-txt, python, typescript, go, durable, webhooks, idempotency, hipaa | | JSON | https://www.anchorterminal.com/api/v1/tools/hatchet.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 66 | 13.2 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 85 | 13.8 | | Agent ergonomics | 13% | 16.2 | 82 | 13.3 | | Security & auth | 14% | 17.5 | 62 | 10.8 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 90 | 7.9 | | Transparency & trust (editorial 69, provenance 72) | 7% | 8.8 | 71 | 6.2 | | Negative events | up to −15 | up to −15 | Published 4 September 2026, -2. GHSA-992g-9cr3-vm5x (CVE-2026-88978), Moderate, CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. The `DurableTask` worker status path looked up durable event log entries by a caller-supplied task UUID with no tenant filter, so a holder of any tenant's token who knew another tenant's task UUID could read its entries. The advisory names Hatchet Cloud as affected and calls exploitation very unlikely because the IDs are random UUIDs. Fixed in 0.106.1. It is the event log this listing is graded on, so 2 points for a fixed path. https://github.com/hatchet-dev/hatchet/security/advisories/GHSA-992g-9cr3-vm5x (read through https://api.osv.dev/v1/vulns/GHSA-992g-9cr3-vm5x) Not deducted. GHSA-hf2m-86fv-rjw5, fixed in v0.110.5 on 5 October 2026, enforced payload visibility restrictions on endpoints that had returned payload data. The OSV mirror answered 404 for it, so its severity was not read. https://github.com/hatchet-dev/hatchet/blob/main/CHANGELOG.md | -2 | | **Total** | | | | **68.3 → B** | ### Why each score - Reliability 66: Graded as Hatchet Cloud, with the hosted lines. Status page at status.hatchet.run on Better Stack with three components (20). Its incident list, which reaches back to August 2026, shows one incident, about nine hours of elevated latency and delayed task processing on one shared shard in us-west-2 on 22 August 2026. Other shards and regions were unaffected, so we score it between minor and major (15 of 30). The pricing page gives plan quotas with numbers (2,000 runs a day without a card, worker slots, queue backlog) and the docs give a 4 MB payload limit, but no request rate for the API was found (8 of 15). The docs say which errors each SDK retries, the Go SDK honours `Retry-After` on 429, the OpenAPI file lists 429 on event creation, and idempotency keys are generally available (12 of 15). SLAs are named for the enterprise plan only and no SLA document is published (3 of 10). Event waits carry no beta label, the SDKs are 1.x except Ruby at 0.9.0, and the platform version is still 0.x (8 of 10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 85: OpenAPI 3.1 file in the repository with 147 operations, and typed inputs on all seven MCP tools (25). llms.txt on the docs host (10). The docs say when to use a durable task and when a DAG, and warn about determinism. The MCP tool descriptions are one line each and do not say when not to use a tool (14 of 20). Typed SDK signatures with an optional payload validator and 56 enums in the API schemas, but event data and MCP run input are free-form objects (11 of 15). Code samples in four languages. The API file has few examples, and no rendered REST reference was found in the docs index (10 of 15). Dated changelogs for the platform and each SDK, and `/api/v1/stable` paths (15). - Agent ergonomics 82: Seven compact MCP tools, and list endpoints with limit and offset (23 of 25). Events list by key, workflow, status and search text (18 of 20). Errors return a code, field, description and docs link, though no list of codes was found (14 of 20). Idempotency keys by TTL or status, and scope with a lookback window against a race between push and wait. No MCP tool sets `readOnlyHint` or `destructiveHint` (12 of 20). A wait needs only an event key, and there are official SDKs in four languages (15). - Security & auth 62: API tokens per tenant with a configurable expiry, created and revoked through the dashboard or API. No narrower scopes, and the docs say tokens are not restricted by role or payload visibility (20 of 30). A read-only VIEWER role, a per-member payload flag and deny-by-default profile grants for the MCP server, with no read-only token and no confirmation before `trigger_run` or `replay_run` (11 of 20). Event payloads from webhooks are untrusted content. Hatchet has payload validators, CEL filters and webhook checks by HMAC, API key or basic auth, and no prompt-injection guidance was found (8 of 15). Audit logs with actor, action, IP address and time on Business plans and above, kept 30 days. Event pushes are not among the documented actions (9 of 15). SECURITY.md with private GitHub advisories and security@hatchet.run, advisories published with CVE IDs, SOC 2 Type II, HIPAA and independent testing stated in the docs. No bug bounty (SECURITY.md says so), no security.txt, and the trust centre was not readable (14 of 20). - Payments & pricing 40: No machine payment protocol (0). Per-unit prices published without a login, $30 per million runs and $5 per million events (20). The pay-as-you-go plan starts at $0 without a card (20). A person signs up in the browser for the cloud. Embedded mode needs no account but is local software for development (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 90: Platform v0.110.19 tagged on 8 October 2026 (30). Tags on most working days in September and October, and five dated changelog entries between 25 August and 5 October (20). Issue reply times were not sampled. There is a Discord, a stale-issue workflow and a changelog (15 of 25). Current official SDKs, Python 1.41.1 on 24 September and Ruby 0.9.0 on 5 October 2026. The MCP server is not in the official registry (15). CI workflows for tests, each SDK, lint and an OSV scanner (10). - Transparency & trust 71: MIT (30). The privacy policy of 18 August 2026 gives retention periods (workflow logs up to 90 days, account data 12 months after closure) and the pricing page gives 1, 7 or 90 or more days by plan. No DPA or sub-processor list could be read, because the trust centre is script-drawn (18 of 30). No deprecation policy was found. The changelogs carry Removed sections, there are migration guides, and the cloud agreement gives 15 days' notice of price changes (8 of 20). CLI telemetry is disclosed with an opt-out, server analytics are settings, the privacy policy names PostHog and Google Ads without a full list, and regions are published (13 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/hatchet.md (JSON https://www.anchorterminal.com/fixes/hatchet.json) ### What we couldn't check - unchecked: the trust centre at trust.hatchet.run is script-drawn, so the SOC 2 report, DPA, sub-processor list and penetration test summaries were not read. - unchecked: GHSA-hf2m-86fv-rjw5. The OSV mirror answered 404 and GitHub's advisory page was not tried, so its severity and scope are known only from the changelog line. - unchecked: issue and pull request reply times, GitHub stars and package download counts. - unchecked: the domain's registration date, and whether the MCP server is in the official registry (no server.json is in the repository). - unchecked: the status page history before August 2026, and whether the incident list is complete for the 90 days. - The standard terms (Common Paper Cloud Service Agreement 2.1), as our reader summarised them, forbid security or vulnerability tests and allow aggregated usage data and customer content to be used for machine learning. Whether Hatchet's cover page changes either was not established. Recorded as a fact with no deduction, and it matters before any probe is run. - The audit log page says Business plans and above, while the pricing page lists audit logs only under the enterprise plan and shows no Business plan. - The pricing page lists 1 million runs a month as included on the plan without a card and also a limit of 2,000 runs a day. How the two interact was not established. - The lead named an MCP server among the interfaces. It exists, but it is a local operations tool for coding agents and cannot push the event that resumes a wait. - api.osv.dev answered 404 for robots.txt, so it publishes no rules. status.hatchet.run answered 200 with an empty file, and trust.hatchet.run answered its app page. ### Sources - home page and footer links: (seen 2026-10-09) - pricing page: (seen 2026-10-09) - cloud terms (Common Paper cover page): (seen 2026-10-09) - standard terms the cover page incorporates: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - docs index for agents: (seen 2026-10-09) - durable event waits: (seen 2026-10-09) - pushing events: (seen 2026-10-09) - MCP server docs: (seen 2026-10-09) - exposing tasks as agent tools: (seen 2026-10-09) - security page: (seen 2026-10-09) - audit logs: (seen 2026-10-09) - platform changelog: (seen 2026-10-09) - status page and incident list: (seen 2026-10-09) - repository at v0.110.19 (shallow clone): MCP tool source, OpenAPI file, SECURITY.md, CHANGELOG.md, the licence file, tags, SDK versions, and the docs sources for or groups, durable tasks, retries, roles, webhooks, regions, idempotency and CLI telemetry: (seen 2026-10-09) - advisory GHSA-992g-9cr3-vm5x through the OSV mirror: (seen 2026-10-09) ## Who's behind it (provenance 72/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Hatchet Technologies, Inc. | 20/20 | | Domain age | hatchet.run, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | cloud.hatchet.run | 15/15 | | Terms of service | read, states 3 of the 7 things a reader expects | 6.6/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.hatchet.run | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms page is a Common Paper Cloud Service Agreement cover page for Hatchet Technologies, Inc., last updated 17 July 2025, governed by Delaware law, incorporating Standard Terms Version 2.1 at commonpaper.com. The privacy policy was last updated 18 August 2026, covers workflow data and API usage data, and names an EU representative in Ireland. hatchet.run/.well-known/security.txt answered 404. SECURITY.md in the repository takes reports through private GitHub advisories or security@hatchet.run and says there is no bug bounty. The dashboard and API are at cloud.hatchet.run. The webhook docs show incoming webhook URLs on cloud.onhatchet.run, a second domain. status.hatchet.run runs on Better Stack with three components. Its robots.txt answered 200 with an empty body. The repository's licence file is MIT, copyright 2023 to present Hatchet Technologies Inc. The domain's registration date was not looked up. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://hatchet.run/policies/terms), read 2026-10-09, dated 2025-07-17, states 3 of the 7 things a reader expects. - Gives the date it was last updated. Last updated 2025-07-17. - Names the governing law or courts. The law of the State of Delaware. - Not found in the text. States a limit on its liability. - Not found in the text. Says how the agreement or account can be ended. - Says how changes to the terms are announced. Gives 15 days of notice before a change. - Not found in the text. Lists what users may not do. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). The order form is governed by key terms on the page and by the Cloud Service Agreement Standard Terms Version 2.1, incorporated by reference. "Framework Terms: This Order Form incorporates and is governed by the Framework Terms that are made up of the Key Terms below and the Hatchet Technologies, Inc. Cloud Service Agreement Standard Terms Version 2.1, which are incorporated by reference." - Also in the text (2026-10-08). Hatchet may change pricing with at least 15 days' notice, and the change applies from the next subscription period. "Provider may update Product pricing by giving at least 15 days notice to Customer (including by email or notification within the Product), and the change will apply in the next Subscription Period." - Also in the text (2026-10-08). Notice of non-renewal is due at least 30 days before the current subscription period ends. "Non-Renewal Notice Period: At least 30 days before the end of the current Subscription Period." **Privacy policy** (https://hatchet.run/policies/privacy), read 2026-10-09, dated 2026-08-18, states 8 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-08-18. - Says how long data is kept. Names a period of 12 months. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Says where data is transferred or stored. Relies on standard contractual clauses. ## Live (updated 2026-10-10 02:54 UTC) - Right now: up, HTTP 200, 598 ms, checked 2026-10-10 02:54 UTC (get on `https://cloud.hatchet.run`) - Uptime 24h 100.0% (115 probes) · 30 days 100.0% (115 probes) · p50 681 ms · p95 1.6 s - Vendor status page: unknown, no machine-readable status found - github `hatchet-dev/hatchet` v0.110.5, released 2026-10-06 - npm `@hatchet-dev/typescript-sdk` 1.36.0 - pypi `hatchet-sdk` 1.41.1, released 2026-09-24 - Watching changelog - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/hatchet.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Task runs after the first 1 million a month | $0.03 | per 1,000 tool calls | $30 per million runs. A failed run is billed, retries are not | | Events after the first 1 million a month | $0.005 | per 1,000 tool calls | $5 per million events | | Extra user beyond 50 (card on file) | $10 | per seat per month | | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - A durable task waiting on an event is evicted from its worker slot and resumes from the durable event log after a restart or crash - Events can be filtered with a CEL expression, and a scope with a lookback window catches an answer pushed before the wait began - MIT licence, self-hostable, with SDKs for Python (1.41.1), TypeScript (1.36.0), Go and Ruby (0.9.0) - Pay-as-you-go cloud plan starts at $0 without a card, with 1 million runs and 1 million events a month included, per the pricing page - Platform release v0.110.19 on 8 October 2026, with dated changelogs for the platform and each SDK ## Weaknesses - No approver inbox, Slack or email channel, routing or reminder. The owner builds the request and the way the answer is pushed - An event wait has no timeout of its own. A deadline needs a sleep condition in the same or group - API tokens are scoped to a tenant with an expiry, with no narrower scopes, and the role and payload restrictions do not apply to them - Audit logs are for Business plans and above, kept 30 days, and the documented actions do not include event pushes - The seven MCP tools trigger, inspect and replay runs. None pushes an event, and none sets a read-only or destructive annotation - The standard terms the cloud agreement incorporates forbid security or vulnerability tests of the product. This matters before any probe is run ## Before you call it (notes for agents) 1. Put the approval wait in a durable task, and keep API calls, database reads and random values in child tasks, because the code between checkpoints is replayed 2. Add a sleep condition in the same or group as the event condition to set a deadline, and treat the sleep firing first as a timeout 3. Give the event a scope and the wait a lookback window when the answer can arrive before the wait starts. Both must be set together 4. Filter with a CEL expression such as `input.user_id == '1234'` so one approval key cannot resume another request's task 5. Push the answer with the SDK's event push or `POST /api/v1/tenants/{tenant}/events`. The MCP server has no tool for it 6. Grant the MCP server one profile with `hatchet mcp auth --grant `. It refuses profiles that were not granted ## Connect Install: ```bash pip install hatchet-sdk ``` Claude Code: ```bash hatchet mcp install --target claude-code ``` MCP client configuration: ```json { "mcpServers": { "hatchet": { "args": [ "mcp", "serve" ], "command": "hatchet" } } } ``` ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Temporal | BB | 77.2 | 22 | hitl.approve, hitl.ask, agent.durable, automation.workflows, automation.code | no | https://www.anchorterminal.com/tools/temporal.md | | Trigger.dev | BB | 74.7 | 67 | hitl.approve, hitl.ask, agent.durable, automation.workflows, automation.code | no | https://www.anchorterminal.com/tools/trigger-dev.md | | Restate | BB | 73.3 | 90 | hitl.approve, hitl.ask, agent.durable, automation.workflows, automation.code | no | https://www.anchorterminal.com/tools/restate.md | | Inngest | B | 66 | 304 | hitl.approve, hitl.ask, agent.durable, automation.workflows, automation.code | no | https://www.anchorterminal.com/tools/inngest.md | | Orkes Conductor Human tasks | C | 54 | 696 | hitl.approve, hitl.ask, agent.durable, automation.workflows | no | https://www.anchorterminal.com/tools/orkes-conductor.md | | Pipedream API + MCP | B | 65.5 | 315 | automation.workflows, automation.code | no | https://www.anchorterminal.com/tools/pipedream.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Event waits are `ctx.aio_wait_for_event()` in Python, `ctx.waitForEvent()` in TypeScript, `ctx.WaitForEvent()` in Go and `ctx.wait_for()` with `Hatchet::UserEventCondition` in Ruby (source: ) - The docs call event waits the foundation for human-in-the-loop workflows, and give sleep plus event in one or group as the way to put a deadline on a response (source: ) - Lookback windows need a scope on both the wait and the pushed event. The Ruby SDK does not support them yet (source: ) - Events arrive from an SDK, the REST API (`event:create` in the OpenAPI 3.1 file, 147 operations) or an incoming webhook checked by basic auth, an API key header or HMAC (source: ) - The CLI's local MCP server, added in v0.107.0 on 15 September 2026, has seven tools (`trigger_run`, `get_run`, `list_run_events`, `list_workers`, `replay_run`, `engine_status`, `submit_feedback`) and uses only CLI profiles the user granted (source: ) - `submit_feedback` sends its arguments, the deployment type and the CLI version to Hatchet's PostHog project (source: ) - Idempotency keys (TTL-based or status-based, from a CEL expression) became generally available in v0.101.27 on 17 August 2026 (source: ) - Two security advisories were fixed in the last 90 days. GHSA-992g-9cr3-vm5x (CVE-2026-88978, Moderate), a missing tenant filter on durable event log lookups, fixed in 0.106.1. GHSA-hf2m-86fv-rjw5, payload visibility not enforced on some endpoints, fixed in v0.110.5 (source: ) - The cloud terms are a Common Paper Cloud Service Agreement cover page, last updated 17 July 2025, that incorporates Standard Terms Version 2.1 (source: ) - The status page shows one incident since August 2026, about nine hours of elevated latency on one shared shard in us-west-2 on 22 August 2026 (source: ) - #4 of 10 in Best human approval and handoff for AI agents: https://www.anchorterminal.com/best/human-in-the-loop/index.md - All 45 human approval comparisons: https://www.anchorterminal.com/compare/human-in-the-loop/index.md ## Compare - [gotoHuman vs Hatchet](https://www.anchorterminal.com/compare/gotohuman-vs-hatchet.md): E 43.6 vs B 68.3 - [Hatchet vs Inngest](https://www.anchorterminal.com/compare/hatchet-vs-inngest.md): B 68.3 vs B 66 - [Hatchet vs Orkes Conductor Human tasks](https://www.anchorterminal.com/compare/hatchet-vs-orkes-conductor.md): B 68.3 vs C 54 - [Hatchet vs Permit MCP Gateway](https://www.anchorterminal.com/compare/hatchet-vs-permit-mcp-gateway.md): B 68.3 vs C 54.1 - [Hatchet vs Pushary](https://www.anchorterminal.com/compare/hatchet-vs-pushary.md): B 68.3 vs D 51.4 - [Hatchet vs Restate](https://www.anchorterminal.com/compare/hatchet-vs-restate.md): B 68.3 vs BB 73.3 - [Hatchet vs Temporal](https://www.anchorterminal.com/compare/hatchet-vs-temporal.md): B 68.3 vs BB 77.2 - [Hatchet vs Trigger.dev](https://www.anchorterminal.com/compare/hatchet-vs-trigger-dev.md): B 68.3 vs BB 74.7 - [Hatchet vs withHuman](https://www.anchorterminal.com/compare/hatchet-vs-withhuman.md): B 68.3 vs D 51.8 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on hatchet.run or one of its subdomains, or the README of github.com/hatchet-dev/hatchet. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "hatchet", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Hatchet on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Hatchet on Anchor Terminal](https://www.anchorterminal.com/badges/hatchet.svg)](https://www.anchorterminal.com/tools/hatchet) ``` Plain link: ```html Hatchet on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Hatchet is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/hatchet-dark.png - Light: https://www.anchorterminal.com/assets/share/hatchet-light.png