Why Hatch.
Support is too important to rent
Your support desk holds every complaint, workaround and promise your company has made. We think that history should live somewhere you control.


How we got here.
Help desks stopped working for the people using them
The big suites priced every agent, every add-on and now every AI answer. The lightweight tools broke the moment volume arrived. Teams were left choosing between expensive and fragile.
We ran support ourselves
Hatch started as the internal desk for a 40-person support team that could not justify another seat price rise.
Then we opened it up
Other teams asked for it, so we released the code. Two years later it handles more than a hundred million tickets a year.
What we believe.
Four ideas behind every release
Read every line
The whole desk is on GitHub under AGPL-3.0, including the AI reply engine. Nothing important is hidden behind an enterprise build.
Your data, your servers
Self-host anywhere, or use Hatch Cloud and export everything in one archive whenever you want.
No seat tax
Cloud plans are priced per workspace. Adding the tenth agent costs the same as adding none.
Drafts, not autopilot
AI writes the first version and shows its sources. A person decides what reaches your customer.
Compared.
Hatch next to the usual options
| Hatch | Per-seat suites | Shared inboxes | |
|---|---|---|---|
| Pricing | Per workspace or free | Per agent, plus AI per resolution | Per user |
| Where data lives | Your cloud or ours, exportable | Vendor servers | Vendor servers |
| Custom workflows | Point and click, or code | Admin panels, paid tiers | Limited |
| Source code | Open, AGPL-3.0 | Closed | Closed |
| Scales to | Millions of tickets | Millions of tickets | A few hundred a day |
