Help centre

Help and support.

Short guides for each part of the product, plus the questions people ask most. For the full walkthrough, read the Docs. If none of this covers your problem, write to us.

Getting started

  1. After you sign in, the start page offers three ways in: describe your app, clone an existing app, or generate an idea from research.
  2. For an idea, pick a topic, target market and niche, then add one to five phrases a real customer would search. Leave Safe preview on for a no-cost run.
  3. Each way ends in a plan. Answer its open questions in one go, then continue to Name & domain, where you also say whether you need a marketing site.
  4. Scout agents (in the sidebar) save a market brief to run again later. Start from one of the six examples, then press Run now; weekly and monthly are reminders, not automatic runs.
  5. No logo yet, or bringing your own? In the builder, Recipes → Brand designs one or uses yours, and adds the favicon and the image shown when a link is shared.
  6. The Docs walk through every step in the order that works best.

Credits or your own AI key

  1. On Pro you need no key: the builder, research, names and idea chat run on your 300 monthly credits. Your balance is shown in the builder.
  2. To use your own account instead, choose Claude, Gemini or GPT and use the 'Get API key here' link to create a key in that provider's console.
  3. Paste it in. Nothing is stored on our servers; the key is used for the request and discarded. With your own key there is no limit from us.
  4. Tick 'Remember my keys in this browser' only on a machine you trust — that stores it unencrypted in local storage.

Building your app

  1. Open a project and choose Build. Pick a web app or a mobile app, then 'Build the first version' to start from your research.
  2. Describe changes in the chat in plain English. The preview updates as soon as each change is ready, and every version is kept in History.
  3. Attach files with + or by dropping them on the message box: screenshots and images, a PDF (one per message, up to 10 MB), Word documents (.docx, .odt), and text or Markdown files. Save .doc or .pages files as .docx or PDF first.
  4. Click Select on the preview, then click any element to change its text directly or describe a change to just that element.
  5. Files appear in the Code tab as they are written. You can also edit the code by hand there.
  6. For a mobile app, scan the QR code with the free Expo Go app to open it on your phone.

Recipes

  1. Recipes, under the chat, are ready-made requests for big jobs: payments, an admin panel, marketing pages, email, a theme, languages, SEO and an audit.
  2. They are numbered in the order that works best. Connect the database first: payments and the admin panel need it.
  3. An amber note means something it depends on is missing, with a button to fix it. It still runs if you go ahead.
  4. The audit writes a plan shown above the chat. Implement it one step at a time.

Publishing, domains and data

  1. Publish puts a web app on a name.blissfulplan.store address. Republish whenever you want the live version updated.
  2. On Pro, connect your own domains from the Publish dialog by adding the DNS record each one shows: the marketing site on www.yourname.com, the app on app.yourname.com, or just one of them.
  3. With a database, update the Sign-in addresses (in Publish or Database) after each new address, or signing in there fails.
  4. Database connects or creates a Supabase project. Tables arrive as migrations you review and apply; the Data tab shows your tables and anything exposed.
  5. GitHub creates a private repository, or links one you already have, then pushes new versions and pulls back edits made there.

Hosting elsewhere

  1. Publish → Host it elsewhere has the steps for Vercel, Netlify, Cloudflare Pages and GitHub Pages. Connect GitHub first: every host builds from it, and updates when the builder sends a change.
  2. If a host asks for settings: build command npm run build, output folder dist.
  3. Add the host's address (for example myapp.vercel.app) under Sign-in addresses, then connect your domain in that host's own settings.
  4. WordPress cannot run the app, but it can be the marketing site: keep it on www, connect only the App address here.

Reading domain results

  1. "Available" means the ending's own registry has no record of the domain.
  2. "Likely available" is for endings with no public registry lookup, such as .io and .co: DNS has never heard of the name. Confirm it at a registrar.
  3. Names with no domain that looks free are removed before you see them.
  4. If a run returns nothing, check the message: 'the registry did not answer' is temporary, and different from everything being taken.
  5. Availability is a snapshot. A domain is only yours once a registrar confirms the purchase.

A branded starter repository

  1. Separately from the app builder, Pro can create a Next.js starter with your brand applied. Finish the venture studio through the Brand step, then choose Build repository on the project.
  2. Enter a GitHub token with repo scope. AppCrafter checks the scope before creating anything.
  3. Choose a custom domain or local development — local skips domains entirely and tells you the ports to use.
  4. The result is a real repository with a runnable Next.js project and your brand already applied.

Plans and billing

  1. Free covers one app and three research runs a month, with 50 starter credits, then your own AI key.
  2. Pro ($15 a month) removes both limits, includes 300 AI credits a month, and adds your own domain, AI logos and starter repositories. Studio ($39) adds 1,000 credits, workspaces and client preview links.
  3. Upgrade from Account → Plan Details, choosing monthly or annual.
  4. Cancel any time in the billing portal. You keep Pro until the period you paid for ends.

When something goes wrong

  1. A 502 from a research run usually means the model cannot use the web search tool. Try the recommended model for that provider.
  2. 'Rate limited' means too many requests in a short window; the message says when to retry.
  3. A failed build records which stage failed and why — open the project to see it. A failed recipe can simply be run again.
  4. Still stuck? Write to us with the project name and roughly when it happened.

