Docs  /  Getting started
01 — Getting started

From idea to live URL in five minutes.

No installs, no terminal, no setup. Sign in, type what you want in plain English, and the AI builds it. When it's ready you'll have a real web address you can share.

1

Make an account

Head to hatchable.com and sign up with your email. No credit card. The free tier covers everything you need to build, test, and share with people you invite. You only pay when you decide to put something on the open web.

If you've already got an account, you're done with this step. Open your console →

2

Pick how you want to talk to the AI

Two paths. Both end up at the same place — a live app on Hatchable. Pick whichever feels easier today; you can switch any time.

Easier · no setup

Use the built-in chat

Open your console, find the chat box, type. Hatchable's AI does the building. No installs, no configuration. Best for people who don't already have an AI tool they love.

Skip to step 3 if you're going this route.

For Claude / Cursor / Codex users

Point your own AI at Hatchable

Already using Claude Code, Cursor, ChatGPT, or Codex? Add Hatchable as a tool one time, then build from inside the AI tool you already use. Your chat history stays where you like it.

Continue with step 2½ below for the one-time setup.

Connect your AI to Hatchable (only if using your own AI)

Hatchable speaks MCP — a small open standard that lets AI tools call into other tools safely. Adding Hatchable takes one paste. Once it's done, your AI can create projects, write code, deploy them, and check that they work — all in the same conversation.

Claude & Claude Code · one-click setupAdd Hatchable to Claude → (URL + name pre-filled; click Add, then Connect on the row to start OAuth — one setup covers both surfaces) ChatGPT · chatgpt.com/apps#settings/Connectors/Advanced → Create appURL: https://hatchable.com/mcp Codex · Settings → MCP servers → Add server (Streamable HTTP)URL: https://hatchable.com/mcp Antigravity · ask the agent in chatAdd the https://hatchable.com/mcp MCP connector with OAuth. Cursor · one-click setup (Cursor 1.0+)Add Hatchable to Cursor → (OAuth handled on first connect, no token) Cursor (older versions) · ~/.cursor/mcp.json{ "mcpServers": { "hatchable": { "url": "https://hatchable.com/mcp", "headers": { "Authorization": "Bearer $HATCHABLE_TOKEN" } }}}

All five OAuth-capable clients (Claude, Claude Code, ChatGPT, Codex, Antigravity, plus Cursor 1.0+) handle sign-in via a browser tab — once the connector is added, click Connect on its row (or its equivalent: Authenticate in Codex, the OAuth prompt on first use in Cursor/Antigravity), approve on hatchable.com, and you're done. Claude Code shares its connectors list with Claude on the web, so one setup covers both. Cursor 1.0+ added OAuth over Streamable HTTP; older Cursor versions still need a static token from your API keys page in place of $HATCHABLE_TOKEN.

3

Tell the AI what to build

Whichever path you picked, the next step's the same. Describe the thing, who it's for, what matters most. Don't worry about being technical. The more specific you are about the use case, the better the first version comes out.

You
Build me a chore tracker for my kids on hatchable. Each kid has their own page where they can check off their daily chores. I want to see a weekly summary on my page showing who finished what.
→ I'll set up a small database with kids and chores, build a kid view and a parent view, and add the weekly summary. Give me about a minute.
The two-word signal: "on hatchable"

Tacking "on hatchable" onto the end of any prompt tells your AI to reach for the Hatchable tools rather than writing local files. It's the difference between "I'd like to talk about an app" and "please build this app right now." Use it once at the start of a session and your AI usually sticks with the platform from there.

The AI will ask a question or two if something's ambiguous ("how many kids?", "should chores reset weekly or daily?") — answer in plain English. It plans the whole thing, writes the code, sets up the database, and tests its own work before showing you anything.

4

Watch it deploy

You'll see a stream of "doing this, doing that" go by — making the database, writing pages, testing. When it's done you get a live URL like your-name.hatchable.site/chores. That's a real, working website you can open on your phone right now.

What you get out of the box

  • A live URL on the open internet, with HTTPS
  • A private database that holds your data
  • Login, if your app needs it (your kids signing in, etc.)
  • Email sending, if your app needs to send any
  • File uploads, scheduling, and more — only the things your app actually uses

All of it included. Nothing to configure. Nothing to bolt on. Hatchable handles every piece of plumbing so the AI can focus on building what you asked for.

5

Share it (or keep it to yourself)

By default your app is private — only you can see it. To bring others in, paste an email address or a Hatchable handle and pick "Can use" or "Can edit." They get an invite, sign in, and they're in. No seat limits. Invite your family, your team, your whole book club.

Want it on the open web instead? That's a one-click flip in the project settings — see Sharing & selling for what each option costs.

6

Change anything by talking

Forgot a feature? Spot a bug? Want a different color scheme? Go back to the chat box and say so. The AI rewrites the relevant pieces and redeploys. Every change is tracked, so if a new version breaks something you can roll back with one click.

You, two days later
Add a "missed chore" badge that shows up next to a kid's name when they've skipped something for two days in a row.
→ Done. Took 22 seconds. Open the parent view to see the new badge — Maya's got one already.

You're never stuck with the first version. The whole point is that you keep talking to it, and the app keeps getting closer to what you actually wanted.

Where to look in your console: the Code tab shows every file in your project plus a History sub-tab where each change is a labeled entry — the AI's request as the title, its plain-language summary as the body. Once you publish your site to the web, new changes land as drafts at your-app-draft.hatchable.site first, where only you and your collaborators can see them. You click Promote to live when each one's ready. Your live site stays untouched until you do.

That's the whole thing.

If you've got an idea right now — even a fuzzy one — you can have a working version of it before lunch.

Start building