# Hatchik help

Hatchik hosts the websites and apps you build by talking to Claude. This is
everything Hatchik knows about what goes wrong and what to do about it.

There is no support desk. There is no queue, no ticket and nobody to email about
a broken site. That is deliberate, and it only works because the answer is
always one of three things.

## The three things that fix almost everything

**1. Ask your AI.** Claude is connected to Hatchik and can look at your project,
read the error, read the logs, change the code and publish the fix — in the same
conversation you are already having. Say what you see, in your own words: "my
site is showing an error", "the booking form doesn't save anything", "it looked
fine yesterday". You do not need the right words for it.

**2. Undo.** Every time you make something live, Hatchik saves the version that
was live before, including your data. Say "undo that" or "put it back how it was
this morning" and your site goes back. You cannot break your live site
permanently.

**3. Download everything.** Your files, your database and your settings come out
as one file, any time, without asking anyone. Say "download everything from my
project" and you get a link.

## Pages

- [**What Hatchik is**](/docs/what-hatchik-is) — what you get, what it costs,
  what it does not do.
- [**Connecting Claude**](/docs/connect-claude) — the one-time setup, and what
  to do when it stops working.
- [**Draft and live**](/docs/draft-and-live) — how previewing and publishing
  work.
- [**Going back**](/docs/undo) — undo, and returning to an earlier version.
- [**Publishing failed**](/docs/publishing-failed) — the message said it did not
  work.
- [**My site is broken**](/docs/site-is-broken) — it published, but something is
  wrong.
- [**Keys, passwords and other settings**](/docs/app-settings) — how a key gets
  into your app without ever going through the chat, and why your draft and your
  live site keep separate ones.
- [**Bringing a site you already have**](/docs/bringing-a-site-over) — copying a
  site you own onto Hatchik, and what does not come with it.
- [**Your own web address**](/docs/custom-domain) — pointing a domain you own at
  your site.
- [**Your contact form**](/docs/contact-form) — where the messages go, why the
  form is off until your site has one, and what Hatchik turns away.
- [**Email your app sends to your customers**](/docs/email) — sign-up
  confirmations, password resets and receipts, choosing an email company, the
  three settings your web address needs, and what to do when one does not
  arrive.
- [**Letting people sign in to your app**](/docs/accounts) — accounts for your
  own customers, the forgotten-password link, where your customers actually
  live, and the one thing about undo that changes once people have accounts.
- [**Paying for Hatchik**](/docs/billing) — trials, prices, declined cards,
  paused projects.
- [**Your data**](/docs/your-data) — downloading it, losing it, deleting it.
- [**Locked out**](/docs/locked-out) — you cannot sign in.
- [**If a project is taken offline**](/docs/taken-offline) — what the publish
  check looks for, and how to put a site straight back.
- [**Limits**](/docs/limits) — the actual numbers.
- [**How apps run on Hatchik**](/docs/how-apps-run) — the technical contract,
  for your AI.

If you are deciding whether to trust any of this with a site real people use,
the page that answers that directly is
[what happens if the AI breaks your live site](/what-happens-if-the-ai-breaks-my-site.html)
— including the parts Hatchik cannot put back.

## When you need a person

`hello@hatchik.com` is read by a person, and only for these: a billing dispute,
a legal or data-protection request, or an abuse report. It is not a way to get
help with a broken site, and nobody there will look at your code. Everything
about your projects, your data and your money is something you can do yourself,
and this documentation says how.