What's your go to tech stack when starting a new SaaS project?
Lately I've noticed most discussion around AI coding tools focuses on which assistant or terminal agent people use, but not much on the actual architecture decisions behind that, things like framework, hosting, database, and auth choices that affect cost and security down the line.
For context, my current default stack is Next.js on the frontend, Supabase for database and auth, Vercel for hosting, and Stripe for payments. I picked it mainly for speed of shipping and because it keeps infra costs predictable early on, but I'm not sure it's the best call for security or scaling past MVP stage.
A few things I'm curious about:
Do you settle on a default stack before prompting your AI agent, or does the agent end up influencing your stack choice?
What's been your biggest regret, cost, security, or scaling wise, with a stack you picked early on?
Any stack you'd actively avoid for a new SaaS in 2026?
Would love to hear what's worked, or not, for others building solo or in small teams.
Replies
I usually start with Next.js, Supabase, and PostgreSQL. I'm optimizing for speed, simple deployment, and fewer moving parts until real uses tell me what actually matters.
@dipmala_kumari My default stack is Next.js, TypeScript, PostgreSQL, Prisma, and Vercel. I've found that keeping everything simple makes iterations much faster.
@dipmala_kumari @jonathan_monroe I'm a big fan of choosing boring, reliable technology for MVPs. For me, Next.js, Tailwind, Supabase, and stripe cover almost everything I need.
@dipmala_kumari @jonathan_monroe @tarsicio_hudson I'd rather spend time talking to customers than configuring infrastructure. Have you ever switched stacks midway through building a product?
@dipmala_kumari For me, the best stack is the one I already know well. These days that's Next.js, Supabase, PostgreSQL, Tailwind CSS, and GitHub Actions.
Biggest regret pattern I've seen described repeatedly is auth coupling, not hosting cost. Vercel bills get scary but you can move off in a weekend. Migrating users out of an auth provider that owns your password hashes and sessions is a much worse afternoon. Worth checking what an export actually gives you before you're committed.
The stack matters, but clear architecture matters even more. A well organized codebase on a simple stack is easier to scale than a complicated one built from day one for hypothetical future needs.
I've stopped overengineering my first versions. I prefer Next.js, Tailwind CSS, Supabase, and Vercel because they let me focus on solving customer problems instead of maintaining infrastructure.
I say stick with the big players, whatever you're already good with. Stack choice usually matters less than knowing it well. I go with Vue/Nuxt + Tailwind, still very solid and less crowded than the Next crowd here.
AI doesn't really influence the choice for me either, it's more about not letting the agent maintain a stack you can't keep up with yourself.