Compare

Hatchet vs Riverqueue

Hatchet scores higher on the AgentReady, 66/100 against 45/100. They differ on 10 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Hatchet. Hatchet is a developer platform that helps engineering teams build and deploy mission-critical AI agents, durable workflows, and background tasks.

Riverqueue. Fast and reliable background jobs in Go.

Where Hatchet is ahead

Hatchet passes clear product positioning and mcp discoverable, and Riverqueue does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds adopt: self-service signup, fast time to first request and mcp integration available. Riverqueue misses those.

And on operate, idempotency support, observable execution and agent compatibility verified. Riverqueue misses those.

Where Riverqueue is ahead

Riverqueue passes cli available, and Hatchet does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.

It also holds operate: retry behavior documented. Hatchet misses it.

What neither does

Both fail structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, agent-compatible signup flow, programmatic credential creation, structured, predictable output, machine-readable errors, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover. Hatchet leads 100 to 73. Hatchet misses nothing; Riverqueue misses clear product positioning, mcp discoverable.

Understand. Both sit at 31/100 here. Hatchet misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented; Riverqueue misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented.

Adopt. Hatchet leads 75 to 48. Hatchet misses agent-compatible signup flow, programmatic credential creation, cli available; Riverqueue misses self-service signup, agent-compatible signup flow, programmatic credential creation, fast time to first request, mcp integration available.

Operate is whether an agent can run against it in production and recover when a call fails. Hatchet leads 59 to 29. Hatchet misses structured, predictable output, machine-readable errors, retry behavior documented, rate-limit behavior predictable; Riverqueue misses structured, predictable output, machine-readable errors, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified.

Pricing

Hatchet starts at $0/mo and has a free tier. Riverqueue does not publish one and has a free tier.

Signal by signal

Which to pick

Hatchet clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Hatchet and Riverqueue. Alternatives to each: Hatchet, Riverqueue.

An agent can fetch this as data: POST /v1/compare {"slugs": ["hatchet", "riverqueue"]}