Home/r/indiehackers/2025-07-13/#tech-stack-2025-choices-reasons
6

what's your tech stack at 2025 and why did you pick it?

r/indiehackers
7/13/2025

Content Summary

The post discusses tech stack choices for solo founders in 2025, inspired by Andrew Ng's emphasis on reusability. The author uses Next.js + Supabase + Vercel but expresses interest in Python-based backends. Commenters share diverse stacks including Next.js/Back4app/Vercel, Django/HTMX, and Expo/Kotlin. Key themes include balancing reusability with project needs, leveraging AI for boilerplate code, and prioritizing known tools over hype. Debates arise about Ng's reusability advice versus modern plug-and-play approaches.

Opinion Analysis

Mainstream Opinions:

  • Most commenters prioritize stack reusability across projects, aligning with Andrew Ng's advice.
  • Popular stacks include JavaScript-based tools (Next.js/Vercel) paired with BaaS platforms (Supabase, Firebase, Back4app).
  • Many emphasize using known technologies over hyped ones for efficiency.

Controversial Views:

  • u/tremblerzAbhi partially disagrees with Ng, arguing AI reduces the need for rigid stacks by generating boilerplate code, though acknowledges compounding benefits.
  • Debate exists between full-JavaScript stacks (Next.js) vs. multi-language approaches (Python/Django), with u/Junior-Read-770 conflicted about Python backends.

Key Debates:

  • Reusability vs. flexibility: Some advocate for standardized stacks, while others support plug-and-play tools aided by AI.
  • Language preferences: Python enthusiasts (u/Junior-Read-770) seek alternatives to JavaScript-centric tools, but face integration challenges.

SAAS TOOLS

SaaSURLCategoryFeatures/Notes
Next.jshttps://nextjs.org/Frontend FrameworkReact-based framework for server-side rendering and static site generation
Supabasehttps://supabase.io/Backend-as-a-ServiceOpen-source Firebase alternative with PostgreSQL database, authentication, and real-time capabilities
Vercelhttps://vercel.com/Hosting/DeploymentPlatform for frontend frameworks and static sites with serverless functions
Back4apphttps://www.back4app.com/Backend-as-a-ServiceBuilt on Parse, offers low setup overhead and scalability
Convexhttps://www.convex.dev/Backend-as-a-ServiceModern backend platform with built-in database and real-time capabilities
Capacitorhttps://capacitorjs.com/App DevelopmentCross-platform native runtime for web apps
Djangohttps://www.djangoproject.com/Backend FrameworkHigh-level Python web framework
HTMXhttps://htmx.org/Frontend LibraryAllows adding interactivity directly in HTML
Firebasehttps://firebase.google.com/Backend-as-a-ServiceGoogle's platform with database, authentication, and hosting
Railwayhttps://railway.app/Hosting/DeploymentPlatform for deploying apps with databases and cron jobs
Fly.iohttps://fly.io/Hosting/DeploymentPlatform for running full stack apps globally
Northflankhttps://northflank.com/Hosting/DeploymentPlatform for deploying and managing microservices

USER NEEDS

Pain Points:

  • Difficulty choosing a tech stack that balances reusability across projects with specific project needs
  • Confusion about long-term tool suitability for solo founders juggling multiple ideas
  • Tension between using preferred languages (e.g., Python) and stack efficiency (e.g., JavaScript-based tools)
  • Concerns about stack limitations (e.g., HTMX potentially lacking features)

Problems to Solve:

  • Finding a development stack that is reusable across multiple projects to save time
  • Balancing speed to market, cost, scalability, and reusability in tech choices
  • Reducing setup overhead and configuration time for small to mid-sized projects
  • Generating boilerplate code efficiently when switching stacks

Potential Solutions:

  • Using full-stack frameworks like Next.js + Supabase + Vercel for integrated solutions
  • Adopting Backend-as-a-Service (BaaS) platforms (Supabase, Firebase, Back4app, Convex) for low-configuration backends
  • Considering AI tools to generate boilerplate code when exploring new stacks
  • Prioritizing known technologies over hyped ones for faster development

GROWTH FACTORS

Effective Strategies:

  • Offering low-configuration backend solutions to reduce setup time for developers
  • Providing integrated hosting/deployment platforms with auto-scaling capabilities
  • Supporting multiple project types (web, mobile) through cross-platform tools

Marketing & Acquisition:

  • Targeting solo founders and indie hackers through community discussions (e.g., Reddit)
  • Highlighting ease of use and quick deployment in marketing messages

Monetization & Product:

  • Freemium models with scalable pricing based on usage (e.g., Vercel, Railway)
  • Product-market fit through solving pain points like boilerplate code generation and configuration overhead
  • Feature development focused on reusability and cross-project consistency

User Engagement:

  • Community building in developer forums and subreddits
  • Showcasing real-world stack implementations in indie hacker contexts
  • Encouraging discussions about trade-offs (speed vs. scalability) to build authority