From vibe-coded prototype to production: the 25-point checklist
6 min read
On this page
Tools like Lovable, Bolt, v0, Replit and Cursor can take an idea to a working demo very quickly. The demo, though, is built to look right, and production has to behave right when strangers, bad actors and real payments arrive. The 25 points below are grouped into ten areas. Work through them in order, mark each one, and you will have a clear list of what is done and what a developer still needs to handle.
If you prefer an interactive version that saves your progress, the Production Readiness Checklist tool covers the same ground by stack.
How to use this checklist
You do not need to be a developer to work through most of these points. Many are questions you can answer by clicking around your dashboards or testing the app as a normal user. For each point, write one of three answers: done, not relevant, or needs work. "Not sure" counts as needs work.
Two habits make the results more reliable. First, test in the live app on your real domain, not in the builder's preview, because settings often differ between the two. Second, keep a short note of how you checked each point. When a developer joins later, that note tells them what has really been tested and what has only been assumed.
Authentication
- Every private page and API call checks the user on the server. Hiding a button in the interface is not security. If someone can call the API or query the database directly, they must still be refused. Ask your developer where each permission check happens.
- Sign-up, email confirmation and password reset work on the real domain. These flows often break at launch because redirect links still point at a preview URL. In Supabase, check the Site URL and the allowed redirect URLs in the authentication settings.
- Sign-in and sign-up are protected from abuse. Confirm there is rate limiting or bot protection, such as a CAPTCHA on sign-up, and that sessions expire and sign-out actually ends the session.
Data access and row level security
- Row level security is switched on for every table that holds user data. In Supabase, tables in the exposed schema can be read through the public API unless row level security is enabled. In Firebase, Security Rules must no longer be in test mode.
- Policies limit each user to their own rows. A policy of
using (true)lets anyone read everything. Inserts and updates need awith checkclause so users cannot write rows on behalf of someone else. A correct pair looks like this:
alter table public.notes enable row level security;
create policy "Users read own notes"
on public.notes for select
to authenticated
using ((select auth.uid()) = user_id);
create policy "Users add own notes"
on public.notes for insert
to authenticated
with check ((select auth.uid()) = user_id);
- You have tested with two accounts. Sign in as user A, then as user B, and try to see or change A's data by editing URLs or IDs. Storage buckets need the same test: private files should not be reachable by guessing a link. The Supabase RLS Checker flags common policy gaps from your SQL.
Secrets
- No secret keys are shipped to the browser. Any variable prefixed
VITE_orNEXT_PUBLIC_ends up in code that anyone can read. Payment secret keys, service role keys and AI provider keys belong only in server code or edge functions. - No secrets are committed to the repository. Check the current files and the history. A key removed in a later commit is still visible in earlier ones. Paste suspect files into the Secret Leak Scanner, which runs locally in your browser.
- Any key that was ever exposed has been replaced. Deleting the file does not make the key safe. Create a new key, deploy it, then revoke the old one.
Payments
- Webhooks are verified and drive fulfilment. Grant access to paid features when your server receives a signed webhook from the payment provider, not when the user lands on a "success" page, which anyone can visit. For Stripe, verify the signature using the endpoint's signing secret and the raw request body.
- Prices come from the server. If the browser sends the amount to charge, it can be changed. Use price IDs or server-side lookups.
- Live mode is set up properly. Live keys, a live webhook endpoint and live products are separate from test mode. Also check what happens on failed renewals, refunds and cancellations, not just the first payment.
Errors and monitoring
- Errors are recorded somewhere you will see them. Add an error tracking service to both the front end and the server so crashes reach you before users complain.
- You are alerted when the site goes down. A simple uptime monitor that emails or messages you is enough to start. Make sure users see a helpful error page rather than a blank screen.
Backups
- Automatic database backups are running. Check what your database plan includes and how far back you can restore. Uploaded files in storage may need their own backup.
- A restore has actually been tried. A backup you have never restored is a hope, not a plan. Restore into a separate project once and write down the steps.
Performance
- Lists are paginated and queries are indexed. Prototypes often load every row at once. That is fine with ten rows and painful with ten thousand. Add indexes for the columns you filter and sort by.
- The app is usable on a mid-range phone and a slow connection. Compress and resize images, remove unused libraries, and test on a real device. The Dependency Freshness Check also helps you spot outdated or deprecated packages.
SEO and sharing
- Public pages can be read without JavaScript, if search matters to you. Many AI builders produce single-page apps where the first HTML response is almost empty. Search engines may render JavaScript, but link previews in chat apps and social networks often do not. Server rendering or pre-rendering public pages solves this.
- Each public page has its own title, description and preview image, and the site has a
robots.txtand a sitemap. Keep private dashboards out of search withnoindex.
Legal pages
- A privacy policy and terms of use are published and linked. They should describe what you actually collect and which services process it. App stores require a privacy policy link, and many countries have privacy laws. Get local advice if you are unsure what applies.
- Cookie consent and data requests are handled. If you use non-essential cookies or tracking in places that require consent, such as the EU and UK, ask before setting them. Have a way for users to request a copy or deletion of their data.
Deployment
- Development and production are separate. Production should have its own database and keys, so testing never touches real customer data.
- The app builds and deploys from the repository. If it only runs inside the AI builder, you depend on that tool forever. Confirm a developer can clone the code, set environment variables and deploy it to your hosting.
- You can roll back. Know how to return to the previous working version in your hosting dashboard, and use your own domain with HTTPS.
Track your progress
Use this list to record where each area stands:
- Authentication (points 1 to 3)
- Data access and row level security (points 4 to 6)
- Secrets (points 7 to 9)
- Payments (points 10 to 12)
- Errors and monitoring (points 13 and 14)
- Backups (points 15 and 16)
- Performance (points 17 and 18)
- SEO and sharing (points 19 and 20)
- Legal pages (points 21 and 22)
- Deployment (points 23 to 25)
When the list is longer than you expected
It is normal for an AI-built prototype to have open items in several areas. The tools were designed to get you to a demo, and this list covers what comes after. The AI-generated app security issues page explains the most common gaps in more depth, and Supabase auth or RLS broken covers the database side.
If you would rather hand the remaining work to someone, copy your open points into a listing and post your takeover for free. Developers who take over AI-built apps can see exactly what is left and get in touch with you directly.
Frequently asked questions
Do I need to finish all 25 points before launching?
Not all of them carry the same weight. Points about access control, secrets and payments protect your users' data and money, so treat them as must-haves. Some performance and SEO points can follow soon after launch if you have a plan for them.
Can I ask the AI builder to fix these issues itself?
You can ask, and it may help with some items, but check the result rather than trusting the summary. AI tools sometimes report that a security rule is in place when it is not. Testing with a second user account is the reliable way to know.
My app uses Firebase, not Supabase. Does this checklist still apply?
Yes. The areas are the same. Instead of row level security policies, you check Firebase Security Rules for Firestore and Storage, making sure they no longer allow open reads and writes.
Is the Supabase anon key a secret?
No. The anon or publishable key is designed to be visible in the browser. Your data is protected by row level security policies, which is why those policies matter so much. The service role key is different: it bypasses those policies and must stay on the server.
How do I know which points apply to my app?
Work through each one and mark it done, not relevant, or needs work. If you are unsure about a point, write it down as a question. A developer reviewing your project can answer those questions quickly once they have access.
Who can do this work for me?
Many developers and agencies specialise in getting AI-built prototypes ready for real users. You can post your project on TakeoverWork with a note of which checklist points are open, and interested developers will get in touch. Agree scope and price directly with them.
Stuck with a half-built app?
Post your project free. Developers who finish and rescue projects can send you an interest note, and you decide who to talk to. You agree scope and payment directly with them.
Free tools that help
Related guides
How to hand over an unfinished software project (complete checklist)
Package your half-built project so a new developer can run, change and deploy it without guessing: accounts, code, setup, known issues and a clean access plan.
ReadHow to give a developer access without sharing passwords
Use team invites and limited roles instead of shared passwords, service by service, and know exactly how to remove access and rotate keys when the work ends.
ReadHow to write a takeover listing that gets good responses
Developers decide quickly whether a takeover is worth a reply. Clear facts about the stack, the state of the code and your budget bring better, more specific responses.
ReadRelated problems
Security issues in AI-generated apps: what to check and how to fix them
AI app builders ship working features fast, but often leave keys in the browser, tables open and API routes unprotected. Here is how to check yours.
ReadSupabase auth or RLS broken? How to find the cause
Supabase auth and RLS problems show up as login loops, missing emails, empty pages or data leaks. Most come from a handful of settings and policy patterns.
ReadLovable app not working? How to find what broke and get it fixed
Most Lovable apps that break do so for a short list of reasons: auth settings, database policies, keys, deploys, edge functions or payments. Here is how to narrow it down.
ReadBolt app stuck? How to get your project moving again
A stuck Bolt project usually means the AI has lost track of a large codebase, the build is broken, or the app only works inside the browser preview.
Read