One flat price. AI credits included.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.