Choosing your stack for an indie project

The best stack for an indie project isn’t necessarily the newest or the most “scalable” — it’s the one that lets you ship and iterate fast without maintenance eating all your time.

Principles that help

Use what you already know
Learning a language, a framework and a database at the same time delays the first deploy. Prioritize reaching an MVP with technologies you’re comfortable with; you can change or evolve later.

Fewer pieces, less pain
Each new technology is one more thing to update, debug and keep working in production. A lean stack (e.g. Next.js + a database + an auth provider) is usually enough to start.

Think “a year from now”
Choose tools with good documentation and an active community. That way, when you need help or want to hire someone, it’ll be easier.

Common combination examples

• Front + API: Next.js (or another full-stack framework) with API routes or a minimal backend.
• Database: Postgres on a managed service (Supabase, Neon, Railway) avoids managing a server.
• Auth: Supabase Auth, NextAuth or Clerk so you don’t reinvent login and sessions.
• Deploy: Vercel or similar for front and serverless; Railway or Render if you need long-running processes or workers.

There’s no single “right” stack for everyone. What matters is: can you launch in weeks, not months, and can you maintain it on your own? If yes, you’re on the right track.