Supabase

PASS consensus from 3 PASS.

The React quickstart covers project creation, seeded table setup, RLS, client initialization, selection, and browser output. One numbered page carries the whole path from project creation through the SQL that creates the table, grants, and the RLS policy, to createClient and a supabase.from('instruments').select() call rendered on the page. The React quickstart walks from project creation through SQL Editor table creation, RLS policy, Vite scaffolding, supabase-js install, client init, and a select query in one linear page.

PASS consensus from 2 PASS, 1 PARTIAL.

Database counts end at 16XL; Realtime limits and billing quotas use separate scopes, leaving 24XL and 48XL connection counts undocumented. A single table gives Database Max Connections and Connection Pooler Max Clients for all eleven compute sizes (Nano 60/200 through 16XL 500/12,000), and the pooling page names which limit each number governs without restating any value. Connection limits per compute size are listed in a single table with footnoted caveats. Plan-level quotas (MAU, egress, bandwidth) are on the pricing page and cover different scopes; no contradictory numbers were found.

PASS consensus from 3 PASS.

The 42501 troubleshooting page identifies RLS insert denials, while the RLS guide supplies grants, an insert policy, and tests. A dedicated 42501 page enumerates five causes with a log query and grant-inspection SQL, and the RLS guide supplies the with check insert-policy form plus pgTAP tests that assert the denial. The RLS page explains the grant-vs-policy distinction and pinpoints 42501 as a missing-grant indicator. A dedicated troubleshooting page for 42501 lists the three causes (missing privilege, restricted schema, column access) with SQL fixes. The error codes reference confirms 42501 maps to 'insufficient privileges' with HTTP 401/403.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The push example shows the insert trigger, receiver payload parsing, secret-key validation, auth-header setup, and a test insert. Creation and the INSERT payload shape are documented, but no page states how a delivery is authenticated: there is no signing secret, signature header, or verification procedure, and the Dashboard steps stop at selecting events without reaching the URL or headers fields. Creating the webhook (via Dashboard or SQL) and the payload shape are documented. However, delivery authentication is not covered: no webhook signing secret, HMAC signature header, or verification procedure is described, so an agent cannot confirm who sent the payload.

PASS consensus from 3 PASS.

The API quickstart aligns cURL and JavaScript reads; the JavaScript reference .md URL failed to load. The reference gives await supabase.from('characters').select() and the Data REST API guide describes the same surface as PostgREST at https://<project_ref>.supabase.co/rest/v1/, with both the reference and the quickstart using the publishable key. The JS select reference gives a minimal example. The API overview (rest/v1/) and SQL-to-API page confirm the REST endpoint mapping. The React quickstart uses the same pattern to query an instruments table, matching the REST form shown in the API quickstart's curl and browser examples.