Got an idea?
We'll get it launched.

Yes. The code repository is created under your GitHub account on day one. The domain is registered in your name. The server is rented to your account. If you cancel, you walk away with all of it. No obfuscation, no licensing tricks, no hostage situations.

Cancel any time. We hand over the server keys, you keep the GitHub repo, the domain stays in your name, and your customers' data is yours. You can keep running everything yourself afterwards for roughly £10–15/month total (a small server, the domain renewal, transactional email). No exit fee, no data extraction charges.

Your product code (anything you build inside the */product/ folders and your own database migrations) is yours, full stop — licence it however you want. The substrate code Hatchik provides is released under Business Source License 1.1. Plain English: you can use it for your own product anywhere forever, modify it, fork it, share it with your team, hire developers, sell to your own customers — all fine. The only thing you can't do is offer it to third parties as a competing "Hatchik-like service". After three years the substrate converts to Apache 2.0 automatically — fully open, no strings, no exceptions. The full text lives in the LICENSE file inside your sandbox repo.

Hatchik is built for you. The product owners we have in mind are lawyers, restaurateurs, consultants, designers — people with a clear app idea but no infrastructure background. You'll drive an AI helper (Cursor, Windsurf, Claude Code, Cline, Codex, Antigravity or similar) to build the actual features, and we make sure that experience is safe — your AI can't accidentally break things, and you stay in charge of what launches. If you've never used an AI coding tool before, we walk you through it after signup.

£89 one-time when you launch (covers your domain, hosting account, mailboxes, and full configuration — done in minutes). Then £14/month while you're getting your first users. After your 15th sign-up the monthly graduates to £39 — because by then you've got traction. You'll get an email a month before the change. The free Sandbox stays free forever; you only start paying when you want a real domain.

Prices on this page are shown in GBP for reference, but checkout auto-detects your country and shows you the equivalent in your local currency — USD, EUR, AUD, INR, BRL, AED and 25+ others. VAT (UK / EU), GST (Australia / India / Singapore), US state sales tax, and other local taxes are calculated and added automatically at checkout, with a proper tax invoice emailed to you. Customers in lower-income regions get an automatic purchasing-power discount applied. You never have to work out what the right amount is — your local price, with your local tax, in your local currency.

Hatchik uses Paddle as our Merchant of Record — a well-trodden model used by many global SaaS products. Paddle is the legal seller, which means they handle all the boring tax compliance globally so we don't pass that cost (or complexity) on to you. The practical effect: your bank statement will read "Paddle.com Market Ltd · Hatchik". Your subscription, login, app, and support all stay with Hatchik — only the billing entity differs. Refunds run through Paddle and usually land within 5–10 days.

Hatchik works equally well whether you're selling to paying customers, building an internal tool for your team, running a community project, or just making the thing you've always wanted to exist. Stripe payments are wired in but optional — flip them on if you ever want to charge, leave them off if you don't. The Stage 2 graduation at 15 sign-ups is based on real people using your app, not on revenue, so the pricing works the same way whether you're monetising or not.

No — and this one is non-negotiable. We build the iOS and Android shells from your code, ready to submit. You handle the submission itself, because the apps live on your store accounts under your legal identity. That means you'll need an Apple Developer Program account (~£99/year) and a Google Play Console account (~£25 one-time), and you're responsible for the listing metadata (description, screenshots, keywords, age rating), compliance with each store's review guidelines, privacy declarations (App Tracking Transparency, the Data Safety form), staged rollouts, and responding to review feedback. We're happy to advise on common rejection reasons and what each store looks for, but we don't press submit on your behalf. See §5.3 of our product spec for the full list.

You can take an on-demand Postgres snapshot any time from Supabase Studio (a couple of clicks) and download it locally — handy before any risky migration. We also run Hetzner Cloud snapshots of your VPS on demand on Launch + Growth; ask and we'll take one. If you'd rather we ran a Postgres snapshot for you, email hello@hatchik.com and we'll do it the same day. Growth tier ships with extended retention on snapshots we hold.

Yes. The easiest path is the website wizard at hatchik.com/start — a couple of fields and a button. Once you've connected Hatchik to Cursor, Windsurf, Claude Code, Cline, Codex, or Antigravity (instructions at hatchik.com/install), your AI tool can also manage your project from chat — deploys, status, redeploys, and creating new projects. Payment always bounces to your browser, because we never take card details through chat. Same outcome either way: your app on your domain, your code in your GitHub.

