Launched this week
FixRLS
A repair tool for fixing Supabase RLS errors
5 followers
A repair tool for fixing Supabase RLS errors
5 followers
Generate copy-paste Supabase RLS SQL, AI repair prompts, key placement guidance, MCP guardrails, and proof-of-fix tests without connecting to your project.
Hi Product Hunt 👋
I built FixRLS because many AI-built Supabase apps get stuck right before launch on the same painful issues:
- “new row violates row-level security policy”
- “Is my anon / publishable key safe in the browser?”
- “What should I do if a service_role key was exposed?”
- “How do I connect Supabase MCP to Cursor or Claude Code without giving it too much access?”
Docs explain the concepts, but on launch day builders usually need something more concrete: copy-paste RLS SQL, an AI repair prompt, key placement guidance, MCP guardrails, and a proof-of-fix test they can run before shipping.
FixRLS is intentionally not a scanner and not a full security audit. It does not connect to your Supabase project, does not ask for secrets, and does not claim your app is “secure.” It gives you a focused repair starting point for common Supabase launch blockers.
I’d love feedback from Supabase builders, Cursor/Lovable/Bolt users, and anyone who has fought with RLS before launch.