01 · Checklist
What should you check before launching an AI-built app?
Check the seven items in the table before real users arrive. The vendor column holds only what each tool's own documentation states, with links in the next section. Where the docs are silent, the cell says so, because silence is a question for you to answer, not a pass.
| Check | Lovable | Bolt | Replit |
|---|---|---|---|
| Code you own and can move | GitHub sync to one repository, one branch at a time | GitHub connection available; built-in version history | Not covered on the pages we read |
| Data access rules | Docs say every table needs RLS policies before going live | Security Audit checks the database for missing RLS, and only the database | Not covered on the pages we read |
| Secrets | Entered through a secure input, stored in your Supabase project | Secrets feature for outside service keys | Secrets stored encrypted; Static deployments do not support them |
| Release and rollback | Not covered on the pages we read | Publish or Update by button; edits do not go live on their own | Published apps run as snapshots; publish again to update |
| Where data lives | Supabase project you own, or the built-in backend | Bolt Database, or your own Supabase | Do not rely on filesystem data; use Replit storage or a database |
| Tests | Not a tool feature: you add them | Not a tool feature: you add them | Not a tool feature: you add them |
| Monitoring after launch | Not covered on the pages we read | Logs for functions, auth, PostgreSQL and storage | Monitoring shows published app status and configuration |
02 · Lovable
What does Lovable's own documentation say about going live?
Lovable's Supabase integration docs say every table should have row-level security policies before going live, and call missing policies the most common way app data gets exposed.
- 01
Lovable runs automated checks, including RLS coverage, but a check is not a review: someone should confirm who can read each table.
- 02
The same page says secrets such as a Stripe or Resend key are entered through a secure input and stored in your Supabase project, not in app code or the repository. Projects that share one Supabase project overwrite each other's secrets, so give each app its own. Per the GitHub docs, sync is two-way for one branch at a time, and if you disconnect, the repository stays on GitHub while later changes live only in Lovable.
03 · Bolt
What does Bolt's documentation say about publishing?
Bolt's Publish page says edits do not go live automatically: you click Update.
- 01
Free plan sites are always public, and sites with a custom domain can only be public. Paid plans can run a security audit before publishing.
- 02
The Database page says the Security Audit checks the database for open permissions or missing row-level security policies, and checks only the database, not the rest of your project. The page also notes that databases in unpublished projects, and projects on Netlify, can pause after six or more days of low usage. The version history and GitHub page describes connecting a project to GitHub for branches and pull request reviews.
04 · Replit
What does Replit's documentation say about deployments?
Replit's Deployments docs list four types: Autoscale, Static, Reserved VM and Scheduled.
- 01
They state that published apps run as snapshots, so you publish again to update, and that you should not rely on data written to the app's filesystem. Access controls that limit who can see an app are on Pro and Enterprise plans.
- 02
The Secrets docs say secrets are encrypted at rest and exposed to code as environment variables, and warn against hard-coding them or storing them as plain configurations. They also note that Static deployments do not support secrets.
05 · Gaps
What does no builder tool decide for you?
No builder decides your tests, your review of access rules, or your plan for incidents. These are the gaps that turn a good demo into a risky launch.
Tests
Write checks for sign-up, login, payment and any path that changes data. See prototype to production.
Independent review
A person who did not build the app reads the access rules and the secrets handling. A code audit does this.
Backups and recovery
Confirm what is backed up and try a restore before you need one.
Ownership
Put the repository, domain and cloud accounts under your organization, not one person's login.
06 · Next step
How does Ace8 help move an AI-built app to production?
Ace8 is the modernization practice of AceMQ.
- 01
AceMQ engineers audit the app first, fix what blocks launch, add tests and a deploy pipeline, and ship it. See software project rescue for the method. The price is a quote on request, with a fixed price for the first audit.
- 02
Request a rescue audit and we will tell you what stands between your app and real users.