Hatchet vs Upstash
Upstash scores higher on the AgentReady, 72/100 against 66/100. They differ on 5 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.
Upstash. Serverless data platform providing Redis, Vector database, messaging, workflow orchestration, and secure cloud containers for AI agents.
Where Hatchet is ahead
Hatchet passes idempotency support, and Upstash does not. That is operate, whether an agent can run against it in production and recover when a call fails.
Where Upstash is ahead
Upstash passes authentication documented, and Hatchet does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.
It also holds adopt: cli available. Hatchet misses it.
And on operate, retry behavior documented and rate-limit behavior predictable. Hatchet misses those.
What neither does
Both fail structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, agent-compatible signup flow, programmatic credential creation, structured, predictable output, machine-readable errors. 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.
Understand. Upstash leads 38 to 31. Hatchet misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented; Upstash misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented.
Adopt. Upstash leads 80 to 75. Hatchet misses agent-compatible signup flow, programmatic credential creation, cli available; Upstash misses agent-compatible signup flow, programmatic credential creation.
Operate is whether an agent can run against it in production and recover when a call fails. Upstash leads 71 to 59. Hatchet misses structured, predictable output, machine-readable errors, retry behavior documented, rate-limit behavior predictable; Upstash misses structured, predictable output, machine-readable errors, idempotency support.
Pricing
Hatchet starts at $0/mo and has a free tier. Upstash starts at $0/mo and has a free tier.
| Hatchet plans | Upstash plans |
|---|---|
| Developer $0/mo +usage | Free $0 |
| Team $500/mo +usage | Pay as you go $0.2 per 100K commands |
| Scale $1,000/mo +usage | Fixed 250MB $10/month |
| Enterprise Custom | Fixed 1GB $10/month |
| - | Fixed 5GB $10/month |
| - | Fixed 10GB $10/month |
| - | Fixed 50GB $10/month |
| - | Fixed 100GB $10/month |
| - | Fixed 500GB $10/month |
| - | Enterprise Custom |
Signal by signal
| Signal | Hatchet | Upstash |
|---|---|---|
| AgentReady | 66 | 72 |
| Discovery | 100 | 100 |
| Understanding | 31 | 38 |
| Adoption | 75 | 80 |
| Operability | 59 | 71 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Unknown | Unknown |
| CLI | Unknown | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Upstash clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Hatchet and Upstash. Alternatives to each: Hatchet, Upstash.
An agent can fetch this as data: POST /v1/compare {"slugs": ["hatchet", "upstash"]}