Frequently asked

Common questions.

Do I need my own AI API key?

No. Every account gets 50 starter credits to try the builder without a key, Pro includes 300 AI credits a month and Studio 1,000, and on Pro or Studio you can top up 500 credits for $10 whenever you need more (top-ups never expire). Credits pay for the app builder, market research, names and idea chat. A credit is one US cent of what the AI provider charges, plus 25% for retries and price changes. One message to the builder (the first version, or one change) on a mid-range model such as Claude Sonnet 5.5 uses about 9 to 17 credits, so 300 credits are roughly 17 to 33 messages; an economy model goes several times further, and the most capable models use about 17 to 66 a message. The pricing page lists each model. Monthly credits are used first, renew each month and do not roll over. On any plan you can connect your own Anthropic, OpenAI or Google key instead; your provider bills you directly, with no markup and no limit from us. Once its starter credits are used, the Free plan needs your own key, and AI logo generation always uses one. Safe preview runs the research flow without calling a provider at all.

What do I actually end up with?

A working app: React and TypeScript for the web, or React Native for phones. You can publish a web app to its own address in one click, connect a database in your own Supabase account, and push the code to your own GitHub repository at any time. Nothing about it depends on AppCrafter to keep running except the free blissfulplan.store hosting, and you can move off that whenever you like.

What if I want to stop using AppCrafter?

Take everything with you, free, on any plan. Download the project as a zip (the code, plus your research, concept and brand as Markdown with your logo) or push it to your own GitHub, and host it anywhere that serves a Vite app. Your Supabase database and Stripe checkout are already in your own accounts, so they keep working without us. We check on every release that a downloaded project installs and builds with nothing from AppCrafter. The step-by-step guide is at appcrafter.app/leave.

Can I build mobile apps?

Yes: pick a mobile app before the first build and it is built with React Native and Expo, for iPhone and Android. It previews in the page, and opens on your own phone through the free Expo Go app by scanning a QR code, updating as you build. Publishing to the App Store and Google Play is not available yet; the code is a standard Expo project, so you can publish it yourself with Expo's tools.

What are recipes, and in what order should I run them?

Recipes are detailed, ready-made requests for the big jobs: payments, an admin panel, the marketing site's pages, email, a light and dark theme, languages, SEO and GEO, and a full audit with a step-by-step plan. They are in the Recipes button under the chat, numbered in the order that works best. Connect the database before payments and the admin panel, because both need to store who paid and who is an admin. Add the marketing pages after payments and the admin panel, run the theme and languages once your pages are settled, SEO after languages and after publishing, and the audit last. Any order still works; the menu warns you, without blocking, when a step runs before what it depends on. The full sequence is in the Docs.

Can my app have a marketing site as well?

Yes. When you choose the domain, AppCrafter asks whether you need a public marketing site next to the app, and where each goes: by default the site on www.yourname.com (with yourname.com forwarded to it) and the app on app.yourname.com. Connect both from Publish and each goes to the right place. With a marketing site, the first build makes the landing page and the app together; without one, it opens straight on the app. The theme and languages recipes then ask whether to change the app, the site or both.

Can I host my app on Vercel, Netlify, Cloudflare or GitHub Pages?

Yes. Connect GitHub, then open Publish → Host it elsewhere for the steps for each one. The host builds the app from its GitHub copy (build command npm run build, output folder dist) and updates by itself whenever the builder sends a change. If your app has a database, add the new address under Sign-in addresses so signing in works there. WordPress cannot run the app itself, but it can be your marketing site, with the app on app.yourname.com.

What does a research run actually do?

It searches the live web for evidence of demand in the market you defined, then generates five distinct concepts grounded in what it found, each scored on revenue potential, starting cost and build difficulty. You see the sources behind the analysis, and all five concepts are saved, not just the one you pick. The concept you choose is what the first version of your app is built from.

Are the revenue estimates reliable?

No, and we will not pretend otherwise. They are hypotheses generated by a language model from the research available at that moment. Treat them as a starting point for your own diligence, not a forecast. Do not make an irreversible financial decision on the strength of a number this product produced.

Is my app's data safe?

The data lives in your own Supabase project, not ours. The builder writes your tables as migrations you review before anything runs, and refuses a table that anyone on the internet could read or change: every table must have row-level security. The Data tab checks the live database and flags anything exposed, with a one-click request to fix it. It is a strong safeguard, not a guarantee, so review what you publish.

Where do my API keys go?

Your key is sent to our server, used to call the provider on your behalf, and discarded when the request ends. It is never written to our database. If you tick remember, it is stored in your own browser's local storage, which is unencrypted — that box is off by default and we say so in the interface. GitHub and Supabase access tokens are handled the same way.

Can I cancel?

Any time, from the billing portal in your account. You keep Pro access until the end of the period you have already paid for, then drop back to Free. Your projects and research are not deleted when you downgrade.

What happens to my data if I delete my account?

It is removed. Deleting your account takes down any published apps and custom domains, then removes every project, research run, saved concept, brand asset and stored credential, and clears your generated files from storage. Your own GitHub repositories and Supabase projects are yours and are left untouched. It is immediate and cannot be undone, which is why it asks you to type your email address to confirm.

Need a person? Contact us — we reply within two working days, and within one on Studio.