Free Sandbox: ~60–90 seconds from form submit to a working subdomain at yoursubdomain.hatchik.com, with the sign-in email landing right after. Launch tier (your own domain, mailboxes, server in your region) takes a bit longer because we register the domain and wire DNS — expect a follow-up email within the hour and your stack live within 24 hours. Same product either way; only the provisioning path differs.

The boundary is your free Sandbox: your AI builds and pushes freely there, breaks nothing real (test-mode payments, no live customers), and you only promote to a Launch tier with a real domain once you're happy. Inside the substrate we gate destructive actions — CLAUDE.md tells your AI never to drop tables or columns without your say-so, migrations land as files for you to apply, and your repo's commit history makes any change reversible. "Use the Sandbox first" is the rail.

Today every sandbox lives on our Germany host (Hetzner Cloud, Nuremberg — EU GDPR jurisdiction). When you upgrade to Launch, you can ask for Finland, US East, US West or Singapore and we'll provision a host there once we have demand — all Hetzner, same hardware family. Your server is provisioned in your name. If you have specific rules to meet (GDPR for EU customers, HIPAA for US healthcare), tell us at upgrade and we'll match the region; we'll also send you the relevant paperwork.

Many apps in 2026 use AI to generate text, summarise content, chat with users, or recommend things at runtime — that's different from the AI that helps you write the code (your Cursor or Claude subscription handles that). Hatchik pre-wires integrations with Claude, GPT, Gemini, Grok and open-source models, and gives you two ways to pay for the usage: bring your own provider key (you get billed by the provider directly, no Hatchik involvement), or route through us for one bill, an included token allowance, and built-in cost caps. Either way, switching between providers is a config change, not a rewrite. If your app doesn't use AI internally, ignore it — it's optional.

Yes to all. Hatchik gives you a normal GitHub repo and a file called AI_CONTEXT.md that explains your stack — any AI coding tool can read that file and start helping. Named and tested: Cursor, Windsurf, Claude Code, Cline, Codex (OpenAI's CLI), and Antigravity (Google's IDE) — these open the repo folder and edit files autonomously. Browser AIs work too: ChatGPT, Gemini, Grok, Claude.ai, Perplexity Comet — you copy-paste between the chat and your editor instead of letting it edit files for you. And the AI inside your app (for features like chatbots or summaries) can use any provider: Anthropic, OpenAI, Google, xAI (Grok), Mistral, OpenRouter — it's just an API key in your .env file. If your tool isn't on this list, ask it — most of them just work.

Yes. By default that's exactly how it works — you put your Anthropic, OpenAI, or OpenRouter key into your app's .env file and the provider bills you directly. No Hatchik involvement, no margin on top, no lock-in. Hatchik's optional passthrough (one bill, included token allowance, vendor switching without code changes, cost caps) is a convenience for customers who want unified billing — it's not a requirement. You can switch between BYO and passthrough at any time, and the substrate code reads from environment variables that work with either path.

When we provision your sandbox we drop a BACKLOG.md file at the root of your repo pre-populated with about twenty starter tasks based on what you described. As your AI assistant works on features, it ticks them off — it reads and writes that file like any other. You see progress at a glance and can re-order, add new ideas, or leave notes inline. BACKLOG.md works with any tool you point at the repo — and if you'd rather use a proper tracker, just wire your own in. We don't make that decision for you.

No — and that's deliberate. We give you the foundation: hosting, domain, payments, mail, mobile builds, security. The actual product (the features your customers pay for) you build with your AI helper, or by hand, or by hiring someone. We're the boring infrastructure underneath, not the architect. If you want an AI tool to build your whole app from a prompt, look at Lovable or Bolt — they're great for prototypes but tend to hit a wall when you need real business plumbing. Hatchik is what's underneath after that.

A single dedicated VPS will comfortably carry a Launch-tier app well into its first thousand paying users. When you need more, the underlying setup is plain Docker + Postgres + Caddy — moving to a bigger server (or splitting across several) is hours of work, not weeks. At that point you've probably hired your first developer; we'll help them with the handover.