Get the weekly radar
One short email with the freshest products, every week.
Grounded in available product and source data
FixRLS helps developers fix common Supabase Row Level Security and key mistakes before launching an app. It's aimed at the pattern that shows up in AI-generated projects built with tools like Cursor, Lovable, Bolt, Claude Code, or ChatGPT: RLS errors, confusing auth policies, exposed keys, and unsafe MCP setups.
Instead of reading documentation or asking an AI for another guess, FixRLS generates copy-paste SQL policies, repair prompts, key placement guidance, and proof-of-fix tests you can review before shipping.
It never connects to your Supabase project and never asks for secrets, focusing instead on practical fixes you apply yourself.
The site doesn't specify which Supabase versions or project sizes it's built to handle, so that's worth checking directly for larger or more complex setups.
FixRLS targets four things that repeatedly show up in AI-generated Supabase apps: Row Level Security errors, auth policies that are hard to reason about, API keys exposed in client code, and MCP setups that aren't locked down.
It's for anyone shipping a Supabase-backed app who wants a pre-launch check on the security basics, rather than discovering a gap in RLS, auth, or key handling after users are already on the app.
No, it never connects to your Supabase project and never asks for secrets.
You point to the problem you're hitting — an RLS error, a confusing auth policy, whatever it is — and FixRLS returns SQL you can paste straight into Supabase, plus a proof-of-fix test so you can confirm the change actually worked before shipping.
