A go-live review for an AI-built app answers one question before real customers arrive: what can a stranger read, and can you recover if something goes wrong? Run five checks: database access rules, what the public key can read, secrets in client code, sign-in on every read, and a restore test. Then two named owners decide go or hold.
An app built with an AI tool can work on the first try while nobody has reviewed its access rules, keys or backups.
Why this check belongs on your launch list
Researchers examined 159,041 projects built with one AI app-building tool. Of the 34,545 that used an online database service, 24,664 sent database records as soon as the site loaded, with no sign-in. The researchers retrieved only parts of the data. They also say the sample is not representative, that some of the data may be meant to be public, and that automated checks are no substitute for a professional security assessment (the researchers’ page). Treat the figures as a reason to look, not as a rate for your app.
Key takeaways
- The first test needs no code.
- The risk comes from settings nobody reviewed.
- Go-live is a decision with two named owners.
The five checks
1. Row-level access rules. The documentation of the database service in that research says to enable row-level security on every table in an exposed schema. Without it, a table is readable and writable by any role that has a grant on it (the service’s row-level security guide). Ask your builder to show, table by table, that the rule is on and what each policy allows.
2. What the public key can read. The key shipped with your app is visible to anyone who opens its code. Ask your builder to run a read request with only that key and show you the result. It should return nothing that a visitor should not see.
3. Secrets in client code. Service keys bypass the access rules and belong on the server only. Search the code that reaches the browser for any key marked as a service or secret key. One found there means the access rules do not protect you until the key is replaced.
4. Sign-in on every read. Check each page and each request that returns customer data, not only the login screen. List what is public on purpose and confirm the rest asks who you are.
5. A restore test. “We have backups” is a statement. A restore is evidence. Delete one record on purpose, restore it into a separate copy and time it. The timing from a test on one laptop is not a promise for a real system, but it shows whether the path exists.
Run the first test now
Open your app in a private browser window without signing in. Look at what loads. Then ask your builder what a request with no sign-in returns for each table. You do not need to read code to hear whether the answer is clear.
Decide go or hold
Write the result on one page. Name two owners: one accountable for the business risk, one for the technical checks. Each states in writing what they saw. A failed check does not mean the app is finished. It means the date moves, and you know why.
After launch
Keep the same page. When the app changes, rerun the checks that the change touches. When a new data source or a new user group arrives, add it to the page before it goes live.
Where OrNsoft fits
Bring us the problem. We move the system from concept or pilot to production. If your app is close to go-live, bring us the problem.
OrNsoft is an advanced AI engineering firm, founded in Florida in 2009, with applied AI in its software since 2015. One call is enough to know whether we can help.
Questions
- What is a go-live review?
- A short, structured check, done before real customers use an app, of what an unauthorized person can reach, what happens when something fails and who is accountable.
- Can I run the first test myself?
- Yes. Open your app in a private browser window without signing in and look at what loads. Ask your builder to show you what the same request returns with no sign-in.
- Is an AI-built app unsafe by default?
- No. The risk comes from settings that were never reviewed. The same checks apply to an app built by a freelancer or an in-house team.
- Who should sign off on go-live?
- Two named owners: one for the business risk and one for the technical checks.
Bring us the problem.
Book a call