Free production check

Built with Lovable, Bolt or Cursor and stuck before launch? Bring it to Nexugen.

  1. Step 1

    Check

    Connect the GitHub repo or upload a ZIP. You get a plain report of what will break with real users. Free.

  2. Step 2

    Move

    The app runs on Nexugen with your Supabase project. Pilot fixes the findings and shows you each change first.

  3. Step 3

    Launch in the stores

    Website to App puts it in the App Store and Google Play. Pilot keeps it running after launch.

What the check looks at

  • Database rules
  • File storage
  • Keys in the code
  • Server functions
  • Payments
  • Admin access
  • Package holes
  • Crashes and failed requests

An example report

From a sample shop app made the way AI builders make them.

Sample app · Built with Lovable · 11 files read

Not safe to launch yet

Critical
2
High
8
Medium
0
Low
2

What will break with real users

CriticalAnyone can read and change every row in "orders"

Row Level Security is not turned on for orders. Your public key ships inside the app, so anyone who opens it can read, edit or delete every row in this table without signing in.

  • supabase/migrations/20250101000000_init.sql:10

What Nexugen does: Pilot writes a migration that turns on Row Level Security with rules scoped to each signed-in user, and shows it to you before anything runs.

Critical.env with secret keys is committed to the repository

VITE_STRIPE_SECRET_KEY are in the repository, so anyone with access to it, now or later, has them. VITE_STRIPE_SECRET_KEY also goes to the browser because of the prefix.

  • .env

What Nexugen does: Nexugen moves these into encrypted settings on import (never as a file), and Pilot removes the file from the repository. Rotate the keys that were exposed.

HighAdmin pages are only hidden in the browser

The app hides admin screens when the user is not an admin, but no database rule checks the role. Anyone can call the same data directly with the public key and do what an admin does.

  • src/pages/Admin.tsx:6

What Nexugen does: Pilot adds a role check to the database rules (a has_role() function over a roles table), so hiding a button is no longer the only lock.

HighAdmin rights come from a value users can set themselves

The app reads the role from user_metadata. Any signed-in user can change their own user_metadata from the browser console and make themselves an admin.

  • src/pages/Admin.tsx:8

What Nexugen does: Pilot keeps roles in a table only the database can write and checks them in the database rules.

9 more in the full report.

What is already good

  • Your database rules are kept in code, so they can be reviewed and rebuilt
  • Row Level Security is on for 1 of 2 tables
  • The app uses only the public Supabase key in the browser
  • Sign-in runs on Supabase Auth, not a home-made password store

Common questions

Do I keep my Supabase?

Yes. Your app keeps the same Supabase project, tables, files and user accounts. Nothing is copied out of it.

Do you need my secret keys?

No, never. The check reads your code only. If it finds a secret key in the code, the report says where so you can change it.

Does it run my code?

No. The check reads the files as text. Nothing is installed, built or run, and the code is not kept after the report is made.

What does it cost?

The check is free. Moving the app and the fixes after it are on your Nexugen plan.

Find out what will break before your users do.

Run the free check