What is Supabase Auth (Platform)?
The dashboard login layer: JWT sessions, auth-state listeners, and Google sign-in for the BYOB product itself. Distinct from the Better Auth wiring generated apps receive.
Related terms
Anon Key vs Service-Role Key
The public client key (safe in browsers, constrained by RLS) versus the privileged server key (bypasses policies, never leaves the server). Mixing them up is the classic Supabase security bug.
Row-Level Security (RLS)
Per-user table policies enforced by the database itself: users can only read or write their own rows. RLS is what makes the anon key safe to ship in client code.
BYOB-Managed Google Auth
Google sign-in provisioned by the platform so generated apps authenticate without the developer registering OAuth clients. Project-owned OAuth remains available for teams bringing their own brand and keys.
Cloudflare Worker
Serverless code running on Cloudflare’s edge network, close to visitors worldwide. BYOB deploys generated apps as Workers: no servers to provision, scale, or patch.
Dispatcher Worker
The SaaS router that maps each request — by publish slug or custom domain — to the right per-project Worker. One edge entry point, thousands of isolated apps behind it.
Dispatch Namespace
The isolate group containing a fleet of per-project Workers. Namespaces let one platform deploy, version, and route user projects independently.