Prepare your AI-built app for its first users
Tell the assistant whether you have a public site, private accounts or an API. It can use the project’s known targets and ask for missing access. Approve the proposed scope and use the results to decide whether to open registration.
Prepare my launch check →Launch readiness checklist
Prepare the check with your AI assistant
Sample conversation
I’m inviting paying users on Friday. Help me choose what to test before opening registration.
Assistant · Are you opening just the website, customer accounts or an API? I’ll start with the routes your first customers will use. Which private action must a stranger never complete?
On first setup, verify the target and grant the assistant access to the intended project. Review the draft and confirm the run in your workspace.
Illustrative result and next action
A private export opened for the wrong account. Keep registration closed until the export is fixed and both owner and stranger controls have been rerun.
Questions before you start
Does completing the checklist clear my release?
It means the inputs are ready. Check the scan report and unresolved findings before inviting customers.
Which check comes first for a public site?
Verify your domain and run an external check before enabling registration. Add account-based checks once staging has private routes.
How do I prepare test customers?
For supported Express or FastAPI projects with SQLite, review the assistant’s fixture plan in the workspace before it prepares synthetic users. Otherwise provide suitable staging accounts yourself.
What should delay launch?
Reproduced access to somebody else’s private file needs an owner and a retest. An unavailable account leaves a gap to resolve or explicitly accept.
What can a public URL show?
An external check examines the reachable surface. Private workflows require authorized access and suitable test accounts. A source-code review or expert investigation has a different scope.
Can I reuse a prepared project?
Select the verified project, review the environment and permissions, then confirm the run. Recheck fixtures if the release changed the access model.