head to head · open source
Temporal vs Hatchet
Temporal has 24,138 GitHub stars, 2,068 forks, 956 open issues and last shipped yesterday. Hatchet has 8,214 stars, 528 forks, 135 open issues and last shipped yesterday. Temporal leads on adoption by 194% (24,138 vs 8,214 stars). Temporal is written in Go under MIT; Hatchet is written in Go under MIT. Temporal has attracted 9% as many forks as stars, Hatchet 6%. Hatchet was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (distributed-systems, durable-execution, golang), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Temporal | Hatchet | |
|---|---|---|
| GitHub stars | ★ 24K | ★ 8.2K |
| License | MIT | MIT |
| Written in | Go | Go |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 2.1K | ⑂ 528 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Temporal if
- You weight community size — 24K stars and counting
- You want the MIT license terms
- Your stack matches Go
- You value the larger contributor base for long-term maintenance
pick Hatchet if
- You want the Hatchet feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Go
- You evaluated both and Hatchet fits your workflow better
About Temporal
Temporal—durable execution platform Introduction • Getting Started • Contributing • Temporal Docs • Temporal 101 Introduction Temporal is a durable execution platform that enables developers to build scalable applications without sacrificing productivity or reliability. The Temporal server executes units of application logic called Workflows in a resilient manner that automatically handles intermittent failures, and retries failed operations. Temporal is a mature technology that originated as a fork of Uber's Cadence. It is developed by Temporal Technologies, a startup by the creators of…
read the full Temporal overview →
About Hatchet
An orchestration engine for background tasks, AI agents, and durable workflows Hatchet Cloud · Documentation · Website · Issues What is Hatchet? Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. It supports applications written in Python, TypeScript, Go and Ruby, and can be used as a service through Hatchet Cloud or self hosting. Hatchet provides a full platform for queuing, automatic retries, durability, real time monitoring, alerting, and logging. Get started quickly The fastest way to get started with Hatchet is signing up for Hatchet Cloud to try it out! We…
read the full Hatchet overview →
More in Infrastructure & Operations
Related comparisons
More Orchestration & Scheduling projects
Compare either of these against the rest of the Orchestration & Scheduling field.
Frequently asked questions
Is Temporal or Hatchet more popular?
Temporal has 24,138 GitHub stars and Hatchet has 8,214. Temporal has the larger community by that measure.
Are Temporal and Hatchet free?
Both are open source. Temporal is licensed under MIT and Hatchet under MIT. Neither carries a licence fee.
What is the difference between Temporal and Hatchet?
Temporal is written in Go and Hatchet in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Temporal or Hatchet?
Choose Temporal if you want the larger community (24,138 stars) or its MIT licence terms. Choose Hatchet if its feature set, stack or MIT licence fits better. Both are self-hostable.