Launch checklist for apps built with Lovable, Bolt, Replit or v0
An app builder gets you to a working demo quickly. Real users need a few more things in place, and most of them take minutes to check.
Updated
Short answer
Before sending real users to an app built with Lovable, Bolt, Replit or v0, check eight things: custom domain and SSL, Row Level Security on every Supabase table, no secrets in client code, auth email settings, backups, error tracking, uptime checks on the site and API, and a status page. The table below says why each one is needed and how to check it.
Add uptime monitoring freeThe checklist
The Supabase rows assume Supabase is your backend, which is the common setup. If you use another database, the same questions apply to it.
| Item | Why | How to check |
|---|---|---|
| Custom domain with HTTPS | The default URL is fine for testing but not for users or email links | Open the site on your domain over https:// and confirm the browser shows no warning |
| Row Level Security (RLS) on every table | A table in an exposed schema without RLS is readable and writable by any role with a grant on it | Run the SQL below in the Supabase SQL editor and fix every table that shows false |
| No secrets in client code | Anything in the browser bundle is public | Search the repo for secret keys. Use only the publishable key in the browser |
| Auth email and redirect settings | Sign-up and password-reset emails break on defaults | Sign up with an address outside your team and open the link |
| Backups | You need a copy before the first bad migration | Look at Database, then Backups in Supabase, and check your plan |
| Error tracking | Most users who hit an error never report it | Trigger a test error and confirm it reaches the tracker |
| Uptime checks on site and API | You hear about an outage from users otherwise | Create monitors for the public URL and one API endpoint |
| Status page | It gives users one place to look during an incident | Open the page URL in a private window |
Custom domain and SSL
Connect the domain in your builder, then add the DNS records it asks for. In Lovable this is under Project → Settings → Domains, and custom domains need a paid plan. Lovable says it installs the SSL certificate for you, so you do not buy or upload one. If your domain has CAA records, they have to allow Lovable to issue it.
Check the other builders' own docs for their steps. Whichever you use, monitor the domain afterwards, because a certificate that fails to renew is easy to miss.
Supabase Row Level Security
Supabase documents RLS as the control that limits what the public key can reach. Without it, a table in an exposed schema can be read and written by any role that has a grant on it. With RLS enabled and no policies, the publishable key sees no data until you add policies.
select schemaname, tablename, rowsecurity
from pg_tables
where schemaname = 'public'
order by rowsecurity, tablename;
alter table public.reports enable row level security;Enabling RLS is not enough on its own. Write a policy for each table, then test as a signed-out visitor and as two different users. Supabase also recommends reviewing the policies for the anon and authenticated roles regularly.
Secrets and keys
| Key | Where it can live |
|---|---|
Publishable key (or legacy anon) | Browser code. Supabase calls it safe to expose, with RLS doing the protecting |
Secret key (or legacy service_role) | Backend only. It bypasses RLS, so never put it in the browser or in source control |
Variables prefixed VITE_ | Public. Vite embeds them in the client bundle, so they should not hold API keys |
If a secret key was ever pasted into the client code or committed, rotate it. For third-party API keys, call the API from an Edge Function and keep the key in function secrets.
Auth email, backups and errors
- Email limits: unless you set custom SMTP, Supabase Auth only delivers to addresses on the project team and limits the built-in service to 2 messages per hour. Set up SMTP before launch.
- Site URL: it starts as
http://localhost:3000. Change it under Authentication, then URL Configuration, and add your production redirect URLs. - Backups: Supabase backs up Pro, Team and Enterprise projects daily (7 days on Pro). On Free, export your data regularly with the CLI and keep a copy elsewhere.
- Error tracking: add a tracker such as Sentry to the frontend and any server code. Ask your builder to add it, then confirm a test error appears.
Set it up in UptimeIO
Do this last, once the domain works. You want one monitor for the page users load and one for the backend, because the page can load while the API behind it is failing.
- Create an HTTP monitor for your public URL. Only a
200passes by default. - Create a second monitor for an API endpoint or a small health function. If it needs a key, add it under HTTP Configuration as a request header. A Keyword monitor can also confirm the response contains the text you expect.
- Choose where alerts go: email, Slack, Telegram, Pushover or a webhook.
- Create a status page and add both monitors to it.
- Interval: the shortest is 5 minutes on Free, 1 minute on Pro and 30 seconds on Scale.
- Status page URL: it lives at
your-subdomain.status.uptimeio.com. The subdomain cannot be changed after creation. Custom domains are on Pro and Scale, and the Free plan includes one status page.
Questions
- What should I check before launching an app built with Lovable?
- Your custom domain and SSL, Row Level Security on every Supabase table, that no secret keys are in client code, auth email and redirect settings, backups, error tracking, uptime monitors for the site and API, and a status page.
- Is it safe to expose the Supabase publishable key?
- Yes, Supabase calls it safe to expose online. What protects your data is Row Level Security, so enable it on every table and write policies. The secret key must stay on the backend.
- Why are my Supabase sign-up emails not arriving?
- Without custom SMTP, Supabase Auth only delivers to addresses that are part of the project team and allows 2 messages per hour. Configure SMTP in the Authentication settings.
- Does the Supabase Free plan have automatic backups?
- Supabase documents automatic daily backups for Pro, Team and Enterprise projects. For Free projects it recommends regularly exporting your data with the CLI.
- Do I need a status page for a small app?
- It is optional, but it gives users somewhere to check during an outage instead of emailing you. The Free plan includes one status page.
Related
- Website monitoring - HTTP and keyword checks for your public site.
- Status pages - Publish your uptime and incidents on a page you control.
- Monitor Supabase Edge Functions - Health endpoint, keyword check and heartbeat for scheduled functions.
- HTTP monitoring docs - Status codes, response time alerts, SSL and domain expiry checks.