AppBully.Database checks
Check the rules. Don’t assume they work.
Connect Supabase to review supported database and access settings. Understand what needs attention without having to become a database expert.
Get your Launch PassWorks with
Claude Code
CodexMCP 
What you get
Data access rules
Review supported row-level security settings that help control who can access your data.
Configuration concerns
Spot supported settings that deserve a closer look, with an explanation of why they matter.
Fix and check again
Take a fix prompt to your coding assistant, review the change and run another check.
See what your database allows.
Connect your Supabase project
Choose the project that belongs to your app. AppBully reads supported configuration so the review starts with your database settings.
Find the access concerns
Focused checks look at supported access and security settings, including row-level security. Findings explain what was observed and why you should review it.
Make a considered fix
Copy the guidance into your coding assistant. Review the proposed change against what your users should be allowed to do before applying it.
Recheck your database
Run another database check after updating Supabase. Use the new findings to see what still needs attention. A code push alone does not verify your live database settings.
Each completed database check uses one check from your pass.
Your coding assistant. Now with receipts.
AppBully spots the loose ends. Claude Code or Codex gets the evidence and fix prompts, right in your editor.
Claude CodeCodex
AppBullyFindings for your appWho can edit this record?
api/projects/[id]
Check that the person making changes owns the project.
AppBully · Finding + evidenceClaude CodeCodexFound the loose end.
Check ownership before saving a project. Keep other users from changing it.
Illustrative example. Review changes with your assistant, then recheck in AppBully.
Your code is only part of the picture.
An app can look right while its database permissions need work. AppBully’s dedicated Supabase checks inspect supported configuration separately from your GitHub code, then turn the results into understandable findings and practical next steps.
