Lite is free. Pro adds this and the rest of the quality layer.
Adams forSupabase projects.
The database is a short step from the browser. Adams keeps the powerful key private and helps review who can read what.
Lite and Pro
// the problem
What goes wrong
Two keys, very different powerA public key is meant for the browser and relies on access rules. The service key bypasses them. Mixing the two exposes every row.
Rules that are off or too openA table without access rules, or with one that allows everyone, works perfectly in testing and leaks in production.
// what adams does
What Adams does
Blocks the service keyLite: a powerful key written into code is caught at commit and moved to an ignored env file.
Scopes an access checkPro: pick access control and a separate agent reviews the rules and the queries that use them.
Asks about data firstPro: who owns a row and who may read it are settled before tables are built.
// worked example
An example
Checking who can read orders
Illustrative session.
~/project~/your-project · example
/adams:secure
Scope: access control
P0: the service key is used in browser code
P1: orders table has no owner rule
Replace the key first, then add the rule
// faq
Questions
Does Adams connect to my Supabase project?
No. It reads files in your repository. It does not log in to your project.
Can it write the access rules?
Your AI can. Adams asks the decisions first and has a separate agent review them.
What is free?
The secret guards. The secure check is Pro.
// related