FixRLS

FixRLS is the tool Supabase developers didn't know they needed until their production database goes wide open. Row Level Security—RLS—is Supabase's whole thing. It's supposed to be your firewall. But here's the thing: most Supabase projects ship with RLS policies that are either missing, broken, or just straight up wrong. One misplaced service_role key and your entire database is public. FixRLS generates copy-paste RLS SQL, AI repair prompts for Cursor, Claude Code, Lovable, or Bolt, key placement guidance, MCP guardrails, and proof-of-fix tests—all without asking for your secrets. It stays offline and template-driven. You plug in your schema placeholders, it spits out the fix, you validate it yourself. No connection to your Supabase project. No scanning. No secrets needed. That's the point.

The free Fix Kit handles one immediate repair. The planned $19 Launch Pack is for teams shipping to production who want the full guardrail suite. Service_role key exposure is treated as critical. Anon key tables get checked for real ownership rules. MCP setup stays scoped and read-only where possible. This is pre-launch repair, not live scanning—because the best security fix happens before you have a breach. Supabase powers half the indie hacker scene right now, and most of those projects have RLS policies held together by hope and Stack Overflow answers. FixRLS just made it impossible to ship with those holes.