A practical guide to current capabilities, including where provider setup or human review is still required.Open the builder →
1. Getting started
Create an account, describe the business outcome and users, then answer the builder interview. Save the first version before large refinements.
Use one project per product
Review the application plan
Never paste credentials into a prompt
2. Business Brain
Store reusable audience, offer, tone and operating context. Review shared memory before reusing it across projects.
3. AI Builder
Generate websites, web apps, dashboards, CRM-style tools and supported native contracts. The blueprint connects pages, data, actions and visual structure; generated output still requires review.
4. Websites and web apps
Edit responsive pages in Studio, preview interactions, inspect readiness deductions and export source. Preview does not prove that provider-backed actions are live.
5. Mobile and native
Mobile-responsive web output is available. Native iOS or Android targets require a complete native contract plus platform building and signing outside the browser preview.
6. Backend and database
Backend-enabled blueprints define entities, APIs, persistence and access rules. Validate schema, authentication and least-privilege permissions before handling customer data.
7. Authentication and teams
BuildGPT account access protects private workspaces. Generated-product authentication is separate. Assign viewer, operator, editor, or admin access deliberately; the workspace owner retains destructive ownership controls.
8. Domains
Search through a configured registrar or connect an external domain. New purchases also require secure payment activation. Registration, ownership verification, DNS, SSL and publication are separate states.
9. Deployment
Save an immutable project version, run readiness checks and deploy through a configured hosting provider. Verify health before directing production traffic.
10. AI agents
Create project-scoped agents with bounded tools, budgets and approval rules. Test first; risky actions stay approval-gated and credentials remain server-side.
11. Automations and chatbot
Draft workflows or a custom chatbot, connect triggers and actions, simulate, then activate explicitly. Monitor timelines, retries, approvals and dead-letter failures.
12. Integrations and CRM
Connection status reflects encrypted project credentials and provider validation. CRM records, lead activity and outbound actions remain owner-scoped and auditable.
13. Payments and AI credits
A production payment is successful only after signed provider reconciliation. Usage and AI-credit displays are operational records, not a bank statement.
14. Security
Use least privilege, rotate compromised credentials, verify signed webhooks and review approvals. Keep secrets out of prompts and support messages.
15. Troubleshooting
Start with the visible error, request ID, run timeline, deployment status or domain diagnostics. Retry only idempotent operations and test repairs before publishing.