hatchetvstemporal
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| hatchet | temporal | |
|---|---|---|
| Score | 72/100 | 82/100 |
| Rank in category | #8 of 31 in Workflow Automation | #1 of 1 in Workflow |
| GitHub stars | 8 331 | 24 539 |
| Stars, last 30 days | +192 | +729 |
| Stable releases, 12 months | 43 | 14 |
| Latest release | pi-durable/0.2.0 · 20 Nov 2026 | v1.32.2 · 2 Nov 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Go | Go |
Which one should you pick?
temporal scores 82/100 against 72/100 for hatchet, so it is the safer default.
hatchet ships more often: 43 stable releases in the past year, against 14 for temporal.
If you want the quickest setup, hatchet is easier to run; temporal needs more configuration.
temporal is growing faster right now (+729 stars in 30 days).
Key differences
- Platforms only hatchet lists: Helm.
- Platforms only temporal lists: Kubernetes.
- Features only hatchet lists: Automatic Retries, Background task queue, Concurrency controls, Cron and scheduled runs and 10 more.
- Features only temporal lists: Archival to blob storage, Durable workflow execution, Embedded server mode, gRPC API and 8 more.
hatchet details →temporal details →
Swap a project
Keep hatchet, compare it with
Keep temporal, compare it with