Lovable Cloud to Supabase Launch Preflight

Turn a Lovable Cloud migration or generated Supabase app into a redacted launch packet before auth transfer, RLS, Storage upserts, explicit grants, backend ownership, or smoke tests become production debugging.

Build preflight packet Run full generated-app checker

Check before launch

Backend ownership is clear. Auth transfer has launch evidence. Generated public tables have explicit grants. RLS has negative-test evidence. Storage migration and upserts are tested. RPC/function/view reachability is reviewed. Frontend target switch is verified. Local replay does not depend on dashboard defaults.

Redacted launch notes

Use only redacted notes. Do not paste service-role keys, anon keys, connection strings, customer rows, private screenshots, payment data, full names, private handles, tokens, cookies, or account records.

Ready.

Migration plan packet

What to do with the packet

Paste the generated packet into the full generated-app checker, the grants checker, or the fixed-scope report only after the packet is redacted. The paid report is for one migration or generated-app packet and returns a concise 24-hour Markdown second pass.

Open generated-app checker Open grants checker See migration report scope

Source-backed problem set

Lovable MCP serverLovable documents MCP access patterns for project and database workflows; launch evidence still needs a separate redacted packet. Supabase grants rolloutExplicit grants become the default path for new public-schema tables and Data API reachability. Database API 42501 docsMissing table privileges can return permission errors separately from RLS behavior. Storage access controlObject policies control upload, overwrite, list, download, and delete behavior. Backend ownershipSupabase documents how to distinguish Lovable Cloud from a directly managed Supabase project.