Hey everyone,
I’ve built a SaaS app in Glide that’s getting solid traction: paying customers, affiliates, real usage. The problem is pricing mechanics, not demand. Glide charges per user added to the database, which makes free trials basically unusable at scale.
I’m planning a full migration and defining a new stack with one hard requirement: no pricing tied to number of users or workspaces.
Right now I’m considering: • Supabase strictly as the database • Self-hosted Better Auth for authentication
The idea is to fully control auth and user growth without per-seat penalties, while keeping infra predictable as usage scales.
Curious to hear thoughts from people running Supabase in production: • Does this setup make sense long-term? • Any hidden gotchas with Supabase-only DB + external auth? • Alternatives you’d recommend for this constraint?
A user is considering migrating their SaaS app from Glide to a new stack to avoid per-user pricing. They plan to use Supabase as the database and self-hosted Better Auth for authentication. They seek advice on the feasibility of this setup, potential issues, and alternatives.
Its great but keep in mind you'll lose auth.uid() which is only if you use supabase x supabase auth, and you'll need to map your own external auth user id to supabase and create your policies around that
Thanks for sharing that!
If you are using better auth then you likely won't be using Supabase Auth at all nor would you need to enable RLS as I assume you would handle permissions from your backend system itself. In this case you would just turn off the Data API so that it's not accessible via the REST endpoints. This would be all you would need to do when using Better Auth.