evidence-focused Supabase Postgres evidence collection
Supabase audit
Supabase Postgres audit
Use Database Optimization Tool to review Supabase query, index, and maintenance evidence without treating the project as a self-hosted server.
Local collector runs from your environment
Human review before production decisions
No database changes applied by Database Optimization Tool
How much audit signal survives on Supabase
A Supabase Postgres audit can still find slow query pressure, missing indexes, unused indexes, bloat, and vacuum risk from SQL-visible evidence, even when provider-managed internals stay hidden.
Environment limits
Supabase projects may restrict privileged roles, extension management, filesystem access, and server settings. The audit records those restrictions and avoids inventing host-level findings.
What to do when query stats are limited
The collector checks relation sizes, index scan patterns, table churn, autovacuum indicators, and pg_stat_statements when your Supabase role can read it.
What this page cannot promise
Database Optimization Tool cannot bypass Supabase permissions, change project settings, or promise results from views your database role cannot read.
FAQ
Frequently asked questions
These answers describe the product focus: careful database evidence, clear findings, and team-approved next steps.
Does a Supabase audit require superuser?
No. A evidence-focused Supabase role is preferred when it can connect and read the required catalog and statistics views. Missing permissions are reported as gaps, not guessed findings.
What if pg_stat_statements is unavailable on Supabase?
The report leans more on schema, index, table, and maintenance evidence. Query ranking is weaker without pg_stat_statements, and that limit is stated directly.
Will Database Optimization Tool modify my Supabase production database?
No. The collector gathers evidence-focused evidence and Database Optimization Tool does not apply database changes, create indexes, or change Supabase project settings.
When should I read /docs/collector or /sample-report?
Read /docs/collector before preparing the local evidence export, and review /sample-report when you want to see how Supabase permission gaps and recommendations are presented.