What is 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.
Related terms
Project-Owned OAuth
The developer’s own Google client ID and secret wired into their app. Required when the login screen must show the project’s brand and consent identity rather than the platform’s.
Better Auth
Authentication with managed Google sign-in or email/password flows provisioned for generated apps. Auth pages (callbacks, sign-in) are private surfaces and stay noindexed like any other.
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.
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.