Hatchet

Hatchet is a self-hostable orchestration engine that schedules and executes background tasks, AI agents, and durable workflows for Python, TypeScript, Go, and…

  • AI
  • Automation
Hatchet is a self-hostable orchestration engine that schedules and executes background tasks, AI agents, and durable workflows for Python, TypeScript, Go, and Ruby applications.

Platform availability

Available on 2 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 8 days ago
Popular
788,274 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
8,274
Open issues
138
Last commit
2026-11-13
Latest release
v0.114.2
License
MIT
Activity
rising

Checked 8 days ago - source: GitHub (hatchet-dev/hatchet)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install the CLI, then start the server First install the Hatchet command-line tool with the provided install script, then check it with hatchet --version. Docker must already be installed, because without it you cannot launch the Hatchet server your workers connect to. source
  • Make a starter worker project After the server is running, use hatchet quickstart to choose your language and package manager and create a sample worker project. This gives you a working starting folder; without it you may not have the boilerplate your tasks need to connect. source
  • Confirm your worker connected After starting your worker, look for logs that say it is starting hatchet, waiting for tasks, or sending heartbeats. If you do not see these, the worker probably cannot reach the server, so your jobs will not run. source

Fetched 8 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Hatchet recommend trying its cloud service even if I plan to self-host?

Yes. The README says to sign up for Hatchet Cloud even if you plan on self-hosting, so you can see what a fully deployed platform looks like.

What part of the system do I operate when self-hosting Hatchet?

Self-hosting means running your own instance of the Hatchet Control Plane. It manages workflows, schedules tasks, and coordinates worker execution.

What durability layer does self-hosted Hatchet use?

It uses Postgres as the durability layer for both the task runtime and the observability system.

What long-running issue has been reported for self-hosted Hatchet?

A bug report says the self-hosted engine can completely break after around 4-7 days of active use. It stops assigning tasks, stops updating workflow statuses, and spams context deadline exceeded errors.

Could self-hosting avoid an enterprise license?

A commenter says if the project manages upgrades and patching well, some companies may see ROI from running a self-hosted instance rather than paying for an enterprise license.

Answers sourced from docs.hatchet.run, github.com, github.com, www.reddit.com

Community

Collected 8 days ago - public community threads