Frequently asked questions
What you buy, what you own, and what Maker can do — answered plainly.
What I'm actually buying
What is a credit, and how many does a generation use?
A credit is the unit used to create an application. The cost is fixed and known in advance: a quick generation (sketch) costs 1 credit, a more thorough one (craft) 3 credits, the most complete one (masterpiece) 10 credits. The amount is shown before you launch. Your plan already includes credits: 5 on Discovery, 60 per month on Pro, 400 per month on Max.
Subscription, credits, hosting: which one is required?
Only one thing is required: your plan, including the free Discovery plan. Credits are included in it — not an added cost. Extended hosting, beyond the window already included in each plan, is the only truly separate option, and it is optional. At a minimum, you pay your plan's price, full stop.
What's the real difference between Discovery and Pro?
Both give access to the same levels (sketch and craft). Pro adds, concretely: twelve times more credits (60 per month versus 5), more applications kept online (up to 25 versus 3), a longer included hosting window (7 days versus 48 h), and the option to buy extra credits on demand. The masterpiece level stays reserved for Max.
Ownership and exit
Does the code really belong to me, and what can I do with it?
Yes. Each application is a self-contained Next.js + PostgreSQL project that you own. You export it as a ZIP archive, push it to your own GitHub repository, and extend it freely.
Can I host it elsewhere and leave with it?
Yes. The exported project can be hosted wherever you want, with your own means. You don't need anyone to run it.
If I cancel my subscription, what happens to my applications?
Your ownership outlives the subscription: the code stays exportable, you retrieve it and host it elsewhere. What stops is the managed hosting — the applications we keep online for you shut down. You don't lose your work.
What is the AppSpec, and why is it an asset I keep?
The AppSpec is the structured description of your application: what you described, cleaned up and reusable. You can re-read it, adjust it, and use it to regenerate the application. It's your business thinking turned into a durable document, not a conversation that fades.
Capabilities and limits
What types of applications can Maker generate — and which not?
Maker is built for management applications: anything organised around data to enter, list, relate, track over time and put on dashboards — entities, flows, statuses and indicators, for internal or team use. Not (yet) the right tool for: high-traffic consumer websites, complex real-time logic, very advanced third-party integrations, native mobile apps.
Is the application production-ready, or is it a prototype?
It's a real application, not a mockup. Each application is built then automatically tested — build, startup, navigation across screens — before delivery, and deployed to a dedicated URL. Within its scope, business management for internal or team use, it's usable as is. For critical use, take the time to check it against your own data.
Can I modify the application after generation?
Yes, at two levels. You can adjust the plan (the AppSpec) and regenerate; the visual identity is set via the design charters and designers. And since the code is yours (ZIP export, GitHub push), you can also edit the project directly, with no ceiling.
Trust and data
Are my data and my clients' data isolated?
Yes. Each deployed application has its own database and its own execution space, separate from those of other applications. Your data is not mixed with another client's.
On the free plan, are my applications used as examples, and can I opt out?
On the Discovery plan (free), your applications may be featured as examples (gallery, showcase) and used to improve the service: it's the accepted trade-off for it being free, and it can't be turned off on this plan. You keep full ownership and can export them at any time. Paid plans are not featured this way.