FINDING 01·Developers and end-users in restricted or underserved geographic regions·1 source
Geographic / network accessibility — service unreachable in certain regions
Users in Yemen report that all *.supabase.co domains are completely unreachable without a VPN, breaking authentication, database access, storage, realtime, and edge functions for end users in that region. This is a recent issue (July 2026).
Source
“None of the *.supabase.co domains are reachable without using a VPN. Applications that depend on Supabase stop working completely because they cannot connect to the service. This affects applications built on Supabase, making authentication, database access, storage, realtime, and edge functions unavailable for users in Yemen.”
FINDING 02·Individual developers and small teams relying on Supabase for production data·1 source
Account / data loss and login recovery failures
A user reports losing access to all their databases and organizations after a GitHub login issue, with no clear recovery path — a critical reliability and account-management concern (July 2026).
Source
“I cannot log in with github as I initially did, it is making me start a new org and account and can't access my old organizations and the work that was done. Used the same email to no avail.”
FINDING 03·Freelancers, agencies, and software consultants managing multiple web app projects·2 sources
Pricing doesn't scale for multi-project / multi-environment workflows
Developers managing multiple client projects or needing separate dev/test/staging/prod environments find Supabase's per-project pricing model expensive and poorly suited to their workflows. This is a recurring, recent complaint (2026).
Source
“The Pro plan is $25/month, and then every additional project adds another $10/month. If I want to have separate environments like development, testing, acceptance, and production, I am already looking at around $40/month just for databases.”
Source
“On supabase I cannot create multiple free projects it is limited to 2 and then I have to pay for more around £10 each / month.”
FINDING 04·Developers and businesses seeking open-source / self-hosted backend solutions·2 sources
Self-hosted version lacks feature parity with the cloud offering
Users who attempt to self-host Supabase to avoid cloud costs or maintain control discover that key features — particularly auth provider UIs and integrations — are missing or harder to configure compared to the managed cloud platform. This frustration is documented in recent discussions (2026).
Source
“When I tried deploying supabase on my vps i got to know that it does not provide all the features as it does on the supabase cloud portal. For example there are no auth providers ui and easy integration.”
Source
“I am trying to host Supabase with a separate PostgreSQL DB. According to their docs, they say that Supabase uses pgjwt for auth. However, AWS RDS or Azure PostgreSQL doesnt not support pgjwt. Is there an alternate for pgjwt for PostgreSQL?”
FINDING 05·Full-stack developers and AI/agent workflow builders·2 sources
Row Level Security (RLS) is complex, error-prone, and blocks developers by default
Multiple discussions (2024–2025) highlight that Supabase's RLS being enabled by default causes queries to silently fail without policies, and that writing and maintaining Postgres policies is verbose and error-prone, prompting developers to seek in-code alternatives or switch tools entirely.
Source
“RLS enabled by default → queries fail without policies. Verbose Postgres policies that are error-prone to write and maintain. Secrets and auth setup require lots of manual wiring.”
Source
“RLS enabled by default → queries fail without policies. Writing/maintaining Postgres policies is verbose and error-prone. Secrets and auth integrations require lots of manual setup.”
FINDING 06·Developers building data-heavy applications with large datasets·1 source
Full-text search performance degrades severely at scale
A developer with a large dataset (hundreds of thousands of records) found Supabase's full-text search unusably slow — queries exceeding 8 seconds or timing out entirely — even after indexing, leading them to migrate to PocketBase for dramatically better performance.
Source
“The volume of records quickly became an increasing struggle for Supabase when performing a full-text search on the whole dataset. Even after indexing, the queries ran above 8s when not simply timing out.”