LaunchCheck

This is a sample report for a test app we deliberately broke. Your report will look like this.

Check my app

my-saas.lovable.app/

Not ready to launch yet

Checked Nov 15, 2026, 2:58 PM · Built with Lovable · Backend: Supabase

Critical

10 fixes to make. Paste them into Lovable, Bolt, Cursor or Claude Code as one prompt.

Exposed secrets

3 critical issues to fix before launch.

Critical
  • Stripe live secret key exposed in your frontend code

    A Stripe live secret key lets anyone issue refunds, read customer data and create charges on your account.

    sk_live_TE…0000 in https://my-saas.lovable.app/assets/index-abc123.js
    How to fix: Roll this key in the Stripe dashboard now. Move all Stripe secret-key calls to a server function / API route and only expose the publishable key (pk_live_…) to the browser.
  • Supabase service_role key exposed in your frontend code

    The service_role key bypasses Row Level Security. Anyone visiting your site can read, edit or delete all data in your database and all users' accounts.

    eyJhbGciOi…bmx5 (role: service_role, project: abcdefghijklmnopqrst) in https://my-saas.lovable.app/assets/index-abc123.js
    How to fix: Remove the Supabase service_role key from the frontend and replace it with the anon/publishable key. Then rotate the service_role key / JWT secret in Supabase → Project Settings → API, because the old one is already public.
  • Your .env file is publicly downloadable

    Anyone can download this file, and it usually contains database passwords and API keys.

    https://my-saas.lovable.app/.env
    How to fix: Stop serving /.env (remove it from your public/static folder or block it in your hosting config) and rotate every secret it contained.

Data access & permissions

1 critical issue to fix before launch.

Critical
  • Anyone can read your "profiles" table — including personal data

    Using only the public key in your website, we could read rows from "profiles". It contains columns like email. Anyone can download this data.

    GET /rest/v1/profiles → 1+ rows, columns: id, full_name, email, created_at
    How to fix: Enable Row Level Security on the "profiles" table in Supabase and add policies so users can only read their own rows (e.g. `using (auth.uid() = user_id)`). Only allow public read if this data is meant to be public.
  • What we didn't test

    We only test what an anonymous visitor can read. We never write data, so we can't verify insert/update/delete policies, or whether one logged-in user can read another user's data.

Login & redirects

3 critical issues to fix before launch.

Critical
  • Links or forms on your site point to localhost

    Some links, form targets or login redirects use a localhost address. They work on your computer but are broken for every real visitor.

    http://localhost:3000/dashboard
    How to fix: Replace hard-coded http://localhost URLs with your production domain, or better, build them from `window.location.origin` / an environment variable.
  • Your app tries to call a server on localhost

    While loading, your app sent requests to localhost. In production these always fail, so whatever depends on them (data, login, payments) won't work for visitors.

    http://localhost:5173/api/health
    How to fix: Set your API base URL from an environment variable and configure the production value in your hosting provider (e.g. VITE_API_URL / NEXT_PUBLIC_API_URL).
  • After "Sign in with Google", users are sent to localhost

    Supabase will redirect users to http://localhost:3000 after they log in. Real users will see a "site can't be reached" error and won't be logged in.

    site_url = http://localhost:3000
    redirect after login = http://localhost:3000
    How to fix: In Supabase → Authentication → URL Configuration: set Site URL to https://my-saas.lovable.app and add https://my-saas.lovable.app/** to Redirect URLs.
  • Login page loads correctly

    Found an email field, a password field.

    https://my-saas.lovable.app/login

Errors & blank screens

2 things worth fixing.

Warning
  • Broken links show a blank page

    When someone opens a URL that doesn't exist (an old link, a typo), they get an empty screen instead of a helpful "Page not found" message.

    https://my-saas.lovable.app/launchcheck-404-test-mwhyluna
    How to fix: Add a catch-all 404 route that shows a friendly message and a link back to the homepage.
  • A failed login gives no feedback

    We tried logging in with a wrong password and nothing visible happened. Real users with a typo will think your app is broken.

    https://my-saas.lovable.app/login
    How to fix: After a failed sign-in, show the error from your auth provider next to the form (or as a toast), and re-enable the submit button.

Mobile layout

1 critical issue to fix before launch.

Critical
  • Homepage: page is wider than the phone screen

    The page is 908px wide on a 390px screen, so it scrolls sideways and content gets cut off.

    Elements sticking out: <div> "Wide pricing table"
    How to fix: Make the elements listed above responsive: use `max-width: 100%` on images/tables/code blocks, avoid fixed pixel widths, and let long words wrap (`overflow-wrap: anywhere`). Tables can be wrapped in a container with `overflow-x: auto`.