Introduction
Hatch is an open-source help desk. It runs as one web app backed by Postgres and Redis, and you can use it on Hatch Cloud or host it yourself. Both run the same code.
Quickstart
Create a workspace, forward email and answer your first ticket.
OpsSelf-hosting
Docker Compose for a single server, Helm for Kubernetes.
AgentsAgent guide
Daily work in the inbox: views, macros, shortcuts and AI drafts.
What's newChangelog
Every release, with upgrade notes where something changed.
Quickstart
- Create a workspace. Sign up at hatch.dev/signup and pick a workspace name. It becomes your support address, for example
acme@in.hatch.dev. - Forward your support email. In your mail provider, forward
support@yourdomain.comto the workspace address. New mail shows up as tickets within seconds. - Invite your team. Agents are unlimited on every plan, so invite everyone who answers customers.
- Turn on AI drafts. Add a model key under Settings → AI and point Hatch at your help center. Drafts appear on new tickets right away.
Core concepts
Tickets and conversations
A ticket is one conversation with one customer. Every message, note, field change and automation run is an event on the ticket, so the timeline is a complete record.
Queues and views
Queues decide who owns a ticket. Views are saved filters anyone can make, like “Urgent billing, unassigned”. A ticket sits in one queue but can show up in many views.
SLAs
SLA policies set first-response and resolution targets per queue and priority. Timers pause on pending tickets and outside business hours if you choose.
Automations
Rules run on a trigger (ticket created, field changed, timer elapsed) and apply actions. Every rule has a dry run that replays the last 7 days of tickets.
API
Everything in the app is available through a typed REST and GraphQL API. Create a key under Settings → API.
curl https://api.hatch.dev/v1/tickets \
-H "Authorization: Bearer $HATCH_KEY" \
-d '{"subject":"Order 4821 arrived damaged","customer":{"email":"lee@example.com"},"queue":"orders"}'Extensions
Extensions are TypeScript packages in your own repo. Define ticket types, actions and integrations, then deploy with the CLI.
import { defineAction } from "@hatch/sdk";
export const refund = defineAction({
label: "Refund order",
fields: { orderId: "string", amount: "money" },
async run({ ticket, input, stripe }) {
await stripe.refunds.create({ payment_intent: input.orderId, amount: input.amount });
await ticket.note(`Refunded ${input.amount} on ${input.orderId}`);
},
});Building with an AI assistant? Hatch ships an MCP server, so Claude, ChatGPT and Cursor can read your ticket schema and write extensions against it.