Skip to content

Runtimes & workflows

Durabull vs Hatchet

Hatchet is closer to Temporal than to Bull Board: you run workers, and Hatchet runs the orchestration engine. It is MIT-licensed and can be self-hosted. On 2026-09-29, Hatchet Cloud moved to pay-as-you-go pricing and retired its Team, Starter, and Growth plans.

Hatchet website ↗3 primary references
System map
Your applicationProducers & workers
enqueue / process
Redis + BullMQQueue state & job lifecycle
runtime
inspect / operate
DurabullDashboard · alerts · MCP
operations
A runtime changes how jobs execute. A dashboard changes how you operate them.
The case for Hatchet

Choose Hatchet when you want durable task orchestration with workers you control, Cloud or MIT self-hosting, and published per-task pricing that excludes retries. A Hatchet run and a Temporal Action are different billing units.

The case for Durabull

Stay on Redis + BullMQ. Durabull is the operations layer: queue discovery, alerts, and MCP. It is Apache-2.0 open source for self-hosting, and the hosted dashboard is free to start. Redis, workers, and their operation remain your responsibility.

Capabilities

The details that change the decision

Compare the documented deployment modes. “Not documented” means we did not find a vendor claim, not proof that a capability is impossible. Check the primary sources.
Durabull versus Hatchet feature comparison
FeatureDurabullHatchet
1M task runsFree to start + your infrastructure$0 (included)
10M task runsFree to start + your infrastructure$270 (9M × $30/M)
100M task runsFree to start + your infrastructure$2,970 list
Monitors BullMQYesNo

Setup

How Hatchet connects

You adopt the Hatchet SDK. Your workers connect to Hatchet Cloud or a self-hosted engine.

Application changes. Yes if you leave BullMQ.

Queue discovery
N/A.
Environments
Tenants on Hatchet Cloud (10 on pay-as-you-go), not Redis environments.
Alerts
Hatchet’s own platform monitoring. Not BullMQ alert rules.
AI & MCP
Official CLI MCP server (hatchet mcp install). Tools trigger, inspect, and replay Hatchet runs. Profile access is deny-by-default until granted.

Economics

Understand what you are paying for

Different products, different cost boundaries. Durabull’s hosted app is free to start and covers its dashboard. Redis, worker compute, storage, networking, and operational work remain yours. A runtime’s usage charges may cover orchestration or compute. The prices here are not a total-cost or savings benchmark.
Hatchet pricing
As of 2026-10-20, with a card on file: 1M task runs and 1M events free every month, then $30 per million runs and $5 per million events. Failed runs count; retries do not. Without a card: 2,000 runs and 2,000 events per day. Custom plans for 100M+ runs offer volume discounts that are not published.
Hatchet license
MIT open source. Cloud is commercial.
Durabull
Hosted dashboard is free to start. Redis, worker compute, and infrastructure operations remain your costs. Check the pricing page for current terms. Apache License 2.0 (OSI-approved open source). Self-host on your own infrastructure.
Hatchet Cloud pay-as-you-go task-run charges with a card on file, as of 2026-10-20; assumes events stay within the 1M free. Storage, logs, worker compute, and volume discounts are excluded. Durabull’s free-to-start hosted dashboard also excludes Redis, workers, and operations.
VolumeRuntime / product chargesDurabull hosted feeUnit
1M runs$0Free to start + your infrastructuretask run
10M runs$270Free to start + your infrastructuretask run
100M runs$2,970 listFree to start + your infrastructuretask run

Hatchet Cloud pay-as-you-go task-run charges with a card on file, as of 2026-10-20; assumes events stay within the 1M free. Storage, logs, worker compute, and volume discounts are excluded. Durabull’s free-to-start hosted dashboard also excludes Redis, workers, and operations.

Questions about Hatchet and Durabull

Do Hatchet retries cost extra?

Per Hatchet’s pricing FAQ, retries are not billed: a task that fails and is retried counts as one run. Failed runs do count, and a task spawned by another task is a second run.

Evidence

Sources & methodology

Reviewed against vendor documentation, public pricing, and source repositories. This is a documentation comparison, not a hands-on benchmark. Vendor docs may describe different editions or deployment modes; confirm those details before purchasing.

Durabull details: product documentation, pricing, and MCP reference. Found a change? Send a correction.

Continue your research

Practical guides

Explore Hatchet alternatives →

Connect Redis. Queues appear.

Inspect your Redis-backed BullMQ queues in one place. Hosted Durabull is free to start.