Supabase Auth vs Better Auth?
self-hosted🔢DB ConnectionsauthHey 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?
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?
