Scores 9.1/10 overall. with execution at 9.1 and access readiness at 9.2. Payment: Free tier generous; billing API exists but limited automation. Governance: RLS policies, org-level access, growing compliance certifications. Web accessibility: Dashboard is clean and navigable; PostgREST API is agent-friendly.
Verify before you commit
Use this page to sanity-check Supabase quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 11, 2026
Freshness
Updated 2026-03-11T15:12:00+00:00
Mar 11, 2026
Failures
2
2 active failure modes
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 9.1 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 9.2 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 9.1 | |
Agent believes table is empty when RLS is filtering all rows. Extremely hard to debug — no error message, just missing data.
Agent impact: Agent believes table is empty when RLS is filtering all rows. Extremely hard to debug — no error message, just missing data.
Workaround: Always verify RLS context by testing with known-existing data. Use service_role key for administrative operations. Add explicit RLS policy tests.
Agent's first database query after idle period fails. If no retry logic, the entire operation aborts.
Agent impact: Agent's first database query after idle period fails. If no retry logic, the entire operation aborts.
Workaround: Implement connection retry with 2-second initial delay. Use session pooler mode (port 5432) for persistent connections. Add health check pings.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
Value ------- ~50ms ~150ms ~400ms 99.9% SLA (Pro) Free: 60 direct, 200 pooled 500MB DB, 1GB storage, 2 projects --- - Idempotency: Use ON CONFLICT (upsert) for idempotent inserts: .upsert({...}, on_conflict="id").
Supabase is an open-source Firebase alternative providing a Postgres database, authentication, real-time subscriptions, edge functions, and file storage — all behind a unified REST and client API. For agents, Supabase is a primary data layer: store user data, manage auth flows, query structured data via PostgREST, and react to database changes in... Reviewed from official documentation.
REST API (PostgREST) - Base URL: https://<project-ref>.supabase.co/rest/v1 - Auth: apikey header (anon key for public, service_role key for admin) - Content-Type: application/json - Rate Limits: No hard rate limit on Pro plans; free tier has connecti
For Humans 1. Create account at https://supabase.com/dashboard 2. Click New Project → choose org, name, region, and database password 3. Wait for provisioning (~2 minutes) 4. Navigate to Settings → API to find your project URL and keys 5.
Supabase is an open-source Firebase alternative providing a Postgres database, authentication, real-time subscriptions, edge functions, and file storage — all behind a unified REST and client API.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
9.1 / 10.0
No alternatives captured yet.