The build assistant does not generate an application behind your back. It runs a structured interview, produces a blueprint you can read and change, and only then materializes modules, pages, and permissions. You are approving a plan, not accepting a black box.
A conversation about what the application is for: what you track, who uses it, what has to happen when something changes, and which roles see what.
A structured plan describing the modules, fields, relationships, pages, user types, and workflows the interview implied. You read it, correct it, and approve it.
Approved blueprints are turned into a real application with real database objects, real pages, and real permissions — not a mockup you then have to rebuild.
Every AI builder can produce something quickly. The question is whether you can tell what it produced before it is running in front of your customers.
The blueprint is the artifact that makes this reviewable. It is structured rather than prose, so it can be checked field by field, and it is the same kind of object as a template blueprint — which means it can be versioned, diffed, and reused.
The planner is grammar-constrained, so it produces blueprints that are structurally valid by construction rather than JSON that happens to parse this time. A plan that cannot be materialized is caught at the planning stage, not halfway through creating tables.
An application built this way is not a lesser tier. It gets the same dedicated databases, the same permission model, the same audit logging, and the same ability to be extended by hand or by a developer afterwards.
Speed matters most when you can still tell what you got. The blueprint is there so the answer to 'what did it build' is a document rather than an archaeology project.
Completely. The output is an ordinary application: pages, modules, fields, and workflows are all editable in the visual builder afterwards.
It is strongest at establishing the structure quickly. Genuinely unusual logic is still better specified by you or written as an extension.
Yes. A blueprint you are happy with can become a template you install repeatedly or publish for sale.
Create an account, explore the full builder console, and launch your first application on a custom domain. Nothing is charged while your application is still in development.
No credit card required. The console preview, the documentation, and the architecture reference are all readable before you sign up.
Get started free Read the docsCompose React pages in the Puck page designer, configure themes, assets, menus and User Types, and publish a reviewed page version. User Types select the experience; DataRoles and Locations control access to business records. A saved draft is separate from the version customers see.
Read the guideAI search and Knowledge Core use the current user’s record, field, DataRole, location and AI-read permissions before assembling context. Multimodal retrieval can retain document text and visual evidence. Model serving, ingestion and execution workers must be configured and enabled; seeing an AI control does not establish that a provider or worker is running.
Read the guide