I'm working on a side project to build a SaaS application, and I'm considering my options for authentication systems. The ones I'm looking at are Supabase, NextAuth.js with Postgres hosted on a VPS, and Clerk. My priorities are long-term scalability and maintainability because I want to avoid high costs or limitations as my product grows. As someone who's new to building live projects, I'd love to hear about your experiences and recommendations for someone starting a SaaS today. I'm currently leaning towards Supabase Auth because it combines database and authentication services and appears to be more cost-effective over time. What do you all think?
4 Answers
I think Google Identity Platform is a strong contender, even if it has a more complex setup. You can get up to 50,000 monthly active users for free, making it a good option if you scale. Still, for your first project, keeping things simpler is probably the best route, so Supabase sounds good. Just keep this platform in mind for future projects!
Choosing an authentication system isn't set in stone—you can switch later if needed. I recommend picking something that allows you to quickly develop the core of your app. I've enjoyed working with Supabase as it helps you get started quickly. don't stress too much about long-term decisions right now. Just get your project off the ground!
I had the same concerns, especially when it comes to changing auth systems later. But hearing your experience makes me feel more relaxed about using Supabase for my first project.
Supabase Auth is great for an all-in-one solution, especially in the early stages when cost-efficiency is vital. It’s easy to set up but does tie you to their infrastructure. If you're looking for maximum control, NextAuth with Postgres is excellent, but it requires more management on your end. Clerk is user-friendly, but costs can add up as you grow. Your choice should depend on whether you want speed or complete control.
That's where I'm torn! I want the flexibility of NextAuth but love the simplicity of Supabase. If you were starting fresh, would you focus on speed or control right from the start?
I’ve built a few SaaS projects, and I believe Supabase Auth is the best option for solo developers or small teams. It combines authentication, database, and real-time features all in one, and the free tier is quite generous. The big concern is vendor lock-in as you grow, but for most small projects, that's not a major issue. Clerk is super user-friendly but can get pricey as you scale. On the other hand, using NextAuth with Postgres gives you total control but can be more complex since you’ll be managing sessions and passwords yourself. I recommend starting with Supabase—it makes it easier to validate your idea quickly!
Thanks for the insights! You brought up great points. I was worried about vendor lock-in too early, but it sounds wise to focus on scaling the idea first. If scaling is a problem later, that’s a good issue to have! Appreciate your take.
Thanks for the suggestion! I see the value in Google Identity, but simplicity is key for me right now.