What is supabase?

Technical definition

Supabase is a backend-as-a-service platform assembled around a managed Postgres database. Its components include the database with row-level security, an authentication service, object storage, auto-generated REST and GraphQL APIs derived from the schema, realtime subscriptions to database changes, and edge functions for server-side logic.

Because it is Postgres underneath rather than a proprietary datastore, standard SQL, existing tooling, and normal migration paths apply.

In plain terms

Supabase is a ready-made backend. Rather than setting up a database, a login system, and file storage separately, you get them as one service.

It is built on Postgres, which matters because Postgres is a standard rather than a private format, so your data stays portable.

Why it matters

Assembling a backend used to be the barrier between a working front end and a real application. Managed backends removed it, and that is a large part of why one person can now ship something that needed a team.

One security point deserves emphasis, because it is the most common cause of data leaks in AI-built apps.

Supabase exposes your database through an API reachable with a public key that ships in your frontend code. That is by design and it is safe, but only when row-level security is enabled and policies are set. A table with RLS off is readable by anyone who has that key, which means anyone who opens your site. Several publicly reported leaks from AI-built apps trace to exactly this.

So the check before launch: RLS enabled on every table holding user data, policies that restrict rows to their owner, and a test where you log in as one user and confirm you cannot reach another's records.